Pause VR/AR runtime tracking when no associated frame is able to receive poses/data |
||||||||||||||
Issue descriptionIt is possible for there to be XRDevices and XRSessions that are/can not receive poses or other frame data. For example, because their frame does not have focus (issue 845283). We should pause the runtime's tracking functionality (and maybe other functionality) to avoid wasting battery, CPU, etc. VRDisplayHost, VRDeviceBase, or VRDeviceBase could track this and call VRDevice's PauseTracking()/ResumeTracking() as appropriate. However, we also need to consider non-WebXR uses such as browsing. ⛆ |
|
|
,
Jun 7 2018
Note that we may want to make accomodations for a better user experience (issue 850283).
,
Jul 4
,
Jul 4
,
Aug 7
Removing Blink>WebVR component and assigning to Blink>WebXR
,
Aug 7
Removing Blink>WebVR component and assigning to Blink>WebXR
,
Aug 7
,
Aug 7
Removing Internals>VR component and assigning to Internals>XR
,
Aug 7
,
Sep 4
,
Sep 4
,
Sep 14
@lincolnfrog : is this already "fixed" (did ijamardo@ already land something to fix this)? |
|||||||||||
►
Sign in to add a comment |
||||||||||||||
Comment 1 by ddorwin@chromium.org
, May 26 2018