It works for versions 0.4.4.0, 0.5.0.1, 0.6.0.1, 0.7.0.0 and 0.8.0.0, also on windows 10. On windows 10 runtimes 0.4.4.0, 0.5.0.1, 0.6.0.1 are working only in extended mode.
*Windows 7 or higher *64-bit architecture *Updated videocard drivers *If you moved your desktop to another path then delete directory "Desktop" in your "%userprofile%" (you can copy and paste this to Win+R), otherwise shortcuts are not created on your desktop.
1) Uninstall all of the versions of Oculus Runtime (better with registry clean, Total Uninstall can help you) 2) Reboot your PC 3) Install Oculus Runtime 0.8.0.0 4) Reboot your PC 5) Start "Install.exe" Warning!!! After installing switcher your PC will restart after 10 sec. (It's necessary for the correct switching then)
If you use 0.6.0.1 version on windows 10, you must to start "OVRServer" on your desktop every time after launching OculusConfigUtil If on windows 10 after switching to 0.6.0.1 black cmd window doesn't start - start "OVRServer" manually from desktop. It's doing one time until you switch runtime or reboot PC. Don't close this black cmd window while using 0.6.0.1, otherwise you will see "Service unavailable" in OculusConfigUtil.
For uninstall start "Uninstall.exe"
*Completely reworked the script. *Added correctly switching of tracker driver. *Added correctly compatibility with windows 7\8\8.1\10 *Now you can install oculus runtime to any directory.
Possible issue: Glitch with switching from 0.6 to 0.7\0.8 on windows 7
Solution: Switch 0.6 to extended mode in oculusconfigutil before.
If you will be interested in this switcher and will support me with your feedbacks and may be something else, then
*Possibility for installing switcher to another path (not only default disk C:) *Installator by Inno Setup or another compilator (for easy path choosing, not from cmd window) with registry registration *Add the runtime sdk 1.0 support (when it will be released)
unfortunately the installation failed in the first xcopy line (Win10 Pro, German). Of course I ran it as admin. Parts were copied to C:\ (which is IMHO a bad idea, I'd rather prefer using own documents or something else not in the root folder). However after the failed installation I was hesitant to try it out because you're deleting stuff in system32 and I would rather not risk corrupting system folders.
Anyway, I'm at work now and will probably upload the dos output later this day.
Oh and instead of including the 0.7 & 0.8 Runtime, in my opinion it would make more sense to have 0.5, 0.6 and 0.8 (because there are hardly any incompatibilities between 0.7 and 0.8 but lots between 0.5 & 0.6).
I did not look at your Switcher in-depth, however I assume you must install all the runtimes you want to use as a part of configuration process.
The issue is, some users (ex. me) have a problem with incompatibility of Oculus Runtime older than 0.8. For example, when I installed the 0.6 Runtime, then rebooted the system, Windows did not boot. All I saw was the Windows 10 logo and the dots rotating in circle, forever. I had to get into the Emergency Mode, clean-remove the nVidia driver, plus manually remove the Oculus 0.6 Display Driver (a file in Windows directory, plus a registry entry) because the Windows Installer services are unavailable in Emergency Mode. Then my OS came back online.
My rig details are in the footnote. It happened on 355.82 and then I tried the same on newer version of the nVidia driver. Same thing happened, that's why I ask the question. For some people on Windows 10, launching older runtime is impossible due to incompatibility and can leave them with unusable Windows installation.
EDIT: Forum thread about this. The OP mentiones something else, however the first, and the second answer talk about an "endless boot loop" which leaves the OS "bricked".