Move static physics body with associated mesh

[HiGreg]

@Pryme8 probably means “more computationally expensive than disablePrestep = true”

Related posts:

Move static physics body with associated mesh

I’m trying to use raycasts to detect hits on certain meshes. When none of the meshes moves, this works fine. However, in my project some of the meshes move around (they’re all simple box meshes). When I create a static physics body for one of these meshes, I want to update the body’s position to the mesh’s position each frame, so raycasts can hit it (rotations or billboarding is not required). Using a dynamic or animated body makes moving the associated mesh no longer possible when setting it’…

Rotate PhysicsBody around scene's axis

I think your issue is related to physicsBody.disablePreStep, which for performance reasons is normally true. If you want to modify the physicsBody position or rotation outside the control of the physics engine, set disablePreStep = false until the next scene.onAfterPhysicsObservable. You can read about disablePreStep here.

Moving meshes manually with physics enabled

What do you think of this? Is there a better method? I move meshes manually all the time with physics enabled. The advice on the forums is consistent: disable disablePrestep on the physics body right before you want to change a transform on the transformNode. If it is a one time assignment, enable it again in the next frame or so (performance). Keeping track of which meshes need to re-disable PreStep after the current frame isn’t straightforward. How about something like this? const disab…

Also note the response in the last link:

@Cedric

disablePreStep was introduced to disable unnecessary updates. It’s find for most cases and in particular for heavily instanced meshes.
If you have only a few objects that need pre-step, I don’t think enable/disable prestep will make a huge difference and it might make your code more complex.