cannot enter/exit/re-enter VR mode
Reported by
stephent...@gmail.com,
Apr 23 2018
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3404.0 Safari/537.36 Steps to reproduce the problem: 1. run https://webvr.info/samples/03-vr-presentation.html 2. enter VR (with button) 3. exit VR 4. re-enter VR What is the expected behavior? The app should redisplay on the headset What went wrong? The app does not redisplay on the headset WebStore page: https://webvr.info/samples/03-vr-presentation.html Did this work before? Yes not sure, will verify if I can easily Chrome version: 68.0.3404.0 Channel: canary OS Version: 10.0 Flash Version: Vive, 1080, SteamVR from 19 April
,
Apr 23 2018
,
Apr 24 2018
,
Apr 24 2018
,
Apr 24 2018
Thanks for filing the issue! As this issue is related to VR headset, which is not available at TE end to test and confirm the issue, hence adding TE-Hardware-Dependency label to it. Could someone from Blink>WebVR team to look into the issue and help in further triaging. Thanks!
,
Apr 24 2018
Bill, can you take a look?
,
Apr 24 2018
I've noticed this recently, as well. This did used to work, but I'm not sure what changed. Investigating
,
Apr 26 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/17c587b1b0dfc5f1df1963a70acc73cacb79403b commit 17c587b1b0dfc5f1df1963a70acc73cacb79403b Author: Bill Orr <billorr@chromium.org> Date: Thu Apr 26 03:27:05 2018 Fix reenter webvr presentation on Windows after exiting. We were getting into a state where we thought we had requested a vsync from the device, but actually haven't. This causes future RAFs to not run, and we won't render. BUG= 835888 Change-Id: I41af90675fa5ba8e6b78a598594f4a2cf28217ed Reviewed-on: https://chromium-review.googlesource.com/1028935 Reviewed-by: Bill Orr <billorr@chromium.org> Reviewed-by: Klaus Weidner <klausw@chromium.org> Commit-Queue: Bill Orr <billorr@chromium.org> Cr-Commit-Position: refs/heads/master@{#553888} [modify] https://crrev.com/17c587b1b0dfc5f1df1963a70acc73cacb79403b/device/vr/oculus/oculus_render_loop.cc [modify] https://crrev.com/17c587b1b0dfc5f1df1963a70acc73cacb79403b/device/vr/openvr/openvr_render_loop.cc [modify] https://crrev.com/17c587b1b0dfc5f1df1963a70acc73cacb79403b/third_party/blink/renderer/modules/vr/vr_display.cc
,
Apr 26 2018
,
Apr 27 2018
I confirm I see it fixed in Version 68.0.3410.0 (Official Build) canary (64-bit). Thank you
,
May 8 2018
,
May 10 2018
,
Jun 8 2018
Hi, I see this bug is affecting current stable channel M67. Is it possible to cherry-pick the fix to M67 so that we could use WebVR feature? Thanks.
,
Jun 8 2018
No, given that stable has already shipped and VR isn't very high usage (and still in origin trial), there's no chance that Chrome would do a stable re-spin for VR.
,
Jul 4
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by stephent...@gmail.com
, Apr 23 2018