Closed
Bug 1392027
Opened 8 years ago
Closed 8 years ago
[webvr] vive not working in latest nightly
Categories
(Core :: WebVR, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: trevorjbaron, Assigned: kip)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36
Steps to reproduce:
Opened nightly
Observed webvr worked using https://threejs.org/examples/webvr_cubes.html
Restarted nightly to get latest updates (57.0a1 (2017-08-19) (32-bit))
Tried https://threejs.org/examples/webvr_cubes.html again
Actual results:
Observed webVR supported but no VRDisplays found
Expected results:
Should work as it does in latest stable build
Updated•8 years ago
|
Component: Untriaged → WebVR
Product: Firefox → Core
| Reporter | ||
Comment 1•8 years ago
|
||
Still not working in 57.0a1 (2017-08-25) (32-bit)
| Assignee | ||
Comment 2•8 years ago
|
||
(In reply to trevorjbaron from comment #1)
> Still not working in 57.0a1 (2017-08-25) (32-bit)
WebVR is now only enabled for 64-bit builds.
Could you try updating to a 64-bit build and see if it fixes it?
Please note that a different regression in Nightly and Beta will cause corruption of the display on your 2d monitor while in VR in Nightly and Beta (Release is not affected). You can work around this with a preference change:
layers.mlgpu.dev-enabled = false
When Bug 1381085 lands soon, you won't need this extra preference.
If you really need to stay on the 32-bit build, you can also manually enable WebVR still:
dom.vr.openvr.enabled = true
dom.vr.oculus.enabled = true
| Assignee | ||
Updated•8 years ago
|
Assignee: nobody → kgilbert
| Reporter | ||
Comment 3•8 years ago
|
||
Thanks, 64 bit works. Verified on 57.0a1 (2017-08-28) (64-bit)
Comment 4•8 years ago
|
||
(In reply to trevorjbaron from comment #3)
> Thanks, 64 bit works. Verified on 57.0a1 (2017-08-28) (64-bit)
After
dom.vr.openvr.enabled = true
dom.vr.oculus.enabled = true
Does it fix the problem on FF 32 bit?
| Assignee | ||
Comment 5•8 years ago
|
||
I think we can close this one. If you have any further problems, please reach out again!
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•