New issue
Advanced search Search tips

Issue 725431 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Proj-XR



Sign in to add a comment

WebVR scene is has tracking lag when viewed in Daydream

Reported by pookageh...@gmail.com, May 23 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. Visit https://s3-eu-west-1.amazonaws.com/luke-testing/trailered/test.html on a Pixel phone.
2. Tap the cardboard / enter-vr button
3. Place the device into a Daydream
4. Look Around

What is the expected behavior?
Smooth scene playblack without tracking / rendering lag.

What went wrong?
The framerate drops to ~4fps, and when the user looks around there is a delay before the scene re-renders.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 10.0
Flash Version: 

This works fine in 'cardboard mode' as can be seen by testing on any non-daydream device. It has been suggested that this could be due to a problem with Asynchronous Reprojection.
 

Comment 1 by hdodda@chromium.org, May 24 2017

Labels: -OS-Windows OS-Android
I'm unable to reproduce on Stable due to running into browser crash when entering VR. However, everything seems to be working fine on Beta and Canary - can you try one of those and see if the issue has already been fixed?
Still happening on stable when using Chrome 58.0.3029.83, Android 7.1.2, Pixel XL Build/N2G470.  Can also use https://aframe.io/examples/showcase/helloworld/ as an example to test.

Unable to test with Chrome Beta, as Daydream mode is not triggered when the enter-vr button is pressed, and when the device is placed into the DD it goes to the DD home rather than continuing on the original website.

Comment 4 by klausw@chromium.org, May 30 2017

Not entering VR mode would be expected if the site does not have a correct origin trial token configured. You need a new token for M59 and above. The M58 one no longer applies to those versions, and it may also have expired depending on when it was issued.

To test, try entering "navigator.getVRDisplays" in the inspector's JS console, it should show "native code" if the extension is present. Alternatively, try enabling WebVR and Gamepad API in chrome://flags to override the origin trial token check.
Labels: Proj-VR
pookagehayes@, Are you able to determine if this is still a problem?
@cjgrant - Just tested on version 59.0.3071.125 and issue appears to be fixed. Thanks all.
Status: WontFix (was: Unconfirmed)
Excellent!  Thanks for re-checking!  I'll close this off.
Components: Blink>WebXR

Sign in to add a comment