@leeren @RaananW @Cedric This bug happens only for a non-wasm build of the ammo.js, I think (it was like that when I was using Three js). From what I’ve found out, this is probably related to the build arguments for the non-wasm build of ammo, or idk. Hope that it can be fixed 