Fix: Unreal Animation Montage Not Blending Out

Here is how to fix Unreal Animation Montage not blending out. You play an attack montage. The swing plays. At the end of the montage, the character freezes mid-pose instead of returning to the idle/walk state machine. Or the montage never stops playing. Montages need explicit Slot plumbing in the Animation Blueprint to blend back to the state machine.

The Symptom

After a montage finishes, the character stays frozen in the final frame. Or the montage appears to loop because the state machine is not resuming. Or blending happens but to a default T-pose.

What Causes This

No Slot node in AnimGraph. Montages play on named slots. The AnimGraph must have a Slot node matching the slot name. Without it, the montage plays into nothing.

Slot name mismatch. Default slot is “DefaultSlot.” If your montage uses “UpperBody” but your AnimGraph has a DefaultSlot, the montage plays on DefaultSlot (a new slot auto-created) while your UpperBody Slot node gets no input.

State machine not connected through Slot. Common layout error: state machine output goes directly to Output Pose, bypassing the Slot. Montage data plays on the slot, but the slot is not in the final blend chain.

Blend Out Time too long or infinite. If Blend Out Time in the montage is set very high, the blend back takes forever. Appears as if the character is stuck.

The Fix

Step 1: Add a Slot node in AnimGraph. Open your Animation Blueprint. In AnimGraph:

State Machine -> Slot (DefaultSlot) -> Output Pose

The Slot node is found by right-click > Slot > DefaultSlot. It takes the incoming pose as its “base” and any active montage plays on top. When no montage plays, it just passes the state machine through.

Step 2: Name slots consistently. In the montage asset, the Slot setting in the Anim Slot Manager must match what you reference in AnimGraph. Best practice:

• DefaultSlot: full-body actions (attacks, emotes)
• UpperBody: upper-body-only actions, blended with layered legs

Edit slots under the skeleton asset’s Anim Slot Manager. Add slot names, mark groups, and save.

Step 3: Play with Blend Out control.

void AMyCharacter::PlayAttack()
{
    if (AttackMontage)
    {
        float Duration = PlayAnimMontage(AttackMontage);
        UE_LOG(LogTemp, Log, TEXT("Montage played, duration %f"), Duration);
    }
}

void AMyCharacter::InterruptAttack()
{
    GetMesh()->GetAnimInstance()->Montage_Stop(0.25f, AttackMontage);
}

PlayAnimMontage returns the montage duration. Montage_Stop with a time parameter smoothly blends back; 0 is instant.

Step 4: Listen to OnMontageEnded.

void AMyCharacter::BeginPlay()
{
    Super::BeginPlay();
    UAnimInstance* Anim = GetMesh()->GetAnimInstance();
    Anim->OnMontageEnded.AddDynamic(this, &AMyCharacter::OnMontageEnded);
}

void AMyCharacter::OnMontageEnded(UAnimMontage* Montage, bool bInterrupted)
{
    if (Montage == AttackMontage)
    {
        UE_LOG(LogTemp, Log, TEXT("Attack ended (interrupted=%d)"), bInterrupted);
        bIsAttacking = false;
    }
}

Use for state flags (is attacking?), combo detection, and cleanup. bInterrupted tells you if the montage ended naturally or was canceled.

Layered Slots (Upper Body Attack)

To play attacks on upper body while legs keep walking, use Layered Blend Per Bone or a separate Slot node upstream:

LocomotionStateMachine ->
  Layered Blend Per Bone (spine root) ->
    [Base] locomotion
    [Blend] UpperBody Slot (with attack montage)
    -> Output Pose

Now attack montages only affect upper body, legs continue walking.

Understanding the issue

Animation systems blend pose data over time. The blend math is straightforward; the timing isn't. State machines, transition curves, layer weights - each is a knob that compounds with the others, and bugs at the intersection are common.

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

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

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

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.

“Montages need Slots. Slots need AnimGraph wiring. Without both, the character freezes or the attack never plays.”

Related Issues

For general animation debugging, see Unity Animator Root Motion Not Applied (analogous concepts). For Blueprint Interface issues, Blueprint Interface Not Calling C++.

Slot node in AnimGraph + matching slot name + Blend Out Time tuned. Every montage needs this.