Course contentsShow
← Unreal Engine Game Development
Lesson 336 of 8805. Animation and Character RiggingFree lesson

Debugging Animation Blending with Live Link

You will use the animation debugging tools to analyze blend weights and node activity in real-time to identify and fix jittery character transitions.

In this lesson, you will learn how to use Live Link and real-time debugging tools to pinpoint the source of jittery transitions in your character’s animation blending.

When you notice a "hitch" or jitter during a blend—such as when transitioning between two State Machine states or layering an Aim Offset—the issue is often caused by conflicting blend weights or incorrect data arriving from an external source like a motion capture rig via Live Link.

Using the Animation Debugger

To diagnose this, open your Animation Blueprint and ensure your character is running in the editor (PIE). Navigate to Window > Animation > Animation Debugger. Here, you can select your character instance to see the Active States and Node Weights in real-time.

If your character is jittering, look for rapidly fluctuating values in the Weight column of your blend nodes (like Blend Poses by bool or Layered Blend per Bone). If you are using Live Link, this jitter often indicates that the incoming data stream has a frame rate mismatch or noisy signal values.

Analyzing Blend Weights

You can pause the game or use the "Slow Motion" feature in the Level Editor to step through frames. Watch the Graph view within the Animation Blueprint while the character is in a transition. If the node output values "flicker" between 0.0 and 1.0, your transition logic might be fighting with an incoming Live Link pose.

To isolate if Live Link is the culprit, you can temporarily bypass the Live Link input in your AnimGraph:

// Logic check for debugging: 
// Disable the Live Link Pose node to see if the jitter persists 
// using only internal Animation Sequences.

If the jitter disappears once Live Link is disconnected, the issue lies in your Live Link Remap Asset or the raw tracking data, rather than your transition rules. By comparing the expected transition curve against the real-time node weights shown in the debugger, you can identify if a specific state is holding on too long or if a blend duration is set incorrectly for the incoming data velocity.

Key Takeaway: Use the Animation Debugger to cross-reference your Blend Node weights against Live Link input frames to determine if transition jitter is caused by logic conflicts or noisy external data streams.