How to Fix a Rigidbody Jittering on a Moving Platform in Unity

A rigidbody jittering on a moving platform is poor motion transfer. Here is how to fix it.

How to fix it

1. Move the platform with MovePosition

Move the kinematic platform with Rigidbody.MovePosition in FixedUpdate, so it moves in sync with physics. Moving it via transform outside physics makes resting bodies jitter as the platform and physics desync.

2. Parent the body while on it

Parent the rigidbody to the platform while it stands on it, so it is carried exactly with the platform's motion, and unparent on leaving. This is a simple, reliable way to keep the body locked to the moving platform.

3. Or add the platform velocity

Alternatively, add the platform's velocity to the rigidbody each physics step while it is on the platform, so it moves with the surface. This keeps physics interactions intact while carrying the body along.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unity error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.