Hey Guys, going to be an interesting response here as a bit of a blend of doing work for SpringboardVR and being an Operator long before that as well so I'll be mixing my own experiences and thoughts as made by being in both worlds! This post is intended to give my own feedback on it and to help fill in some gaps and perceptions hopefully and like Eric and Andrew are my general thoughts on the topics rather than a direct response.
What you said is true and I'll probably just be saying what you said again. There are always bugs, I'm sure most of us appreciate that with software you simply can't make a perfect program the first time and I understand from both sides that those bugs can be crippling. First thing I should mention is that there is a lot of testing done before releases like this, there were 2 weeks of Beta Testing internally before an entire week of testing with selected Arcades, it was then decided to extend by a couple of weeks to fix the known bugs and upon release all known bugs had been cleared. The problem arises when we distribute to over 500 Arcades with over 2600 Stations, it's impossible to account and test for every scenario.
In the end there were a bunch of bugs but each bug would only be experienced by 5 or 6 operators most of the time and no others which means they're very individual and that means it takes time to go to each of these operators and collect the data to find out why as we can't replicate them on our end as it's because of their individual setup and we can't just take control of these stations as the bugs are found when in use which means often when it's busy and not available for us to jump on which exacerbates the whole situation. For anyone else reading worried that we don't do enough QA I assure you it is being done to the best of our abilities, there is always room to improve though and each time we fail we will do our best to integrate the lessons and learn from them.
I think it's important here to note that a lot of these Bugs are often due to extremely outdated Drivers and Updates, some GPU Drivers are as much as a year out of date, so whilst they might be "Stable", being that far out of date the programs that rely on them (eg the Launcher and all of the content, haha!) becomes unstable as it's not written for year old drivers, same goes for Windows and keeping the content and the launcher itself up to date. It means the Devs often spend a lot of time finding an obscure work around for these few that keep things so far out of date which takes them away from being able to do other things. I personally keep my GPUs no more than a month out which is more than enough time for any bugs with them to be worked out and use that same philosophy for most other updates.
I think Jordan Williams already addressed this fairly well over in
https://community.springboardvr.com/t/let-us-customise-game-presets/491, the major issue there is that I think the Content Creators are well aware we'd like to be able to make these changes are but are still unwilling to allow us as they want to control what they've created which I think is fair on a certain level but I'm really hoping for a new middle ground to be struck though eventually and would encourage us to make a bit of noise to let the Content Creators know that we want this ability. I think that whilst we feel we have a better idea of how to market to our local market (And in a lot of cases probably do) the Content Creators are trying to get paid too and worry the exact opposite that we don't and it'll end up with their Content being trashed. I think the perfect example of this is Richies Plank Experience being put on PlaystationVR, it's a BRILLIANT bit of content but it's being absolutely panned in the reviews by PSVR Users, the Devs there would rather it just not be on there but they're also making money off it, the problem becomes that when it goes on there they really are unable to control it and the environment it is used in.
I wouldn't be overly concerned about not being able to launch, infact this should make things MORE robust in the end, you see the DRM isn't dependant on having an Internet Connection at all, it is dependant on Springboard running in the background, which means if you lose connection to the internet or our servers you'll still be in Offline Mode and able to launch titles from the Launcher without hassles, you'll just need to manually let the customers know when time is up really, I tested this today for instance with Superhot VR Arcade, I pulled the LAN cable to simulate losing connection, it displayed the "Attempting to Connect" in the Launcher and I was able to launch Superhot which is a CDS title with no hassles.
Out of interest, I've been trying to imagine some scenarios where you would want to close SpringboardVR and launch a title but can't think of any off the top of my head but am pretty tired after a long week and not thinking clearly, what are we thinking are the likely scenarios here? Is good to think about them for developers to see as well!
Probably not a bad idea for the team to be reporting responses, a simple "Email sent to Developers with request on xx/xx/xx" and then when they respond something generic like "Developers Responded positively and working with them" or "Developers are not interested" type respond could be good, I've put this in as a Feature Request over at https://features.springboardvr.com/feature-requests/p/better-tracking-of-content-request-status as well. I think a lot of Developers view Steam as the easy version and anyone else as being more work so don't really consider the requests, other times I wouldn't be surprised if there are exclusivity deals done with Steam and other providers, take Fruit Ninja for instance, there is a company called Secret Location that does their PPM and they probably have a deal with Fruit Ninja as exclusive agents which is why Springboard aren't able to get it on!
I'm unsure about the timeline on this, I agree and want it out soon as it really does affect us in terms of costs, I'm feeling the pain as well with the Australian Dollar being so crap right now!
In response to your last paragraph I agree but also emphasise that there is always so much going on behind the scenes that we don't get to hear about, that's my Springboard perspective, my operator perspective is that those sorts of things need to be communicated better and my mixed perspective shows me that the team have realised this and are trying to do more to get this across and fix it and we'll start to see that very shortly I hope.