Sorry, firefox.exe/chrome.exe is taking a while to load | (unresponsive) firefox.exe/chrome.exe

Question

I'm making an application with WebVR using React VR. I'll test the application with my Oculus Rift and HTC-Vive. I'm using the browser Firefox Nightly to access the WebVR API's.

If I browse to my application using Firefox Nightly or Chromium, I arrive in an empty space with a loading message. A few seconds later I got this message on my Oculus Rift:

Sorry, firefox.exe/chrome.exe is taking a while to load. If this issue persists, please take off your headset and check this app on your computer.

On the HTC-Vive I got this message in Steam VR but it doesn't load at all.

(unresponsive) firefox.exe/chrome.exe

In the webbrouwser, I got the result I must see inside the headset with motion tracking.

I'm using this browsers

• Version Firefox nightly: 55.0a1
• Version Chromium: 56.0.2910.0

And this are my specifications:

• GeForce: GTX 970
• GeForce Game Ready Driver: 378.66
• Processor: Intel^® Core™ i7-6700 CPU @ 3.40GHz
• RAM: 15.87 GB

Answer 1

Downgrading my Nvidia driver to 376 worked as a charm for me, but I can't run the VR scenes on Nightly, just on Chromium.

Answer 2

1. Try installing SteamVR. SteamVR overrides the Oculus runtime and runs applications on its own.
2. Try closing Oculus Home before you launch your WebVR application using the WebVR button.
3. Make sure you are not in the Beta/Dash mode in Oculus 
4. Try to disable the auto-opening of Oculus Home. Oculus home opens automatically on wearing the rift. To disable, select “Run as admin” field in the properties of the Oculus app. More specifically, go to /Oculus-Directory/Support/oculus-client/OculusClient, right click, select properties, check “Run as Administrator”.
5. Make sure that your Desktop and Rift are connected to the same Graphic card. You might need an HDMI to DVI converter for the same. This is what fixed the problem for me.

Answer 3

I was able to get my Oculus to work with WebVR by enabling the Beta channel within the oculus app and letting it install an update. Seems like the current Oculus version might be broken.

Answer 4

This isn't the Oculus software at all. The problem is an NVIDIA driver update that broke everything. You need to go to the NVIDIA site and download drivers from the "376" generation (Dec'16-Feb'17). Install those and the problems go away. I confirmed that things are working with Oculus 1.12, 1.14, and 1.14 beta channel.

It looked like Oculus broke things because 1.14 came out on almost the same day as the "381" NVidia driver update.