Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

Web VR not working - sound but no picture

  • 2 个回答
  • 1 人有此问题
  • 6 次查看
  • 最后回复者为 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

由mark6139于修改

所有回复 (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.

由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).