Fix: Unreal Character Movement Component Not Working

Here is how to fix Unreal character movement not working. You placed a Character in your level, gave it a CharacterMovementComponent, set up input actions, and pressed Play — but the character stands completely still. No movement, no falling, no response to WASD or gamepad input whatsoever. The frustrating part is that nothing in the Output Log suggests anything is wrong. Here is how to diagnose and fix it.

The Symptom

Your ACharacter subclass is in the world with a valid capsule component and a CharacterMovementComponent. You have input actions configured in the project settings or via Enhanced Input assets. You press movement keys at runtime and the character does not budge. The camera may rotate if you have look input wired up, but the character stays planted at its spawn location.

In some variations, the character might spawn and immediately fall through the floor, float in the air without gravity, or move at an impossibly slow speed that looks like it is stationary. All of these stem from movement component misconfiguration rather than input issues.

You might also see this with AI-controlled characters where MoveToLocation or MoveToActor returns success but the pawn does not physically move across the level.

What Causes This

1. AddMovementInput is never called. This is the most common cause. CharacterMovementComponent does not read raw input directly. It waits for your code to call AddMovementInput() with a world direction and scale value each frame. If your input binding calls a function that does not call AddMovementInput, or if the binding itself is broken, the component never receives a movement request.

2. Enhanced Input mapping context not added. With Unreal 5.x and the Enhanced Input system, input actions only work if you add the Input Mapping Context to the player's Enhanced Input Local Player Subsystem at runtime. Forgetting this step means your input actions exist but are never processed, so your bound handlers never fire.

3. Movement mode is wrong. The CharacterMovementComponent has several movement modes: Walking, Falling, Swimming, Flying, and Custom. If the mode is set to None or an unexpected mode, the component may refuse to process movement input. This happens when code or a Blueprint accidentally sets the mode, or when the character spawns in a volume that changes the mode.

4. No NavMesh for AI movement. If you are using the AI MoveTo functions, the character requires a valid NavMesh that covers the destination. Without one, the pathfinding query fails and the AI controller never issues movement commands. The character stays still even though MoveToLocation returns a seemingly valid result.

The Fix

Step 1: Set up Enhanced Input bindings and call AddMovementInput. This is the complete setup for a character that moves with WASD using the Enhanced Input system.

// MyCharacter.h
UPROPERTY(EditAnywhere, Category = "Input")
class UInputMappingContext* DefaultMappingContext;

UPROPERTY(EditAnywhere, Category = "Input")
class UInputAction* MoveAction;

void Move(const FInputActionValue& Value);

// MyCharacter.cpp - BeginPlay
void AMyCharacter::BeginPlay()
{
    Super::BeginPlay();

    // Add the mapping context so input actions are processed
    APlayerController* PC = Cast<APlayerController>(GetController());
    if (PC)
    {
        UEnhancedInputLocalPlayerSubsystem* Subsystem =
            ULocalPlayer::GetSubsystem<UEnhancedInputLocalPlayerSubsystem>(
                PC->GetLocalPlayer());
        if (Subsystem)
        {
            Subsystem->AddMappingContext(DefaultMappingContext, 0);
        }
    }
}

Step 2: Bind the action and convert input to world movement.

// SetupPlayerInputComponent
void AMyCharacter::SetupPlayerInputComponent(UInputComponent* PlayerInputComponent)
{
    UEnhancedInputComponent* EIC =
        Cast<UEnhancedInputComponent>(PlayerInputComponent);
    if (EIC)
    {
        EIC->BindAction(MoveAction, ETriggerEvent::Triggered,
            this, &AMyCharacter::Move);
    }
}

void AMyCharacter::Move(const FInputActionValue& Value)
{
    FVector2D Axis = Value.Get<FVector2D>();

    // Get forward/right vectors relative to controller rotation
    const FRotator YawRotation(0, Controller->GetControlRotation().Yaw, 0);
    const FVector ForwardDir = FRotationMatrix(YawRotation).GetUnitAxis(EAxis::X);
    const FVector RightDir = FRotationMatrix(YawRotation).GetUnitAxis(EAxis::Y);

    // This is the critical call that feeds the movement component
    AddMovementInput(ForwardDir, Axis.Y);
    AddMovementInput(RightDir, Axis.X);
}

Step 3: Verify movement component settings. Log the movement state to identify misconfigurations.

// Add to Tick or BeginPlay for diagnostics
UCharacterMovementComponent* CMC = GetCharacterMovement();
UE_LOG(LogTemp, Warning, TEXT("Mode: %d, Speed: %.1f, Gravity: %.1f"),
    (int)CMC->MovementMode, CMC->MaxWalkSpeed, CMC->GravityScale);

// Fix common defaults
CMC->MaxWalkSpeed = 600.f;   // Default is 600
CMC->GravityScale = 1.f;     // 0 means no gravity
CMC->SetMovementMode(MOVE_Walking);

Related Issues

If your character moves but animations do not play, check our guide on animation montages not playing. If movement works but event dispatchers that should fire on movement events are silent, see Blueprint events not firing for binding and replication troubleshooting.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unreal 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

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

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

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

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

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

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

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unreal, 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.

No AddMovementInput call, no movement. The component does not read input on its own.