[App] Oculus Runtime Switcher (0.5/0.6/0.7/0.8/1.3) with GUI

Oh man this is such a good tool, I am desperately hoping that this tool will allow 0.6 will work under Win10 one day as there's a couple of games that wont run on any other version
 
Overnight this tool stopped working for me for every runtime except 1.3. I've tried every solution I can find, including uninstalling all Oculus drivers and starting from scratch. The main one I need is 0.8, and with that I just get constant crashes for the Oculus service, service unavailable, etc.

There was an update for Oculus Home yesterday that may have triggered this. Unfortunately, I don't believe I can just rollback Oculus Home to a previous version, especially as it automatically updates, and denying it a net connection would render it useless as well.
 
Last edited:
Overnight this tool stopped working for me for every runtime except 1.3. I've tried every solution I can find, including uninstalling all Oculus drivers and starting from scratch. The main one I need is 0.8, and with that I just get constant crashes for the Oculus service, service unavailable, etc.

There was an update for Oculus Home yesterday that may have triggered this. Unfortunately, I don't believe I can just rollback Oculus Home to a previous version, especially as it automatically updates, and denying it a net connection would render it useless as well.

I've sold my DK2 now, so I can't diagnose. Couple of things: has the install path changed for Oculus?

I wish I could fix this, but I probably won't be able to. You need to work on the .cmd files and get it working that way. If you send me your findings, I can help. It could just be that they've broken it and 0.8 just won't work.
 
thanks @drkaii, They changed the directory for Oculus 1.3 from 'program files (x86)' to 'program files'. I changed 1.3.cmd to the new directory and it works fine to restore from attempts at other runtimes. I tried running 0.8.cmd from the command line, but it doesn't get any errors that show up in the console. When the dk2 config appears, it says 'service is unavailable', and usually has a log message just below 'service has crashed'.

Not sure if there's anything else that would be useful. On another note, I haven't seen any other mention of this problem yet, so it's also possible it's just something with my PC that happened yesterday by coincidence on the same day of the update.
 
Last edited:
thanks @drkaii, They changed the directory for Oculus 1.3 from 'program files (x86)' to 'program files'. I changed 1.3.cmd to the new directory and it works fine to restore from attempts at other runtimes. I tried running 0.8.cmd from the command line, but it doesn't get any errors that show up in the console. When the dk2 config appears, it says 'service is unavailable', and usually has a log message just below 'service has crashed'.

Not sure if there's anything else that would be useful. On another note, I haven't seen any other mention of this problem yet, so it's also possible it's just something with my PC that happened yesterday by coincidence on the same day of the update.

Please test: http://bit.ly/ORS2_1beta

Note, if you want to do a proper extensive test, feel free, but I would like feedback if the Home (Latest) button works now, as well as if there are any other bugs :)
 
I haven't seen any other mention of this problem yet, so it's also possible it's just something with my PC that happened yesterday by coincidence on the same day of the update.

No, it's not just you, but I thought it was "just me" as well :p At least that's a good thing to know.

@ drkaii:

Great "little" utility btw! If/when I can get it working again, but anyway thanks for putting it together!

I just found the updated runtimeswitcher 2.1 beta, so I'm going to test that and see how that fares.. will also report back later (probably) or tomorrow.
 
@drkaii: "Sorry, the file you requested is not available.

The file has been deleted by the uploader and it cannot be restored. Please contact the sender and ask them to upload the file again. "

Edit: I see you updated the link in the original post. I still had to change one thing in 1.3.cmd from:
"C:\program files (x86)\Oculus\Support\oculus-runtime\DirectDisplayConfig.exe" on
to
"C:\program files\Oculus\Support\oculus-runtime\DirectDisplayConfig.exe" on

and it works for 1.3, but still not for 0.8

@CoilWinder - glad to know it isn't just me either.
 
Last edited:
Hello everybody.
I downloaded runtime switcher for changing versions 1.3 - 0.8.
Faced with such a problem: when I turn on the version 0.8, when you start ""C:\program files (x86)\Oculus_0800\Service\OVRServiceLauncher.exe" -install -start" error "Stopped work programs: OVRServer_x64.exe 117061-public TCID:641906" appears, and the "Service unavailable" message appears in the Oculus Configuration Utility.
Can you suggest how to solve this problem?
 
Well, after some fiddling, I basically got runtime 0.5.0.1, 0.6.0.1, 0.7 and 1.3.2 working.

I installed the new 1.3.2 first, then 0.5, 0.6, 0.7 and finally 0.8.

Installing runtime 0.8 just messed up everything it seems. I then got the "OVRServer_x64.exe has stopped working" error in an infinite loop. Uninstalled it, then had to reinstall 0.7 I think(?), a bit blurry on the details. I got an error message in the later part of the installation, but went on with it anyway. Seems to work (didn't get that error the first time installing runtime 0.7. The error message was "There was a problem with this Windows installer package, a program required for this install to complete could not be run").

I tried the runtime switcher 2.1 BETA, but in the end I ended up with the older V2, but with the newer 1.3.cmd (actually kept all the scripts from 2.1 beta, but I guess that's the only one different? Except that new alternative 0.6).

As runtime 0.8's DirectDisplayConfig.exe is used in most scripts, I simply copied runtime 0.7's version into the C:\Program Files (x86)\Oculus_0800\Tools folder. Bit of a hack on the hack, but seems to work.

Runtime 0.5.0.1 don't seem to work in direct to rift mode, at least I get the "HMD not detected" message. Haven't really tested that. But it works in extended desktop mode (which I use with 0.5).
Runtime 1.3.2 doesn't always turn on the DK2 when starting Oculus Home. Turning the HMD off and on seems to work. Sometimes maybe restarting Oculus Home.
Runtime 06.0.1 and 0.7 seems to work okay, but I haven't tested all modes or exensively.

I wish runtime 0.8 would work also, as some Leap Motion demos work with that afaik.

Still haven't tried Elite Dangerous with any of these. I guess the only one working with it now is 1.3? I know it worked with 0.8 a few days ago.. but ofc that won't work now.


@rich_hard1: Because some of us have the older DK2, and not least because some games and demos only work with older runtimes. For example Alien Isolation.
 
Yep. 0.8 doesn't work anymore, which means Elite only works in "horrid looking mode", and none of the demos that worked very well with 0.8 but weren't updated to 1.3 work anymore. I can't shake the feeling that Oculus is really [censored] 'angry'  that some people are not moving away from the DK2.
 
Last edited:
Can someone please test the latest version? 0.6 and 0.8 should be fixed. Please test and if you are able to, fix the script files and send back to me so I can distribute (sold my DK2 so can't test!)

https://www.reddit.com/r/oculus/comments/4gtqgo/oculus_runtime_switcher_v22_fix_for_06_08/

Based off instructions from:

FYI as NeoZeroo found out there is a fix to 0.8 service not starting. The only change that need to be made is: Add
Code:
ren "C:\Program Files\Oculus\Support\oculus-runtime\OculusAppFramework.dll" "temp_OculusAppFramework.dll"
to 0.8.cmd after
Code:
net stop OVRService
and Add
Code:
ren "C:\Program Files\Oculus\Support\oculus-runtime\temp_OculusAppFramework.dll" "OculusAppFramework.dll"
to 1.3.cmd after
Code:
sc delete OVRService
Result = Perfect Oculus Runtime Switcher v2.2 ;

And:

For 0.6 you'll have to:1 - Set the "C:\Program Files (x86)\Oculus_0600\Service\OVRServer_x86.exe" to run in Windows 8 Compatibility mode;
2 - Alter the vbscript on the 0.6.bat to: mshta vbscript:Execute("CreateObject(""Wscript.Shell"").Run(""""""C:\program files (x86)\Oculus_0600\Service\OVRServer_x86.exe"""""", 0, False)(window.close)")
3 - Change the line "taskkill /f /im OVRServerx64" to "taskkill /f /im OVRServer*" in all batch files.
Hope it helps :D
 
Still not working for me. As Tmcraig08 suggested in the reddit thread, I added
"C:\program files (x86)\Oculus_0800\Service\OVRServer_x64.exe" -install -start
to the end of 0.8.cmd, which he says is required for 64 bit

This at least got the config tool to say DK2 Ready, but it leaves a console window open, and like the other guy in that thread everything I try immediately crashes at the exact moment the dk2 display is supposed to turn on, and the demo scene option in the config is disabled.
 
Last edited:
Latest version now out, V3: please test!

0.8 and 0.6 should definitely be working! You probably need to change the install path of Home in the cmd files to whatever you've set it to. It's currently set to c:\program files (x86)\oculus which is likely to be wrong for some people.

http://bit.ly/ORSwitchV3

READ the updated instructions, or watch the guide!
 
Back
Top Bottom