Oculus SDK2 no longer working

Hey everyone :)

I'm running Elite on a Razer Blade 14" (2014) and since upgrading my SSD I can't seem to get elite working with the rift any more, when I switch to rift mode I get this error in the background:

http://s22.postimg.org/apxjwjygh/Untitled.png

Can anyone provide some guidance with this error? I have everything installed the way I had before the format and after 6-8 hours battling with this I've hit nothing but dead ends :'(


Thanks in advance for any input into fixing this ^_^ if I can provide any additional information let me know
 
Nothing else works yet either but I did have other games working with it initially, I'm running firmware 2.12 on the rift and software version 4.1.3 but I cant think what could be causing the conflict.

If anything I have less clutter installed now than before but if it helps here is my dxdiag:

http://speedy.sh/NK2uB/DxDiag.txt
 
Last edited:
Nothing else works yet either but I did have other games working with it initially, I'm running firmware 2.12 on the rift and software version 4.1.3 but I cant think what could be causing the conflict.

If anything I have less clutter installed now than before but if it helps here is my dxdiag:

http://speedy.sh/NK2uB/DxDiag.txt

Have you set the DK2 in direct mode and tested some direct mode demos? To eliminate possible screen select issues. Does the tray tool see the RIFT?
 
I've only ever used my Oculus in direct mode, the built in demo to the oculus configuration utility (that also used to work) gives me the same error. I still get my laptop screen view and the tracking still seems to see me when I move with the rift on but I get nothing on the headset and the orange light doesn't go blue like it used to. I've seen people say they have problems with USB 3.0 and the Optimus Nvidia stuff but it worked previously on the same hardware and I have identical software to what I had on my old SSD, I'm just having a look now to see if Nvidia released a driver update in the past 2 weeks (since it was about 14-16 days ago when I last used Oculus with Elite before I upgraded my SSD).
 
I've only ever used my Oculus in direct mode, the built in demo to the oculus configuration utility (that also used to work) gives me the same error. I still get my laptop screen view and the tracking still seems to see me when I move with the rift on but I get nothing on the headset and the orange light doesn't go blue like it used to. I've seen people say they have problems with USB 3.0 and the Optimus Nvidia stuff but it worked previously on the same hardware and I have identical software to what I had on my old SSD, I'm just having a look now to see if Nvidia released a driver update in the past 2 weeks (since it was about 14-16 days ago when I last used Oculus with Elite before I upgraded my SSD).

This is what config I have:

Nvidia 344.65
Windows 8.1 update x64
USB 2 port used with the DK2, because I had read about those issues

So I guess you cannot run the IPD setup for example?

This is what my tool looks like when I turn my Rift off completely:

Capture.PNG
 
Looks the same to me, I have the same Nvidia driver as you (so that rules out a driver update breaking it) I have a small hunch that it might be something to do with a setting or settings I had previous manipulated in the Nvidia control panel. Prior to getting my Oculus I played with those settings a lot when Dead Rising 3 came out because the Optimus stuff was very broken so I could have inadvertently prevented this issue without realising it?
 
Looks the same to me, I have the same Nvidia driver as you (so that rules out a driver update breaking it) I have a small hunch that it might be something to do with a setting or settings I had previous manipulated in the Nvidia control panel. Prior to getting my Oculus I played with those settings a lot when Dead Rising 3 came out because the Optimus stuff was very broken so I could have inadvertently prevented this issue without realising it?

Well possibly but I think if you are getting the same picture I just showed above - No Device Attached - then that's something outside the scope of the NVidia control Panel options, which are more about software settings for apps. But when you go to Setup Multiple Displays in NV CPL, is 'Rift DK2' listed at all?

I dropped you a PM, feel free to email me and we can pick it up on email, swap settings if needed etc.

So I just fired up my Rift and get the image below:


Capture.PNG
 
Just noticed my last message didn't post, I misexplained that I had the same view as you when i start up the config tool with my rift disconnected. When its plugged in I have the same as your last post but when I load up the "Show demo scene" I get the window on desktop but nothing through the rift and thats when the error message pops up. It also comes up when I turn the 3d option on ingame.

But yeah I've replied to your pm and when I get home i'll be online most of the day and weekend so I really appreciate the time your taking to lend me a hand :)
 
Just noticed my last message didn't post, I misexplained that I had the same view as you when i start up the config tool with my rift disconnected. When its plugged in I have the same as your last post but when I load up the "Show demo scene" I get the window on desktop but nothing through the rift and thats when the error message pops up. It also comes up when I turn the 3d option on ingame.

But yeah I've replied to your pm and when I get home i'll be online most of the day and weekend so I really appreciate the time your taking to lend me a hand :)

No problem. Chat later, hope we can get it going :)
 
Defalt, just in case you haven't noticed, we now have a VR discussion area... https://forums.frontier.co.uk/forumdisplay.php?f=69

When I first got my DK2 I had loads of problems... the only way I got it working was a windows re-install - since then working no problem. It looks like that DLL is an NVidia file, I'd be tempted to use driver cleaner to remove the nvidia stuff and try a re-install if you haven't already.
 
Defalt, just in case you haven't noticed, we now have a VR discussion area... https://forums.frontier.co.uk/forumdisplay.php?f=69

When I first got my DK2 I had loads of problems... the only way I got it working was a windows re-install - since then working no problem. It looks like that DLL is an NVidia file, I'd be tempted to use driver cleaner to remove the nvidia stuff and try a re-install if you haven't already.

Good plan, i'll add that on my list of stuff to try when I get home :) Sorry to post in the wrong section, if a mod/admin can move it for me I'd appreciate it :)
 
Recently my Rift does not detect unless I disconnect both USB and HDMI cables from it, then plug it back. Maybe worth trying.
 
Get the graphics driver uninstaller from http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Uninstall the Oculus software, do not reboot
Uninstall the NVidia drivers, reboot into safe mode
Run the driver uninstaller
Reboot into Windows Normal mode

Re-download and install current Nvidia driver and reboot
Re-download and install current Oculus SDK and reboot


After that, you should be good.

I assume by SDK you mean runtime? I cant find anything install'able from the SDK download.


Edit: After following that process if using runtime I try to play the Demo Scene, it dies
View attachment 1462

Elite gives me this
View attachment 1463
 
Last edited:
Just the runtime unless you're a developer.

Also make sure you have the 2010 and 2012 visual c++ redistributables installed (both x86 and x64).. you can get them:

http://www.microsoft.com/en-us/download/details.aspx?id=5555
http://www.microsoft.com/en-us/download/details.aspx?id=30679

I'll grab them now, would windows update not pick those up? Just curious but I'll grab them now :)

Edit: Same result as my last post :( Thank you for all the support so far, I can only presume that its something incorrectly configured in the Nvidia control panel >_< based on the error
 
Last edited:
Recently my Rift does not detect unless I disconnect both USB and HDMI cables from it, then plug it back. Maybe worth trying.

It's not that it isn't detected but complaining something is conflicting with it trying to initialize :(
 
Back
Top Bottom