New issue
Advanced search Search tips

Issue 704690 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

Optimize controller input latency for gamepad API and UI handling

Project Member Reported by cjgrant@chromium.org, Mar 23 2017

Issue description

Controller input must be read from the controller once, then shared with both the Gamepad API and VR UI.

Originally, the controller was read in DrawFrame(). Then, reading was moved to be closer to WebVR frame processing, but this caused DrawFrame to miss (or see duplicate) button events periodically, so controller reading (may) return to DrawFrame().

If we want to read controller state in sync with WebVR frames, we need to queue controller events to the UI, so that it doesn't miss anything.
 
Status: WontFix (was: Available)

Sign in to add a comment