What's Layered Blend Per Bone?

An AnimBP node that blends an upper-body animation over a full-body base pose, isolating the blend to specific bone hierarchies (e.g., spine and above). Used for aim animations while running.

Why is my layered pose completely off?

Weight pin is 0 (no blend), Branch Filters list the wrong root bone, or the input pose is additive while the node expects full-body (or vice versa). Inspect the variable feeding Blend Weights and check the Branch Filters in node details.

What's the difference between Additive and Full Body mode?

Additive: the layered pose is an offset added to the base. Full Body: the layered pose replaces the base for the filtered bones. Mismatch produces wrong-looking results — e.g., adding a raised-arm offset onto an already-raised arm produces hyperextension.

Fix: Unreal AnimBP Pose Blend Zero Weight

Quick answer: Set the Blend Weights variable to 1.0, ensure Branch Filters reference the correct root bone (typically spine_01), and verify additive/full-body modes match the input pose authoring.

A character has a base locomotion (walk/run) and a layered “aim with rifle” pose that should override the upper body while preserving leg motion. The aim pose isn’t visible at all — only legs and arms hang down. The Layered Blend Per Bone exists but applies zero weight.

Layered Blend Per Bone Anatomy

The node takes:

Base Pose (input 0): the full-body pose to blend over.
Blend Poses (input array): one or more layered poses.
Blend Weights: array of floats, one per layered pose. 0 = no contribution, 1 = full override.
Branch Filters: per-pose configuration with root bone name and blend depth.

Fix 1: Check Blend Weights

// In Anim BP Event Graph
if (CharacterIsAiming) {
    AimBlendWeight = 1.0f;
} else {
    AimBlendWeight = 0.0f;
}

Wire AimBlendWeight to the Layered Blend Per Bone’s Blend Weights array (element 0). Default initialized to 0 = always off. Print the value during play to confirm it’s 1 when expected.

Fix 2: Branch Filters Root Bone

In the node’s Details, expand Branch Filters → [0] → Bone Name. For an upper-body blend, set to spine_01 (or your skeleton’s equivalent spine root). Blend Depth = -1 cascades to all child bones.

If Bone Name is empty or wrong, the filter doesn’t match any bones — the layered pose contributes 0 even when weight is 1.

Fix 3: Additive vs Full Body Mode

Check the Layered Pose property of each blend pose: Mesh Space, Mesh Space Additive, or Local Space. If your aim pose was authored as additive (relative to base) but the node treats it as full-body, the rotations are doubled-up.

Right-click → Convert to Additive on the AnimSequence asset to standardize. Or change the node’s expected mode to match the source.

Diagnose with Pose Debugging

Open the Anim BP. In Preview, drag the AimBlendWeight slider. The upper body should transition between base pose and aim pose. If nothing changes, recheck weights and filters.

Console: showdebug animation in PIE. Shows active animation nodes and their current weights.

Verifying

In PIE, set the aiming state. The character’s upper body should hold the aim pose while legs continue to run. Switch off aiming — upper body returns to the locomotion pose. Animation transitions smoothly via the weight lerp.

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 compounds with the others.

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

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

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

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

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

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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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.

“Layered Blend needs weight, the right filter root, and matching pose modes. Three knobs to align.”

Use showdebug animation as your default diagnostic for any AnimBP weight bug — reveals weights in real time.