Position reading is not relative to origin point for OpenVR device
Reported by
ningxin...@intel.com,
Apr 21 2017
|
|||||||
Issue descriptionUserAgent: 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:
,
Apr 24 2017
,
Apr 25 2017
,
Jun 6 2017
,
Aug 10 2017
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.
,
Aug 11 2017
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!
,
Jul 4
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by bugdroid1@chromium.org
, Apr 22 2017