Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Web VR not working - sound but no picture

  • 2 uphendule
  • 1 inale nkinga
  • 12 views
  • Igcine ukuphendulwa ngu mark6139

more options

Trying to view Web VR in FF 58.0.1 on Windows 10.

Running with Occulus Rift CV1 and having not issues running Oculus Home or Steam VR.

When I launch web VR content, I hear just sound and otherwise my VR environment remains in Oculus Home.

Any suggestions?

UPDATE: I think I fixed it. I have a Acer Helios 300 and Firefox defaulted to using the integrated graphics. I switched it to the Nvidia card in the Nvidia Control Panel

Trying to view Web VR in FF 58.0.1 on Windows 10. Running with Occulus Rift CV1 and having not issues running Oculus Home or Steam VR. When I launch web VR content, I hear just sound and otherwise my VR environment remains in Oculus Home. Any suggestions? UPDATE: I think I fixed it. I have a Acer Helios 300 and Firefox defaulted to using the integrated graphics. I switched it to the Nvidia card in the Nvidia Control Panel

Okulungisiwe ngu mark6139

All Replies (2)

more options

So the problem wasn't FF and it's good you found the culprit. If I read this before you responded I would've said iGPU can't do VR and need the most update date dedicated Nvidia 1060 or higher GPU to do VR.

Okulungisiwe ngu WestEnd

more options

If you had responded with that I would have replied that I do have an Nvidia 1060 or higher and that more importantly I would have repeated what I said in my post that I have no problems running VR via other apps.

It is apparent that Oculus Home, Steam, and apps running under them are able to use the Nvidia card without having to specify that in Nvidia control panel. If FF cannot do this there should at least be some more prominent way to instruct the user on the fix because I think this will be a common problem as more people try to use Web VR in FF (there is one support snippet that mentions this but it isn't necessarily easy to find).