Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

perf of native WebVR API tracking degraded on Chrome for Android #255

Closed
cvan opened this issue Apr 21, 2018 · 0 comments
Closed

perf of native WebVR API tracking degraded on Chrome for Android #255

cvan opened this issue Apr 21, 2018 · 0 comments

Comments

@cvan
Copy link
Contributor

cvan commented Apr 21, 2018

reproduced in Chrome 65 on an Android Pixel 2 device:

  1. ensure that the WebVR flag is Enabled from chrome://flags#enable-webvr
  2. using Chrome on Android (current release: 65), navigate to the demo scene at https://mozilla.github.io/unity-webvr-export/ (or your localhost server)
  3. click the VR-icon button to enter VR mode.
  4. move your head around a ton, up and forth, left and right.
  5. notice the tracking is really lagged. the perf was noticeably better.

likely, this appears to be mostly caused the upgrade of the WebVR Polyfill in v1.1.0.

the actionable steps here are to test other WebVR content in Chrome for Android, and see if this is a platform regression or a regression in this project/repo. if it's the former, we should file Chromium bugs. if it's the latter, we should fix the issue in this project.

also, see this relevant issue for Polyfill issues with the new Sensor API: #254

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants