WebVR presentation is headlocked for two seconds when started automatically by placing device into daydream headset |
|||||||
Issue descriptionChrome Version: 60.0.3107.3 OS: (e.g. Win7, OSX 10.9.5, etc...) VR Services: 1.6.156467194 Platform: Pixel, Pixel XL Daydream version: 1.5.170411053 What steps will reproduce the problem? (1) With Daydream as default headset, go to https://webvr.info/samples/03-vr-presentation.html (2) Place phone in headset (3) Follow DON flow then start moving head around in presentation mode What is the expected result? Content in presentation mode does not freeze with head movement.
,
Jun 1 2017
dbbrooks@, does this still repro for you, and how often? I didn't see a freeze in ~10 insertions using Michael's test build from yesterday.
,
Jun 2 2017
Now it seems to freeze, then unfreeze. I'd say 1/4 times approx. 60.0.3112.10
,
Jun 6 2017
Now it'll freeze every time if presentation is triggered automatically by placing device into headset. But the freeze only lasts for a second or two. Chrome: 61.0.3122.0 VR Services: 1.6.156467194 Device: Pixel XL
,
Jun 7 2017
klausw, are you working on this?
,
Jun 12 2017
I'm able to reproduce this issue on Beta 60.0.3112.30, Pixel XL, Android N Repro steps: 1. Open https://webvr.info/samples/03-vr-presentation.html, don't tap "Enter VR" button 2. Insert device into the headset to autostart presentation 3. Wear the headset 4. Calibrate controller (pass DON flow) => Presentation is started automatically but it doesn't respond to the head movement for 1-2 seconds
,
Jun 26 2017
This still repros in 60.0.3112.43 and 61.0.3141.0 - every time. The scene appears to move correctly for a fraction of a second before becoming headlocked for a couple seconds. The orbiting box continues to move, so presentation is not actually frozen.
,
Jun 26 2017
Just to confirm, it works fine when clicking the Enter VR button.
,
Jun 27 2017
When I first encountered this in 61.0.3141.0, the floating boxes were blurry even after the initial issue. I'm not sure if that's related or what caused it.
,
Jul 10 2017
Any update on this?
,
Jul 19 2017
I'm unable to repro on 61.0.3161.4 (recent Canary), or recent ToT. Daydream version 1.7.161000338. Reassigning to vsupruniuk to check if he is still able to repro.
,
Jul 19 2017
I'm like 95% confident this was fixed by https://codereview.chromium.org/2941173002/ I saw this issue a lot when I was testing the CL and got things wrong.
,
Aug 10 2017
verified in 62.0.3178.0
,
Jul 4
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by klausw@chromium.org
, May 25 2017Owner: klausw@chromium.org
Status: Assigned (was: Untriaged)