Windows 10 "Threshold 2" update broke the 0.5 Oculus runtime

rohirm

R
Hi,

Yesterday I installed the latest updates for Windows 10, after that the 0.5 runtime does not work anymore. I have reinstalled all of the drivers (Oculus, NVIDIA), but no luck.

With 0.5 it doesn't show the secondary (DK2) desktop in the extended mode. In NVIDIA control panel it shows the DK2 in the "Setup multiple displays" page, but it always resets the checkbox back to unchecked when trying to enable it (after pressing the apply button).

Version 0.8 works just fine. Anyone else with the same problem? Any ideas how to try to fix this?
I hope ED will be updated for 0.8 soon..
 
Last edited:

thafred

thafred
Same Problem here, sucks bigtime doesn´t it... I had a friend over on friday, after updating to 1511 to play a little Assetto Corsa on DK2 and somehow got it working. Just figured out what I did since I broke it again today trying to get SDK switcher to work...

- switch off Oculus Rift
- Uninstall 0.8 (or any currently installed) Firmware
- Install Nvidia driver 350.12 (the last windows 8.1 driver on my hdd. all the windows 10 drivers don´t seem to work anymore)
- you can now access the DK2 as extended Desktop
- install SDK 0.5.0.1

i tried updating to newest nvidia driver but it broke again. So don´t Update gpu driver unless you plan to switch to sdk 0.8. maybe someone has an idea, sucks to be stuck with such an old driver!
 
Last edited:

thafred

thafred
El_Labero said:
hmm, for me it works... forget the oculus installer & use the runtime switcher v3
Click to expand...

No use for me. The rift just stays in orange mode as Windows doesn't recognise it as a monitor. You have a nvidia gpu and updated windows to 1511 (threshold 2 update)?
 
Last edited:

El_Labero

El_Labero
yes i use, are you sure you followed the instruction correctly?
Of course win doesn´t recognise the rift as a monitor, the direct mode without extended mode is the main feature of 0.7 (does nobody read the changelog? ) ^^ if the Demo works everything is ok.And than you just have to follow the readme and erverything is ok.

you simply install the 0.7 or the 0.8 runtime, put the files in the proper folder an everything works out of the box
 
Last edited:

thafred

thafred
El_Labero said:
yes i use, are you sure you followed the instruction correctly?
Of course win doesn´t recognise the rift as a monitor, the direct mode without extended mode is the main feature of 0.7 (does nobody read the changelog? ) ^^ if the Demo works everything is ok.And than you just have to follow the readme and erverything is ok.

you simply install the 0.7 or the 0.8 runtime, put the files in the proper folder an everything works out of the box
Click to expand...

I am so glad it works for you but that doesn´t change the fact that it doesn´t work on my and OP´s PC. I had Runtime switcher running perfectly on Windows 10 before 1511
Runtime switcher V3 is just a few command lines and I´m perfectly aware of all SDK features, accusing me of beeing stupid and not reading the changelog is just ing anoying and doesn´t help at all.
 

ZZZRonin

Z
I don't know if it can help, this troubleshooting work for me when I have some problem with the Oculus in Extended Mode : In Task Manager, kill 2 Oculus Process named "public TCID", be carefull not to kill the "OVR service" which have the same icon, public service will then restart by themself in a few seconds. Next, open Configuration Utility of the Oculus, power on your oculus, and setup it to direct mode, YOU MUST THEN TRY AT LEAST ONE TIME the Demo by selecting "Show Demo Scene" Button, if everything work well, close the demo and change to extended mode again to know if it work again.
 

duckutus

duckutus
Had the same problem here.... i removed the last update and disabled the windows update (via service.msc)
so... no updates for me until elite moves on to another sdk
 

Deimos-GOW

D
I don't know if this helps or not, I don't have any problems. I have not updated my nVidia drivers since the update, I updated just before installing the Windows 10 update, and my DK2 was on during the update.
 

Wolfox

Wolfox
I had it also on Win7, the problem is related to the option in the SDK to Turn Off Oculus rift, but doing this it disables all secondary screens of the Graphic card. only thing that work is the Test Scene.
After Changing Graphic card, Motherboard, CPU I thought I had a defected hardware. Had to uninstall GPU drivers, some how corrupted, and roll back to SDK 0.5.
The problem is not the latest GPU drivers, is the SDK.
Is also why I avoid the Switch 0.5->0.8
But who knows maybe you guys are having another issue
 

Malic

Malic
This is why I am using 6.0.1 on Win 10

I installed SDK 6.0.1, dragged a copy of the folder from the program files to the desktop, uninstalled and then followed all the instructions for that oculus switcher thing to get both SDK 5 and SDK 7.

So then my computer had SDK 5 and SDK 7 on it, then I just copied all the files from the 6.0.1 folder I had dragged to my desktop back into the SDK 5 folder that the switcher used.. the switcher is just looking at the folder and the folder paths, the names of the files in there are exactly the same but now I do not have anything from SDK 5 anywhere on the computer other then the folder name, which is all 6.0.1 files instead.

I use 6.0.1 specifically because win 10 broke the interceptor made for using the IPD adjusters, SDK 6.0.1 has a change that can be made in the Oculus server to edit the IPD of the lenses.
 

callezetter

C
Yeah I got some trouble getting 0.5 or 0.6 working after the treshold 2 update, here too. Haven tested that many GPU drivers yet tho, so that might be it.
 
Last edited:

RevEm

RevEm
Thank you Pixelpowder, I'm not sure of the drivers for my nvidia card I am using. But will try this when I get home from work tonight. And report back how I get on.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom