How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Velocity Loss Switching From Kinematic to RigidBody in Godot

Q: What causes velocity loss switching from kinematic to RigidBody in Godot?

When you change a body to dynamic mode (or hand off to a RigidBody), its linear velocity is zero because the previous motion was applied by moving the transform, not by physics velocity.

Quick answer: Track the body's velocity while it is kinematic and assign it to linear_velocity (or apply an equivalent impulse) at the moment you switch to dynamic.

A platform character thrown into ragdoll or physics mode falls straight down instead of continuing forward. The animated motion never set a physics velocity, so the dynamic body starts at rest. Carrying the last velocity preserves momentum.

How to fix it

1. Estimate velocity before the switch

While kinematic, compute velocity as (position - last_position) / delta each frame so you have the current motion vector ready when you convert to dynamic.

2. Assign linear_velocity on switch

At the moment you set freeze = false / change to RIGID mode, set linear_velocity to the tracked value so the body continues with the same momentum.

3. Use an impulse alternative

If you cannot set velocity directly, call apply_central_impulse(velocity * mass) right after enabling physics to inject the equivalent momentum.

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 Godot 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.

The errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.