State and events for interstitial/warning screens about webxr HOT 3 CLOSED

Comment by toji
Thursday May 19, 2016 at 05:44 GMT

For the Oculus SDK I believe that any time the app isn't showing what it's rendering (whether due to the HSW or Unknown Sources screen or because Oculus Home is visible) ovr_SubmitFrame will return ovrSuccess_NotVisible. Not terribly granular, but it gives us something to work with. My first thought would be to not resolve the requestPresent promise until this starts returning ovrSuccess. (And have it submit dummy frames periodically in the background till then to test.) Maybe if it starts returning that after requestPresent has resolved we could knock down the rate that VRDisplay.requestAnimationFrame is called at to avoid spinning our wheels unnecessarily.

Same could go for the polyfill. Don't resolve the promise until the interstitial is ready to disappear.

from webxr.

Comment by brianchirls
Thursday May 19, 2016 at 12:34 GMT

Sounds like a good start. I don't think slowing the frame rate is sufficient, since you may want to fully pause the experience. But we could start with this and then add in additional state and events later on if the need arises. Right?

from webxr.

This issue was moved to immersive-web/webvr#27

from webxr.