aframe icon indicating copy to clipboard operation
aframe copied to clipboard

tracked-controls v1.x - only one controller (id:0) is connected

Open smeybi opened this issue 4 years ago • 8 comments

Only one controller is assigned. Both tracked-controls (left/right- 0/1) are assigned to the left(0) vive controller. I think the property "controller" doesn't work. In v0.9.2 works fine.

  • A-Frame Version: 1.x
  • Platform / Device: Vive Firefox/Supermedium
  • Reproducible Code Snippet or URL:

<a-entity tracked-controls="controller: 0; idPrefix: OpenVR"></a-entity> <a-entity tracked-controls="controller: 1; idPrefix: OpenVR"></a-entity>

https://glitch.com/~aframe-tracked-controls-demo

smeybi avatar Jun 07 '20 13:06 smeybi

Use vendor specific controls vive-controls, oculus-touch-controls... All controllers are supported

dmarcos avatar Jun 08 '20 15:06 dmarcos

I used it for the Vive Tracker. There is something for the vive tracker?

smeybi avatar Jun 08 '20 15:06 smeybi

@smeybi I'm trying to do the same, did you find any solution for this? Thanks

jquery404 avatar Nov 23 '21 02:11 jquery404

Not sure if trackers are supported on Chrome / WebXR. I don't find a profile

@toji Do you know if Chrome supports Vive trackers at the moment? Thanks.

dmarcos avatar Nov 23 '21 03:11 dmarcos

@jquery404 I haven't found a solution. I haven't tested in a long time. I will try the tracker today and see if it works again and let me know.

smeybi avatar Nov 23 '21 12:11 smeybi

I have tested it with Aframe 1.2.0 The tracked-controls are for WebVR (Gamepad API) and do not support the Vive Trackers anymore (they used to have it) in Firefox. WebXR doesn't support the Gamepad API. I have checked the inputSources (document.querySelector("a-scene" ).xrSession.inputSources) in Chrome and only the Vive controllers are listed. I assume the Vive Trackers are not yet supported in Chrome.

smeybi avatar Nov 24 '21 00:11 smeybi

Chrome use OpenXR on Windows, which means we need to rely on OpenXR's input mapping system. That system doesn't have a way to iterate over all input devices attached to the system, it only allows you to set up suggested mappings for predefined control sets. As a result internally we produce mappings for the left and right hand controllers, but don't really have a system in place for individual trackers. I have a good interm solution for it at this time either, sorry.

toji avatar Nov 29 '21 18:11 toji

@toji Thanks so much for the info. Unfortunate we lost the functionality in the transition to OpenXR. Hopefully we can bring trackers back. A lot of cool in-browser experimentation was happening.

One possible temporary solution is Firefox desktop. I think it's still on the old WebVR implementation and trackers might still work there. Worth a try.

I think there's nothing actionable on the A-Frame side. I'm so sorry for the inconvenience. I keep the issue open as a reference

dmarcos avatar Dec 01 '21 00:12 dmarcos