tracked-controls v1.x - only one controller (id:0) is connected
See original GitHub issueOnly 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>
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
aframe - UNPKG
84, "src/components/generic-tracked-controller-controls.js",. 85, "src/components/geometry.js", ... 123, "src/components/tracked-controls-webvr.js",.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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.
@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