New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 847273 link

Starred by 3 users
Status: ExternalDependency
Owner: ----
Cc:
bajones@chromium.org
tiborg@chromium.org
█ gordonbrander@chromium.org
cjgrant@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

VR: Chrome controller arm model doesn't match Daydream arm model

Project Member Reported by mthiesse@chromium.org, May 28 2018 
Our controller position and laser ergo angle offset don't match the daydream controller implementation.

You can see this easily by switching between Dashboard and Chrome. The offset is ~2 omnibox heights (sorry, no banana-based scales here), making it significantly harder to target the elements near the bottom of the UI.

Comment 1 by acondor@chromium.org, Jun 15 2018

Owner: acondor@chromium.org
Status: Started (was: Available)

Comment 2 by acondor@chromium.org, Jun 25 2018

Status: Available (was: Started)
I checked the math and constants, but didn't find anything that might cause this. Although, my perception is that Dashboard has a wider field of view than Chrome. Am I the only one seeing this?

Comment 3 by acondor@chromium.org, Jul 3

Labels: Restrict-View-Google
Status: ExternalDependency (was: Available)
Filled b/111120602

Comment 4 by mthiesse@chromium.org, Jul 3

Labels: -Restrict-View-Google
No need to RVG for a b/ link.

Comment 5 by tiborg@chromium.org, Aug 23

Labels: -M-68
Removing milestone since that won't go in for M68. Aldo, consider also decreasing the priority because that doesn't seem critical.

Comment 6 by acondor@chromium.org, Aug 23

Labels: -Pri-1 Pri-3

Comment 7 by acondor@chromium.org, Oct 4

Cc: bajones@chromium.org
Owner: ----

Comment 8 by samdrazin@chromium.org, Today (14 hours ago)

Labels: VR-B-Input
►

Sign in to add a comment