Fix: Godot 3D Picked-Up RigidBody Spinning Wildly

Here is how to fix Godot 4 picked-up RigidBody3D objects that spin uncontrollably while held. Force-based hold (apply force toward target) is unstable; freeze+kinematic provides clean control.

The Symptom

Player picks up a box. While carrying, the box spins faster and faster, eventually flinging itself away. Or held box behaves erratically when bumped against geometry.

What Causes This

Force-based hold instability. Continuous force toward target compounds with collision impulses; angular velocity accumulates without bound.

No angular damping. Angular damp = 0 means no resistance to rotation; small impulses build up.

Holding while still simulating. Physics keeps applying gravity, contacts; held object fights them all.

The Fix

Step 1: Use freeze + kinematic on pickup.

extends CharacterBody3D

var held: RigidBody3D

func pickup(body: RigidBody3D):
    held = body
    held.freeze = true
    held.freeze_mode = RigidBody3D.FREEZE_MODE_KINEMATIC
    held.reparent($Camera/HoldPosition)
    held.position = Vector3.ZERO

func drop():
    if held == null: return
    var world_pos = held.global_position
    held.reparent(get_tree().root)
    held.global_position = world_pos
    held.freeze = false
    held = null

Reparenting to the camera makes the body follow head movement exactly without spinning.

Step 2: Add angular damping for fallback.

body.angular_damp = 5.0   # strong resistance to rotation

Even when not held, this prevents accumulated spin from light collisions.

Step 3: Lock rotation axes if needed.

body.lock_rotation = true   # no rotation at all
# or per-axis
body.axis_lock_angular_x = true
body.axis_lock_angular_y = false
body.axis_lock_angular_z = true

Step 4: For physical hold (Half-Life style), use a constraint. A PinJoint3D between the held body and a hand bone provides physics-correct hold without manual freeze. More complex setup but more interactive.

Step 5: Verify drop preserves position. When dropping, capture global_position before reparenting; reapply after to avoid sudden teleports.

Understanding the issue

The challenge with physics-related bugs is reproducibility. A symptom you see in a 30 fps build may vanish at 60 fps because the integrator's step size changed. Reproducing reliably means controlling both your inputs and the engine's tick rate.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Godot. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Godot-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

Within Godot, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Freeze + kinematic + reparent. Three steps for stable hold without spin.”

Related Issues

For RigidBody2D sleep, see RigidBody2D Sleep. For 3D character stairs, see 3D Stair Stepping.

freeze + kinematic on pickup. Reparent to hand. Unfreeze on drop. Held objects stay still.