Closed
Bug 1242967
Opened 9 years ago
Closed 9 years ago
VR HMDs should create their own VsyncSource; widget/etc. should keep track and switch to listening to them
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: vlad, Assigned: vlad)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: feature, Whiteboard: [webvr])
Attachments
(1 file)
With new vsync work in bug 1184283, widget can switch which source of vsync it listens to. It should know to switch to a HMD vsync source when the user is using a HMD.
Assignee | ||
Comment 1•9 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/32645/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/32645/
Attachment #8712787 -
Flags: review?(kgilbert)
Comment 2•9 years ago
|
||
Comment on attachment 8712787 [details]
MozReview Request: Bug 1242967 - VR HMDs should create their own VsyncSource, and notify widget when necessary
https://reviewboard.mozilla.org/r/32645/#review29513
This all looks good to me, thanks!
Attachment #8712787 -
Flags: review?(kgilbert) → review+
Comment 3•9 years ago
|
||
This is no longer necessary with the WebVR 1.0 implementation, as new VR hardware APIs are not vsync based.
Bug 1250244 (WebVR 1.0 Implementation) includes separate requestAnimationFrame callbacks for each VRDevice that request frames with the correct timing for the VR hardware.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•