When transcluding Crypovoxels web client using WebXR into other worlds, CV is treated as a single WebXR session with infinite guardian boundaries. Movement through the world is treated as very long range head movement in the WebXR stage.
The problem with this is that CryptoVoxels is not prepared to load chunks based on head movement alone -- it seems to require using the control stick and/or teleporting to the new location. This makes it effectively impossible to tranclude CryptoVoxels conveniently into other worlds.
It seems it would be a pretty straightforward fix to add the chunk traversal logic to the head movement case as well, which means the transclusion case should just work.
Additionally, when using theoretically infinitely-ranged WebXR devices like phones, this would mean CryptoVoxels continues to work as intended, instead of mysteriously ending chunk loading after a city block.
When transcluding Crypovoxels web client using WebXR into other worlds, CV is treated as a single WebXR session with infinite guardian boundaries. Movement through the world is treated as very long range head movement in the WebXR stage.
The problem with this is that CryptoVoxels is not prepared to load chunks based on head movement alone -- it seems to require using the control stick and/or teleporting to the new location. This makes it effectively impossible to tranclude CryptoVoxels conveniently into other worlds.
It seems it would be a pretty straightforward fix to add the chunk traversal logic to the head movement case as well, which means the transclusion case should just work.
Additionally, when using theoretically infinitely-ranged WebXR devices like phones, this would mean CryptoVoxels continues to work as intended, instead of mysteriously ending chunk loading after a city block.