Thank you! The scale workaround sounds interesting, but I'm having difficulty determining the exact implementation approach within my repository structure. I would greatly appreciate your guidance on implementing this solution in code I shared (https://github.com/michaello/BouncyBall-visionOS/). Specifically I'm uncertain about Where in my current entity hierarchy I should introduce the container entity for scaling Whether all physics entities (ball, ground, walls) need to be scaled equally, or if only the ball requires this treatment The recommended scale factor to use (10x, 100x?) to prevent premature sleeping How to properly adjust the initial velocity and gravity values to maintain the same visual behavior at the larger simulation scale If you could point me toward specific code changes or provide a small example of the container/scaling setup, it would help a lot! I can't find any sample code on internet for it so it's difficult for me to test your suggestion.
Topic:
Spatial Computing
SubTopic:
General
Tags: