Fix: Unity CharacterController Stuck on Stairs and Steps

Here is how to fix Unity CharacterController catching on stairs as if it forgot how to climb. The character runs flat on smooth ground but stops dead at every stair edge. Or it climbs but bumps visibly with each step. The fix is part Step Offset configuration, part level design trickery to make stairs traversable.

The Symptom

The character runs into a flight of stairs and stops. Or it climbs but stutters with each step, breaking camera smoothness. Sometimes only certain stairs cause issues; others work fine.

What Causes This

Step Offset too small. Default 0.3 m handles a 10-inch step. Modern level art often uses larger steps for fantasy/sci-fi feel.

Slope Limit too tight. The angle of the imaginary ramp through the stairs may exceed the limit. CharacterController treats steeper as wall; cannot climb.

Capsule radius catches lip. A wide capsule clips the stair lip and refuses the step-up.

Skin Width too small. Skin Width below 0.08 m can cause edge clipping; raise to 0.1 m for smoother step traversal.

The Fix

Step 1: Raise Step Offset.

// Inspector or code
controller.stepOffset = 0.5f;     // up to 0.6 for tall steps
controller.slopeLimit = 50f;     // up to 55 for steeper stair runs
controller.skinWidth = 0.1f;

Step Offset must be less than capsule height minus skin width or it gets clamped silently.

Step 2: Use a stair ramp collider. The standard solution: keep your stair visual mesh, but place an invisible inclined plane collider over it at the slope angle. Set the visual stair mesh’s collider to disabled or move it to a layer the character does not collide with. The character glides up the ramp; players see steps.

// Hierarchy:
StairMesh (visual mesh, no collider)
  StairRampCollider (BoxCollider rotated to ramp angle)

Step 3: Tune capsule radius. A capsule radius of 0.3 m is typical for a humanoid. If your character is wider, the radius can catch tile edges; consider keeping the visible width while shrinking the collision radius slightly (0.25 m) to ease step traversal.

Step 4: Detect ground manually for cinematic stairs.

void SnapToGround()
{
    if (Physics.Raycast(transform.position, Vector3.down, out RaycastHit hit, 2f))
    {
        if (hit.distance < 1.1f)
        {
            var snap = (hit.distance - 1.0f);   // keep feet 1m from camera
            controller.Move(Vector3.down * snap);
        }
    }
}

Call after movement to keep the character glued to varying ground heights, smoothing minor stair bumps.

Step 5: For steep stairs, replace with multiple smaller ramps. Visually segmented steep stairs can use a series of ramp segments. Each ramp respects Slope Limit; transitions between them are smooth.

Common Pitfalls

Trying to use CharacterController for traversing very tall obstacles. CharacterController is designed for human-scale traversal; for climbing or vaulting, custom physics or animation root motion is more appropriate.

Using Rigidbody plus CharacterController on the same actor. They fight. Pick one.

Understanding the issue

Game physics is a contract between authoring (the body, mass, collision shapes you set) and the solver (how the engine integrates them per tick). Bugs at this boundary usually surface as 'the values look right but the behavior is wrong' - a sign that one side of the contract isn't honoring the other.

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

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

At the engine level, the behavior comes from a deliberate design decision in Unity. 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

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

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

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

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Unity-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

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unity, 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

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

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.

“Step Offset for tall steps. Ramp colliders for smooth feel. Two simple tools handle every stair.”

Related Issues

For NavMesh edge issues, see NavMeshAgent Stuck on Edge. For Rigidbody falling, see Rigidbody Falling Through Floor.

Step Offset wide enough. Ramp under stairs. The character glides up.