Forum Discussion
Due to forced automatic updates we may move to a competitors product for development
As it says in the title. Unfortunately we can't as a business take the Rift as a serious development platform if we can't control your driver updates.
As we can't suddenly find that our latest presentation builds have stopped working for whatever reason before important meetings etc. It's just not feasible or professional.
I am sure we are not the only ones in this situation.
Please fix this.
As we can't suddenly find that our latest presentation builds have stopped working for whatever reason before important meetings etc. It's just not feasible or professional.
I am sure we are not the only ones in this situation.
Please fix this.
3 Replies
- I really like the release notes for the 1.4. They are pushing an update known to have issues with the latest AMD driver. There is one golden rule, do not fix what is not broken. If a user is happy with the 1.3.2 behavior, it is at his own risk to update if we want, it is a trade between the risk and benefits. But forcing an update that is known to create an issue, that's a fun one :)
- And before someone tries to counter your point with 'just use and older AMD driver' - you may well be in the situation where AMD has fixed something you need in the latest driver. It only gets more complicated from there. This is the nature of PC development and consumerism on a platform that uses devices and software from multiple vendors - and it's why we must have control on what is installed on our systems.
This and some other issues shows that whoever is making this decisions at Oculus doesn't seem to understand the PC platform at all, which is very worrying for the future.
Automatic updates on by default is fine but the user MUST have the option to disable them. I look forward to a future where this is actually a requirement by law for any software system - because the implications of this are greater then issues surrounding even Oculus determination to burn health and safety warnings into our retinas. - I see the process of the way Oculus VR choose to go highly critical also. No real improvement to the API (since 0.6beta nothing really changed except the way to call the same functionality) - just more and more priority of creating an Walled-Garden. IMO Oculus VR has the best device with CV1 in terms of picture quality and lightness and API-behaviour. But it is worse in tracking area, developer support, and API-flexibility. So many failures in the documentation as if it NEVER had anyone proof read it. No git-repository with so the old failures popping up again and again.
While even our consumer-device was late, the competitor got us an development device. We are not even trying to get early access on Oculus Touch since we just see it as a waste of time to even try.
