New issue
Advanced search Search tips

Issue 714013 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Position reading is not relative to origin point for OpenVR device

Reported by ningxin...@intel.com, Apr 21 2017

Issue description

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

Steps to reproduce the problem:
0. Build chromium with 'enable_vr = true' and 'enable_openvr = true'
1. Launch chromium on a Windows PC with HTC Vive
2. Navigate to https://webvr.info/samples/https://webvr.info/samples/01-vr-input.html

What is the expected behavior?
According to WebVR 1.1 spec https://w3c.github.io/webvr/spec/1.1/#dom-vrpose-position, "Position is given in meters from an origin point, which is either the position the sensor was first read at or the position of the sensor at the point that resetPose() was last called. ".

What went wrong?
The position reading is relative to floor (chaperone soft bounds).

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 60.0.3077.0  Channel: n/a
OS Version: 10.0
Flash Version:
 
Project Member

Comment 1 by bugdroid1@chromium.org, Apr 22 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7939eef0d1684481aaa1bbf96509eac432efdfd1

commit 7939eef0d1684481aaa1bbf96509eac432efdfd1
Author: ningxin.hu <ningxin.hu@intel.com>
Date: Sat Apr 22 19:26:57 2017

Read poses relative to the seated zero pose for OpenVR

BUG= 714013 

Review-Url: https://codereview.chromium.org/2829233003
Cr-Commit-Position: refs/heads/master@{#466549}

[modify] https://crrev.com/7939eef0d1684481aaa1bbf96509eac432efdfd1/device/vr/openvr/openvr_device.cc

Labels: Needs-Triage-M60
Labels: TE-NeedsTriageHelp
Labels: Proj-VR VR-Desktop
Owner: cjgrant@chromium.org
Status: Assigned (was: Unconfirmed)
Ningxin, one more bug to ask you about.  This also looks fixed.  There may be more.  Can you confirm fixed via comment, or mark it Fixed?  If not, please let me know.
Status: Fixed (was: Assigned)
Ningxin, I'm batch-closing this bug as it appears you committed a fix.  If the bug was intentionally kept open, please let me know, and feel free to re-open.  Thanks!
Components: Blink>WebXR

Sign in to add a comment