cancel
Showing results for 
Search instead for 
Did you mean: 

Interfering software is preventing the Rift from activating

tozz3r
Explorer
I'm trying to run the Demo Scene in the utility with the Rift Display Mode set to Direct HMD Access.
Running Windows 8.1.
Rift Firmware 2.12
Rift Runtime 4.3

Error:
There is a problem with your Rift configuration.
Interfering software is preventing the Rift from activating. Loaded UMD is reported as 'nvwgf2um.dll'.

Anyone else?
48 REPLIES 48

scalto
Honored Guest
well, got win 8.1 pro, nvidia 344.48 driver installed, 2x gtx 590, quad sli enabled, 2 displays working with 1st card and oculus plugged into 2nd card to dvi interface, getting same error, any solution?

brg,
PJ

ken1256
Honored Guest
HI,I got the same error. i just receive my dk2 yesterday.

GTX880M,

tozz3r
Explorer
"scalto" wrote:
well, got win 8.1 pro, nvidia 344.48 driver installed, 2x gtx 590, quad sli enabled, 2 displays working with 1st card and oculus plugged into 2nd card to dvi interface, getting same error, any solution?

brg,
PJ


Nothing yet. I've emailed support, but they haven't responded.

darkiq
Honored Guest
I had a lot of problems with demo's running 4.3. I uninstall 4.3, install 4.2 and everything seems to work fine now.As for regular issues getting direct to rift working, I usually set my rift display mode to "direct HMD access", and use a program called "VR_Game_Manager - By Bilago" to force the demo to run in directx 11 mode. This usually takes care of most of my issues. Everything else seems to need extended mode to work. Hope that helps 😄

Stjohn909
Honored Guest
Same issue here. 0.4.3 downloaded on Nov 2

tmason101
Honored Guest
"darkiq" wrote:
I had a lot of problems with demo's running 4.3. I uninstall 4.3, install 4.2 and everything seems to work fine now.As for regular issues getting direct to rift working, I usually set my rift display mode to "direct HMD access", and use a program called "VR_Game_Manager - By Bilago" to force the demo to run in directx 11 mode. This usually takes care of most of my issues. Everything else seems to need extended mode to work. Hope that helps 😄


Thanks for the info. Good to at least have a work-around for some projects.

Now we need Oculus to come up with a "Direct" to Rift fix for OpenGL that is solid.

Hopefully with many more people highlighting this issue we can get an engineer's response that points to a resolution.

loosche
Honored Guest
I had the same problem, old card (NVidia GTX580), latest drivers, latest runtime (0.4.3) and it was due to "too many monitors".

I disabled one of my screens and the DK2 started working again.

HartLabs
Honored Guest
I am getting this message in my C++/OpenGL project when I try to launch in direct mode with mirroring disabled. Enabling mirroring fixes it, extended fixes it.

cybereality
Grand Champion
Can you guys try disabling SLI, Surround, and unplugging any extra monitors (one monitor should be OK)?

Especially with SLI, the video ports you use on the GPUs will make a difference.

HartLabs
Honored Guest
Dual GPU laptop no SLI, no external monitors (primary laptop screen only), C++/OpenGL, with the mirroring disabled. Camera LED turns blue, HMD stays orange, get the crash. I might be a special cause though as I am in OpenGL and am having other problems with direct mode as well. I figured more info may help troubleshoot though.