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
To fix it, we should somehow set view.scene.matrixWorldAutoUpdate = true;
either in the file view_3d_map_webxr.html
or in WebXR.js, using this kind of workaround
So in WebXR.js , above these lines
I wonder how there aren't more things broken as I read the comments from mrdoob/three.js#28533.
In my opinion, we should harmonize the xr and non-xr behaviour: either set autoupdate to false in both cases and manage matrices updates ourselves, or set autoupdate to true for both context.
I haven't looked into it yet but first we need to remember why we set the autoupdate to false and if there's really a performance gain or if we'd be better off setting it to true and avoiding the hassle and bugs.
Since the bump of the three.js version f7303de
The view_3d_map_webxr example doesn't work anymore when entering the VR mode
Screencast.from.04-12-2024.17.30.28.webm
Context
Steps to Reproduce
Possible Cause/Fix/Solution
Since this merge in three.js, there is a condition on matrixWorldAutoUpdate .
To fix it, we should somehow set
view.scene.matrixWorldAutoUpdate = true;
either in the file view_3d_map_webxr.html
or in WebXR.js, using this kind of workaround
So in WebXR.js , above these lines
itowns/src/Renderer/WebXR.js
Lines 55 to 57 in 683e55d
we could add
The text was updated successfully, but these errors were encountered: