You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(not sure if this is the right location for this ticket so please inform me if it needs to be moved)
I am encountering difficulty in implementing HTC Vive Trackers in the current WebVR 1.1 standard. I'm curious how this is proposed to be supported in WebXR.
Here are the issues:
WebVR 1.1 browsers appear to expose controllers (and trackers) as an array accessible through Navigator.getGamepads()
There is inconsistency with how WebVR 1.1 browsers expose the trackers:
-- Firefox sometimes exposes them, sometimes they are assigned handedness, sometimes not, unclear pattern to this behavior
-- Exokit only explicitly exposes vive wands, does not expose trackers (related ticket SteamVR tracker support exokitxr/exokit#884)
-- Supermedium has similar behavior to Firefox
WebVR 1.1 browsers do NOT appear to pass the controller "role" that is set by the end-user using the new SteamVR Input Mapping configuration, making it impossible for WebVR applications to use specific trackers with reliability aside from random and/or rewriting a temporary mapping tool within the web application.
The ask for WebXR spec is to expose "role" that controllers may have as determined by SteamVR that allow targeting specific trackers from a web application.
The text was updated successfully, but these errors were encountered:
kfarr
changed the title
HTC Vive Tracker support - v2.0
HTC Vive Tracker support
Apr 3, 2019
kfarr
changed the title
HTC Vive Tracker support
SteamVR Tracker support
Apr 3, 2019
To help figure out how to map this, here are the possible values for controller "role" currently accessible from Unity using official SteamVR component:
There is still ongoing debate about how this should be handled at the SteamVR/OpenVR layer: ValveSoftware/openvr#962
(not sure if this is the right location for this ticket so please inform me if it needs to be moved)
I am encountering difficulty in implementing HTC Vive Trackers in the current WebVR 1.1 standard. I'm curious how this is proposed to be supported in WebXR.
Here are the issues:
Navigator.getGamepads()
-- Firefox sometimes exposes them, sometimes they are assigned handedness, sometimes not, unclear pattern to this behavior
-- Exokit only explicitly exposes vive wands, does not expose trackers (related ticket SteamVR tracker support exokitxr/exokit#884)
-- Supermedium has similar behavior to Firefox
The ask for WebXR spec is to expose "role" that controllers may have as determined by SteamVR that allow targeting specific trackers from a web application.
The text was updated successfully, but these errors were encountered: