Interfering software is preventing the Rift from activating

[tozz3r]

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?

[LanePizza]

"wadeb" wrote:
On Windows 10 build 10041, SDK 4.4, I initially had this error message:

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

Updating to the latest AMD Beta driver, amd-catalyst-15.3beta-64bit-win8.1-mar20.exe, resolved the issue.

I had the exact same problem. Thanks for the fix!

[Lhun]

this isn't a fix, this is a downgrade.

the new driver is WDDM 2.0, and hopefully we can use it

[zqy]

For AMD Catalyst Control Center users, the best way I found up to now is to set the Rift application to "power saving" in the Switchable Graphics Application Settings panel.

[PeterJGalbraith]

I just solved this for myself an hour ago.

For me, the issue was solved by upgrading to the latest runtime (at the time of this posting that is the 0.6.0.0-beta runtime) and, more importantly, making sure your "Main Display" is a display on the same video card as the Oculus.

For me the fix was as simple as changing my main display to a different monitor, stopping the runtime service (via the menu in the configuration) and restarting the service.

It appears that the Oculus was being read via the SLI bridge as a device, and would thus not trigger the error logging, but would fail to display anything because it was on a different card. It looks like the software bases it's search for the Rift (when in Direct to HMD mode) off of whichever monitor Windows marks as the "Main Display".

Hope this helps.

[Soumen]

"PeterJGalbraith" wrote:

For me the fix was as simple as changing my main display to a different monitor, stopping the runtime service (via the menu in the configuration) and restarting the service.

It appears that the Oculus was being read via the SLI bridge as a device, and would thus not trigger the error logging, but would fail to display anything because it was on a different card. It looks like the software bases it's search for the Rift (when in Direct to HMD mode) off of whichever monitor Windows marks as the "Main Display".

Can you elaborate on this please? how to change the main display?

[cybereality]

In the Windows display settings. There is a button that says "make this my primary display".

[PawelMorawian]

Hello,

I have a ASUS laptot running with windows 8.1.
There are 2 graphic cards, an intel graphic and a nvdia.

I cannot get my dk1 work on it in direct mode.
I need it in direct mode because i have to give a presentation and people need to see what is going on.

I tried to desactivate intel graphic but i was not working.

I installed almost all drivers oculus and none is working.

Thank you !

[cybereality]

Optimus laptops are not supported. Very sorry.

[arturturkot]

Hi 🙂
The approach from Oculus team is really disappointing in my opinion...
I would understand that nonsupporting some devices that are really old is fair enough.... but providing new runtimes that do not work with the DK2 on new laptops or made your DK2 stop working because you (Oculus) are not able to handle graphic card settings (lack of knowledge, laziness, costs of that handling - whatever) is more silly and IMHO unprofessional.

If you do not know how to do it, just provide the src for others.... I am not really dedicated for Oculus development, but I buy DK2 and made some test.... Right now I feel more like 'cheated' to do more work for you with testing, which of your runtime will work with me pc, laptop and combination of graphic cards I have there, then really do some tests about DK2 itself, you are not professionals anymore in my opinion.

With regards
Artur