Thanks so much for the kind words around 1.2. We’ve been really happy with the feedback we’ve received, and so far this release has been very robust and stable. As we mentioned last week, we are now feature locked and knocking down bugs as we race toward our targeted 1.3 date of 3/15.
In these last few days before launch it’s crucial that we all work against the latest-and-greatest runtime. To that end we will be changing our approach to runtime releases: on Friday, March 4th and Friday, March 11th we will roll a new, stable runtime out to the LIVE channel. This means that you will see updates and firmware requests a little more frequently than before, but it also means that you should have a continually improved experience in the run up to launch.
We appreciate that many of you are working on builds for demos and launch and would prefer not to have to deal with rolling runtime updates. If that’s the case you should make sure that all of your machines are pointed at the Rift12 channel (instructions below) to opt out of this process and stay at 1.2. Please note that we will be rolling two minor but critical fixes around seating orientation calibration and Home performance to the Rift12 channel on Friday.
Whenever you run our setup.exe your machine will be automatically pointed at the LIVE channel. To know what channel you are currently pointed at, run regedit.exe and examine the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Oculus VR, LLC\Oculus\Config\CoreChannel. If this value is “LIVE” then you are pointed at the Live channel, if you want to stay on 1.2 please change this to “Rift12”. In the sdk zip we ship registry edit files: Rift_1.2_Channel.reg and Rift_LIVE_Channel.reg which you can execute to update this key appropriately.
Please note that if you would like to ensure you are not upgraded you will need to modify the registry for all machines running the Oculus runtime in your office.
Has anyone else lost their Oculus client after today's update? The Oculus shortcut on the desktop isn't valid anymore, so we're not able to update our firmware.
So, the Oculus home upgraded to 1.3 this afternoon (I went and saw in Settings->General and I could see new options like Rebooting the Oculus Service with the Lorem Ipsum description).
Right now it just notified me to update to a new version again and I'm back on 1.2...
Is that normal? I didn't touch anything in home other than starting/closing it as I was debugging our game...
"TPG-Henry" wrote: Has anyone else lost their Oculus client after today's update? The Oculus shortcut on the desktop isn't valid anymore, so we're not able to update our firmware.
My service seems to be constantly trying and failing to update. The service has restarted about 10 times so far and it keep doing it? Any tips/help as I cannot continue development at the moment.
