Quick answer: apply_force does not wake sleeping bodies unless above the wake threshold. Use apply_impulse to guarantee a wake, or explicitly set sleeping = false before applying force. can_sleep = false disables sleep entirely for bodies that need constant simulation.

Here is how to fix Godot RigidBody3D sleeping not waking. You drop a dynamic crate onto the ground. It settles and goes to sleep. You call apply_force on it to simulate wind or a repelling field — nothing happens. The force shows no effect, the body stays still, sleep wins. Godot’s physics sleep behavior mirrors Unity’s: efficient, correct, and infuriating when you do not know the rules.

The Symptom

A RigidBody3D that has come to rest stops responding to forces:

Large forces (gravity change, explosion) do wake it. Rebuilding the scene or entering play mode starts the body awake until it settles again.

What Causes This

Force vs impulse semantics. apply_force adds continuous acceleration — small magnitudes accumulate over time. For sleeping bodies, Godot requires the force to exceed a wake threshold before the body wakes. apply_impulse applies instant velocity change; any non-zero impulse wakes the body immediately.

Sleep threshold in Project Settings. Project Settings > Physics > 3D > Sleep Threshold Linear and Angular Threshold. Default 0.1 m/s linear and ~0.1 rad/s angular. Forces that produce velocities below this get ignored as “too small to wake.”

Sleeping property stuck true. If code once set sleeping = true explicitly (pausing a body), it stays true until explicitly set false. Not uncommon during state restores from save data.

Contact monitor disabled. If contact_monitor = false or max_contacts_reported = 0, the body does not track collisions well enough for physics to wake it on touch. Other dynamic bodies colliding into it do wake it (PhysX handles that globally), but it is less reliable for edge cases.

The Fix

Step 1: Use apply_impulse for user-initiated forces. If your code says “this body should move now,” use apply_impulse. It always wakes the body and applies the velocity change in one frame.

extends RigidBody3D

func push_hard(direction: Vector3):
    # Impulse wakes the body automatically
    apply_impulse(direction * 5.0)

func apply_wind(direction: Vector3, delta: float):
    # Continuous force; wake manually first
    if sleeping:
        sleeping = false
    apply_force(direction * 2.0)

The pattern: impulse for one-shot events, force for continuous with an explicit wake. Never assume apply_force will wake a sleeping body.

Step 2: Disable sleep on critical bodies. For bodies that must always simulate (main characters, vehicles, things that move based on script), disable sleep:

func _ready():
    can_sleep = false

No CPU-saving benefit, but guaranteed responsiveness. Use sparingly — a scene with 200 always-awake rigidbodies costs much more than 200 normally-sleeping ones.

Step 3: Tune global thresholds. Project Settings > Physics > 3D. Lower values mean less aggressive sleep:

These are global. For most games the defaults are fine; tweak only if your use case has many bodies that should respond to light forces.

Step 4: Enable contact monitoring where needed. If you want sleeping bodies to wake on touch and also react via signals:

func _ready():
    contact_monitor = true
    max_contacts_reported = 4
    body_entered.connect(_on_body_entered)

func _on_body_entered(body):
    sleeping = false
    # react to collision

Debugging

Visualize sleep state with a debug indicator:

func _process(_delta):
    $DebugLabel.text = "sleeping=" + str(sleeping)
    $DebugLabel.modulate = Color.GRAY if sleeping else Color.GREEN

Place a 3D label on bodies during dev. See which ones are asleep at any moment. Unexpected sleeps tell you where thresholds need tuning.

Performance Tradeoff

Sleep is a legitimate optimization — scenes with 1000 rigidbodies where only a few move at a time pay almost no cost for the 995 sleeping ones. Disabling sleep on everything or lowering thresholds too far costs CPU that scales with body count. Measure frame time before and after changing sleep settings on a realistic scene.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Godot Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

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

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

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

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

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

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

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

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

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.

“Sleep is PhysX being considerate. When you need responsiveness, be explicit: impulse, not force; sleeping = false, not hope.”

Related Issues

For CharacterBody3D issues, see CharacterBody2D Floor Snap (same concepts in 3D). For area detection, Area2D Not Detecting StaticBody2D covers related physics issues.

Impulse for one-shot, force with explicit wake for continuous. Know when to use each.