I noticed a strange behaviour in my Results when I change the Simulation speed.
On my layout there are several components, when Simulating with normal Speed (10x, 20x, 50x) the results look good.
However, when I select x2000 my components reach a deadlock.
Did anyone else have similar experience?
The built-in behaviors of VC are time-step independent, but there can be issues with scripts that don’t e.g. always ensure world update before querying positions of simulation nodes.
Some specific things like the collision detector checks are also tied to the rendering. Those occur automatically only after each frame is rendered, but can also be forced to update at desired constant simulation time step from the API.
thanks for the answer. Indeed I have some custom scripts where I use for example condition(lambda: axisX > xxx Value) how do I ensure the world update before querying positions of simulation nodes?
Collision detectors are turned off for this simulation
Generally you need to call vcNode.update() on the appropriate node such as component to ensure the positions are up to date.
However, calling update on the whole sim world unnecessarily will make your simulation much slower.
https://help.visualcomponents.com/4.10/Premium/en/Python_API/vcNode.htm?rhhlterm=update