Floating Origin and TrailMeshes

[CrashMaster]

One of the issues is Wasm specific: translating everything every frame requires sending a lot of data across the JS/Wasm boundary (disablePreStep=false), and it is not fast to say the least.

Here is a discussion about that from a while ago:

Havok and BabylonJS are out of sync

Babylon uses a variable framerate by default, which is what causes the apparent jitter. Enabling deterministic lockstep will remove the jitter. However, in your onAfterPhysicsObservable, you’re teleporting every body every step; this will cause problems for both performance and behaviour, in any physics engine, not just Havok. I strongly recommend you do not do this to the physics - simulate physics with a fixed coordinate system and transform the coordinates wherever your application needs to …

You can also have issues when not using a fixed physics framerate, creating jittering.

Translating everything back to the origin for rendering only is not easy to accomplish as discussed here:

Big and small objects

I still haven’t been able to solve this problem, with this problem it’s probably not even worth continuing to do my pet project, if you suddenly find a solution, please let me know, I’ll be grateful

None of this is unfixable, but I didn’t take yet the time to make all of that in a single demo haha