Diego Marcos
Diego Marcos
If it works on master then it will be fixed in the next version. Have you tried the very latest master build? https://cdn.jsdelivr.net/gh/aframevr/aframe@ce9fd2321c97daf01bf9f098ad8b625c1603bc63/dist/aframe-master.min.js Thanks
Cool. Thanks for taking the time to report
Some info from Discord: ``` Multimodal is supported for regular controllers and hands. To non-primary inputs will move from inputsources to trackedsources. So if you put the controllers down, hands...
A-Frame is now only looking into `xrSession.inputSource` and not `xrSession.trackedSource`. We need to adjust
Spec as reference https://pr-preview.s3.amazonaws.com/cabanier/webxr/pull/1361.html#dom-xrsession-trackedsources
With trackedSource now containing the "secondary" input I would not expect multimodal input to work in any A-Frame version. I'm assuming Meta Browser. So not sure how 1.5 or master...
I improved controller switching across the board. Can switch from hand to controllers. Or use any combination of hands and controllers. Except Logitech MX Ink that is not currently supported...
Thanks so much for verifying. Closing and can reopen if necessary
Thanks. Looked at the PR before this issue. Instead of using `laser-controls` you can add [magicleap-controls](https://aframe.io/docs/1.6.0/components/magicleap-controls.html#main) to each hand entity as follows ``` ``` Would that work? Thanks
Let me know if you have any questions