Windows 10 "Threshold 2" update broke the 0.5 Oculus runtime
- Thread starter rohirm
- Start date
Are you uninstalling and running a driver cleaner a few times before installing the new(old) one while in safe mode?
- - - - - Additional Content Posted / Auto Merge - - - - -
Have not changed any of the scripts, i changed the 6.0.1 file names so they are activated by the existing scripts as if they were the SDK 5 files
Hi, I encountered a problem with detecting the DKS after upgrading to threshold 2. I was able to get it working again by following the procedure here - and I think the detection problem is independent of the graphics card vendor. It has been pointed out, quite rightly, that this is a risky, hacky way to sort out the DK2. But I think the whole process of getting SDK 0.5 to run on windows 10 is itself a rough hack and I couldn't find a way to get the system to cooperate without beating it up a little.
There is another post that posts a possible fix for th2, though it involves editing your reg database.
https://forums.frontier.co.uk/showthread.php?t=202726&p=3141204&viewfull=1#post3141204
That said, it might be worth trying before this fix, to go into your device manager, show hidden, and remove all displays that you can find entirely, and try to restart which is essentially what this fix does though it might not be enough to do it via device manager alone.
https://forums.frontier.co.uk/showthread.php?t=202726&p=3141204&viewfull=1#post3141204
That said, it might be worth trying before this fix, to go into your device manager, show hidden, and remove all displays that you can find entirely, and try to restart which is essentially what this fix does though it might not be enough to do it via device manager alone.
Thank you for the link Damian, Not sure I like the idea for messing with the registry though. I think ill just wait for elite to update to the latest sdk. Thanks again.
Hi rj16066, I am using the Nvidia 359.00 driver. @Damian, I did try the reg fix. I only found one file in there related to OVR0003 file, And deleted it. When I installed sdk05 it said that is not compatible with your system and will not be installed. I tried 06 and got the same. 07 installed fine. i am using windows 10.
Last edited:
I didn't bother using any switcher as elite is the only game I play. I have a shortcut on my desktop of 0.6 sdk set to run in compatible mode and set to run as administrator. I start computer turn of my headset the screen goes black the goes back to Windows. Next I run the shortcut give it a few seconds to load up and turn on the headset load elite works fine. Sorry if I'm not making myself very clear as I struggle with computers and jargon. The only thing I did was access the x86 file in the sdk 0.6 ticked the relevant boxes and made a shortcut
Windows 10 latest nvidia drivers ps you have to run the shortcut and leave it running and switch of headset every time you want to use dk2
rob
Windows 10 latest nvidia drivers ps you have to run the shortcut and leave it running and switch of headset every time you want to use dk2
rob
I did ignore the message. but i still get "NO HMD DETECTED, TRACKER CONNECTED" in the utility. No blue light on the tracker and amber light on hmd.
- - - - - Additional Content Posted / Auto Merge - - - - -
The dk2 is visible in the NVidia control panel. but not in windows.
Last edited:
Windows 10 isn't great when it comes to updates, in settings I've got mine set to refer, where only you can search for updates.
Last edited:
So i just found out the trick to switch runtime versions, and i was back in VR world but then made the stupid mistake of updating windows 
now runtime 5 is dead! runtime 8 works perfect, but not with Elite.
The only way i can get Elite working on the rift is by using Steam VR on runtime 8, but its terrible as it only runs at 60hz.
I have been raking forums and websites for a fix, but hitting dead ends.
Anyone found a workaround other than steam VR to get the runtime 5 working again with the new windows update?
I just hope the reddit masters find a cure soon, as i am back to playing Elite with this primitive thing called a ''LCD Monitor'' and it's hard to enjoy the game as much.
now runtime 5 is dead! runtime 8 works perfect, but not with Elite.The only way i can get Elite working on the rift is by using Steam VR on runtime 8, but its terrible as it only runs at 60hz.
I have been raking forums and websites for a fix, but hitting dead ends.
Anyone found a workaround other than steam VR to get the runtime 5 working again with the new windows update?
I just hope the reddit masters find a cure soon, as i am back to playing Elite with this primitive thing called a ''LCD Monitor'' and it's hard to enjoy the game as much.
At the moment, yes that does seem to be the only option to get a smooth flawless VR experience with ED, but i cant bring myself to use that method of brutality just for one game, and sacrifice all my other VR games when there could be a fix or workaround tomorrow.
The other method is to roll back the Windows 10 update, unfortunately its not an option for me as i have deleted the rollback to save space.
Going to give it a try with a few more attempts using Steam VR on 0.8 runtime.
Some posts on here claim to have it running fine at 75hz even using a 60hz screen. (Sceptical)
!!!!!RESULT!!!!
Ok.
I turned off DSR in the nvidia control panel to allow me to make a custom resolution.
Set my resolution to 1280x768
Refresh Rate set to 75Hz
and for the timing i changed from automatic to GTF and saved the custom resolution.
Launched ED while steam VR is active
in game graphics options set 3D to HMD (headphones)
BANG! 75fps, ultra graphic settings, and not a single flicker or judder (until i fist punched the air)
it's not as smooth as it was using the extended mode with the 5 runtime drivers, but the difference is hardly enough to make a fuss over.
The other method is to roll back the Windows 10 update, unfortunately its not an option for me as i have deleted the rollback to save space.
Going to give it a try with a few more attempts using Steam VR on 0.8 runtime.
Some posts on here claim to have it running fine at 75hz even using a 60hz screen. (Sceptical)
!!!!!RESULT!!!!
Ok.
I turned off DSR in the nvidia control panel to allow me to make a custom resolution.
Set my resolution to 1280x768
Refresh Rate set to 75Hz
and for the timing i changed from automatic to GTF and saved the custom resolution.
Launched ED while steam VR is active
in game graphics options set 3D to HMD (headphones)
BANG! 75fps, ultra graphic settings, and not a single flicker or judder (until i fist punched the air)
it's not as smooth as it was using the extended mode with the 5 runtime drivers, but the difference is hardly enough to make a fuss over.
Last edited:
If you have a problem using the Switcher v3 for windows 10 with the last update... here is the solution!
-Go to Switch 0.5
-Go to device administrator
-Show monitors
-Right click on Oculus DK2 and uninstall
-Check the square of unisntall software
Try to close and open the device and it will work!!!!! ( or make a extended mode for DK2 )
The solution that i was searching !!!!!
Thanks to realovirtual.com
The best comunity in Spain of VR.
Now i can play ED with 0.5 with the update of windows.
-Go to Switch 0.5
-Go to device administrator
-Show monitors
-Right click on Oculus DK2 and uninstall
-Check the square of unisntall software
Try to close and open the device and it will work!!!!! ( or make a extended mode for DK2 )
The solution that i was searching !!!!!
Thanks to realovirtual.com
The best comunity in Spain of VR.
Now i can play ED with 0.5 with the update of windows.
Thanks for that, i might give it a try...
I'm using this method at the moment and its great so far, no messing around with switchers or extra files, just the latest updates and one small tweak to your monitor,
and for me at least, runs much better using steam VR and the 0.8 runtime.
i made a post about it here if anyone is interested. Good luck fellow Commanders
https://forums.frontier.co.uk/showthread.php?t=215305&p=3295162#post3295162
Last edited: