Strange Collisoin

[BH_Adabadoo_VR]

 

 

 

 

 

[IckyATLAS]

It is not strange. It is due to delay between collision and calculating and displaying the collision effects. This is a delay due to processing load and the way events are being managed. Even half a second delay between collision and collision effects between two planes flying at 500 or 600 Mph crossing speed, means that the planes will be 125 meters apart before you see the visual effects. And you see this gap well because at say ex. 80 FPS is no problem to show half a second and the two planes flying apart with 40 FPS.

Indeed the moment the two intersect immediately the collision effects should be displayed but here come limitations due to CPU GPU raw power and the simulators internal management of collision detection and consequences.

[BH_Adabadoo_VR]

4 hours ago, IckyATLAS said:

It is not strange. It is due to delay between collision and calculating and displaying the collision effects. This is a delay due to processing load and the way events are being managed. Even half a second delay between collision and collision effects between two planes flying at 500 or 600 Mph crossing speed, means that the planes will be 125 meters apart before you see the visual effects. And you see this gap well because at say ex. 80 FPS is no problem to show half a second and the two planes flying apart with 40 FPS.

Indeed the moment the two intersect immediately the collision effects should be displayed but here come limitations due to CPU GPU raw power and the simulators internal management of collision detection and consequences.

And internet latency too...

 

You explained it very well.  Thanks!