← Learn library

Character FX & Animation

Biped Character Rig Part 13 - Setting up an IK FK Blend Arm

Channel: TD Superheroes ·

Written guide

Original TD Superheroes video thumbnail
Biped Character Rig Part 13 - Setting up an IK FK Blend ArmTD Superheroes · Video hosted on YouTube

Playing loads YouTube content. YouTube processes data after activation.

Watch on YouTube

If the player is blocked or unavailable, use Watch on YouTube.

Software: Maya

The arm now has separate IK and FK systems. This lesson makes the bind arm follow either one through a blend attribute on the hand settings control. Corresponding IK and FK joints become targets of parent constraints on the bind joints; the blend attribute then controls the two target weights.

The demonstrated convention is zero for IK and one for FK. Control visibility and making the hand follow the arm are left for later lessons. The exact Maya release is unidentified, and the recording does not demonstrate pose matching or guarantee seamless switching between differently posed systems.

Identify the corresponding chains before constraining them

At 00:00–03:01, the instructor reveals the bind, IK, and FK arms so their overlapping positions can be inspected. The simpler animation chain that drives the IK system is hidden to reduce confusion; the twist-bearing IK chain is the one used alongside the FK chain for the bind-joint constraints.

The hand control receives a floating-point IK/FK blend attribute with a minimum of zero, maximum of one, and default zero. A float allows intermediate values, unlike an interface designed only as a two-state switch.

Confirm the identity of each joint before selecting constraint targets. Several joints occupy the same location, and the IK setup itself contains more than one chain. A viewport click without an Outliner or naming check can easily select a node with the wrong role.

The setup starts with corresponding joints aligned. The lesson does not include an automatic matching operation that first brings arbitrarily different IK and FK poses into agreement.

Build a two-target constraint for each bind joint

During 03:01–07:01, the instructor selects the IK joint, then the corresponding FK joint, then the bind joint to be constrained. A parent constraint is created with translation and rotation participation and maintain offset enabled in the recorded settings.

This selection order is kept consistent across the shoulder, twist joints, elbow, and wrist so the target weights are easier to interpret later. Even so, the source catches a mistake where an elbow is selected during a twist-joint operation. The incorrect relationship is repaired before the process continues down the chain.

The repeated setup is partly completed during a pause. Do not infer a fully documented literal connection list from that pause; inspect each created constraint and its actual targets.

With both targets contributing, the bind joints initially sit between the IK and FK results. The instructor moves each system to observe that shared influence. This verifies that both sources participate, but it is only the intermediate state before the blend weights are connected.

Connect the blend value directly to the FK weights

At 07:01–11:12, the target weights are tested manually. Full IK influence with zero FK influence makes a bind joint follow IK; reversing that choice makes it follow FK. The hand attribute will automate this relationship across the arm.

For the chosen convention, the FK weight can receive the blend attribute directly. At blend zero, FK contributes zero. At blend one, it contributes one. The lesson uses the Connection Editor to make this direct connection on each relevant constraint, exposing the necessary attributes in the editor when they are not initially listed.

At this stage the IK weight still remains one. Moving the blend to one therefore produces two active weights rather than a pure FK result. The recording explicitly identifies that incomplete state before implementing the inverse side.

Check a real constraint’s target aliases instead of assuming that a suffix always identifies FK. Consistent selection order helps, but the target’s actual node identity is the stronger verification.

Key the opposite IK endpoints

During 11:12–15:16, Set Driven Key is used for the IK weight. The hand blend attribute is the driver, and each constraint’s IK target weight is the driven channel.

The intended endpoint relationship is:

Hand blend IK target weight FK target weight
0 1 0
1 0 1

The instructor records the first IK weight state across the chain, changes the driver to the opposite endpoint, then records the second state. The driver remains the same while the driven constraint is reloaded for each joint.

These endpoint keys establish the demonstrated switch convention. The source does not specify a separate animation-curve tangent adjustment, so the article does not claim a particular mathematically linear interpolation between them. Inspect intermediate blend behavior if it matters to the intended animation workflow.

A working wrist is not enough to prove the arm is complete. Every corresponding bind constraint needs its own correct weight relationship, including the intermediate twist joints.

Find an omitted joint by testing both full states

At 15:16–16:49, the final test exposes one missed elbow-twist weight. At the FK endpoint, that constraint’s IK contribution has not reached zero. The instructor finds the specific joint, reloads its driven weight, sets the correct endpoint, and keys it.

The blend is then tested again from one side to the other. This is a useful diagnostic pattern: when most of a chain follows the new mode but one section remains between the systems, inspect that section’s target weights before rebuilding the entire setup.

Check the full IK endpoint, full FK endpoint, and several intermediate values, then return to neutral. Confirm that every bind joint follows the intended system at the endpoints. Keep pose matching, control visibility, hand attachment, and extreme-rotation behavior as separate unfinished work; the recording explicitly leaves the first two integration topics for the following stage.