The test case is https://playcanv.as/e/p/TAYVQgU2/. It is only happened in PlayCanvas is because they use position and orientation DomPoints to generate a local matrix by their own [1]. Other WebXR examples like input-profile, they use `transform.matrix` [2]. So, I believe we did it right in Matrix4x4, and there is something wrong when getting the orientation from Matrix4x4. [1] https://github.com/playcanvas/engine/blob/d9b54249828b016338e5ae23ab5bbfd0a69138d2/src/xr/xr-input-source.js#L230 [2] https://github.com/immersive-web/webxr-samples/blob/eea396e20366dd896532a8cf51537552fabc971f/input-profiles.html#L216
Bug 1635363 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The test case is https://playcanv.as/e/p/TAYVQgU2/. It is only happened in PlayCanvas is because they use position and orientation DomPoints to generate a local matrix by their own [1]. Other WebXR examples like input-profile, they use `transform.matrix` [2]. So, I believe we did it correctly in Matrix4x4, and there is something wrong when getting the orientation from Matrix4x4. [1] https://github.com/playcanvas/engine/blob/d9b54249828b016338e5ae23ab5bbfd0a69138d2/src/xr/xr-input-source.js#L230 [2] https://github.com/immersive-web/webxr-samples/blob/eea396e20366dd896532a8cf51537552fabc971f/input-profiles.html#L216