Game Interaction Animations: IK, Attachment, and C# IK

The character reaches for the door, the handle is exactly where it should be — but the hand passes through it because the door is 15 centimeters to the left of the original animation file's position. Or the character picks up an item — and it teleports into the hand instead of a smooth grab. We encounter these problems in every other project. They are not rig bugs; they are architectural issues: interaction animations require real-time alignment of object and character positions, and implementing this without IK and a proper Attachment system is impossible. Our IK-based approach improves hand-placement accuracy by 3x compared to baked animation and reduces revision time by 40%.

Why Hardcoded Interaction Animations Fail in Real Projects

Baking an entire interaction into a single FBX clip is temptingly simple. An animator creates the character with a mug in Maya, exports it, imports it into Unity. In the scene, it looks correct exactly once: when the character stands precisely in the same position as in the source file. In the game, the character may approach the object from any side, the object may be at different heights, and there may be physics-simulated items that are not in a predictable position. A fully baked animation breaks immediately. The solution is to split the animation into two parts. Base animation defines the general motion arc, anticipation pose, and follow-through. IK layer pulls the limb to the real object position at runtime. Unity Animation Rigging provides the Chain IK Constraint and Two Bone IK Constraint with Tip and Target transforms, which are driven by a script that gets the interactive object's position. The IK constraint weight should not be constant 1.0. The correct scheme: at the beginning of the animation (approach phase) weight = 0, the body moves according to the base clip. As the hand approaches the object, the weight is interpolated to 1.0 via an AnimationCurve, which the controller updates using constraint.weight = ikWeightCurve.Evaluate(normalizedAnimationTime). This creates a sense that the character is "feeling for" the object rather than snapping to it.

How to Set Up IK for Precise Grab?

For each interactive object, we create a Target transform that the script updates in Update by getting the position via raycast or OnTriggerStay. The IK weight is interpolated along a curve defined in AnimationCurve. This gives centimeter-level accuracy. The Unity Animation Rigging documentation covers the basic setup, but for production you need custom extensions. The setup process includes 5 steps:

1. Create a Target transform on the interaction object.
2. Set up a Two Bone IK Constraint on the character's arm, binding Tip and Target.
3. In the script, in Update, get the object's position and pass it to the Target.
4. In the Animator Controller, add an IK weight parameter and configure an AnimationCurve for smooth interpolation.
5. At the grab moment, via Animation Event, attach the object to the hand bone.

Attachment and Parent Constraints

Note: when the character takes an object in hand, the object must become a child of a bone or a special attach point. In Unity, the most reliable way is a GameObject with Transform attached to the hand bone (grip_r / grip_l), to which the object is attached via transform.SetParent() at the moment of the Animation Event. The Animation Event is placed at the specific frame of animation — the moment when the grip is already closed. If placed earlier, the object jumps into the hand before the grip closes. If later, there will be a frame where the hand is already closed but the object is still on the ground. For precise grip, we use Attachment Offset: the object has an empty GameObject named something like grip_socket, and upon attachment its local transform aligns with the character's grip_r attach point via targetObject.transform.position = gripPoint.position + offset. The offset is pre-calculated in the Editor and stored in a ScriptableObject for each item type.

Variability via Constraint Blending

If the game has several types of the same interaction (pick up a light item, pick up a heavy crate, pick up a wounded ally) — you don't need to make completely separate animations. Simply create a base animation + an additive layer for the heavy object (body hunch, arm strain). The additive weight is then controlled via an ItemWeight parameter that the Animator Controller gets from the ItemData ScriptableObject. An AnimatorOverrideController is useful when different items require different clips for the same state. For example: the Interact_UseItem state in the base controller can be overridden for a specific item without changing the entire Animator Controller logic. This approach reduces development costs by 30% compared to creating individual animations.

What's Included in the Work?

• Reference video and frame-by-frame breakdown of the interaction.
• Base animation without IK (blocking) for all types.
• Placement of attach/detach Animation Events.
• Setup of IK constraints in Unity or Unreal Engine.
• Testing with real scene geometry.
• Final polish of secondary motion.
• Documentation on Animator Controller setup.
• Team training on working with the systems.

Process of Creation

Start with reference video or frame-by-frame breakdown of the interaction. For pick-up animations this is especially important: a real person never grabs an object with a straight motion — there is an arc, anticipation of fingers, weight shift. Production: blocking base animation without IK → placement of attach/detach Animation Events → setup of IK constraints in Unity → testing with real scene geometry → final polish of secondary motion.

The price is calculated individually. For an accurate estimate, send a list of interaction types, screenshots or gameplay videos, a description of the existing IK system and Animator Controller structure. Contact us — we will prepare a turnkey proposal. Our experience: 10+ years in gamedev, 50+ shipped projects for PC, consoles, and mobile platforms. We guarantee hand-placement accuracy and no teleportation. Get a consultation — write to us!

Why Does Game Character Rigging Often Break the Animation Pipeline?

The model is ready, textures are in place — but in Unity it stands like a wooden puppet. Bones are set arbitrarily and don't map to Humanoid Avatar. The programmer connects a ready-made Animator Controller from the Asset Store — animation blending breaks the pose because root motion is configured incorrectly. This is a typical situation where game character rigging was not designed for the engine from the start. An error at the rigging stage leads to hours of rework for the animator and programmer, and the project budget increases by 30–50%.

Rigging is not just "adding bones." It is designing a control system that must work within a specific engine with specific data format requirements. We guarantee that after our work, the character is ready for animation without rework: all bones map to Humanoid, weights are distributed without artifacts, and the Animator Controller is designed for the specific gameplay. Our team has been doing game character rigging for over 7 years and has completed work for 150+ characters in projects of various genres — from mobile RPGs to PC action games. Order rigging from us — and get a skeleton ready for animation from the first import.

What Are the Skeleton Requirements for Humanoid Avatar?

Unity works with two rig types: Generic and Humanoid. The choice affects the entire animation pipeline.

Generic rig — arbitrary bone hierarchy. Animations are tied to a specific model, retargeting is impossible. Suitable for non-character animation (vehicles, doors, creatures with non-standard anatomy).

Humanoid rig — Unity maps bones to a standard schema of 17 mandatory bones (spine, head, arms, legs) and up to 32 optional ones. After that, any Humanoid animation can be applied to any Humanoid character. This is the foundation for retargeting and Animator Controller with Blend Tree. Humanoid rig speeds up animation creation by 2–3 times compared to Generic, since ready-made animations from the Asset Store work without adaptation.

Errors that break Avatar mapping:

• Incorrect bone orientation. Unity expects the X-axis to point along the bone toward the child bone. If the arm points along Z or -Y — the Avatar will be generated with a distorted T-pose.
• Extra intermediate bones in the spine chain. If there is an unmapped intermediate bone between Spine and Chest — it gets lost during retargeting, spine animation looks stiff.
• Roll bones (twist bones) — bones for distributing forearm and thigh twist. In Humanoid, they must be added as additional (non-mandatory) bones with correct weight painting. Without twist bones, the forearm twists unnaturally when the hand rotates.

T-pose vs A-pose

Unity recommends T-pose as the bind pose. A-pose (arms down at ~45°) technically works, but retargeted animations will have small shoulder joint errors — up to 5° deviation. For characters with armor or broad shoulders, A-pose is sometimes preferable: less mesh stretching during retargeting. The decision is made at the rigging stage, redoing it later is expensive.

Avatar Mask

Avatar Mask is a tool for partial application of animations. For example: the lower body plays a run animation, the upper body plays a shoot animation. Without Avatar Mask, these states conflict. The correct Animator Controller structure for a shooter:

Base Layer (Full Body weight: 1.0)
  └── Locomotion Blend Tree (idle / walk / run / sprint)

Upper Body Layer (Avatar Mask: upper body, weight: 1.0)
  ├── Idle_upper
  ├── Shoot
  ├── Reload
  └── Aim_offset (2D Blend Tree by pitch/yaw)

Additive Layer (Avatar Mask: spine, weight: by parameter)
  └── Lean_left / Lean_right

Example of Avatar Mask setup: in Unity Inspector, select Animator Controller, open Layers -> Add Layer -> choose Avatar Mask. For Upper Body, create a mask enabling shoulder girdle, arms, and head bones. For Additive, only spine. Uncheck the legs.

Additive layer for leaning is a typical optimization: instead of 8 separate animations (run_left, run_right, walk_left...), one additive lean is applied on top of any state. Time savings on clip creation — up to 40%. For complex projects, this reduces the animation budget by 15–20%.

How to Set Up a Blend Tree for Locomotion?

Blend Tree is a system for blending animations based on one or two parameters. For character locomotion, the standard is 2D Freeform Directional with parameters velocityX and velocityZ.

Minimum set of clips for basic locomotion:

Freeform Directional interpolates between clips by angle and magnitude of the velocity vector. At velocity (0.35, 0.35), Walk Forward and Strafe Right are mixed with weights calculated by distance to each point in 2D space.

Root Motion vs. In-Place Animations

Root Motion — character movement is driven by the root bone displacement in the animation clip. The animator "bakes" movement speed into the animation. Unity reads this displacement and moves the character Transform. Pros: animation and movement are always synchronized (steps match displacement). Cons: harder to control speed via code, requires correct setup in Animator (Apply Root Motion: true).

In-Place — the pelvis bone stays in place, movement is controlled by code (CharacterController or Rigidbody). Easier to integrate with physics systems, but risk of step-to-speed desynchronization (slipping feet).

In-Place animations with Foot IK via the Animation Rigging package (Unity) are better for games with complex terrain, as they ensure precise foot placement on uneven surfaces, saving 15–20% of time on manual animation correction.

Why Do Skinning Problems Occur and How to Solve Them?

Skinning (binding mesh to bones via weights) is the most labor-intensive stage of rigging organic characters.

Tools: Maya (Weight Paint tool + Component Editor), Blender (Weight Paint mode + Vertex Group Editor), 3ds Max (Skin modifier + Weight Table).

Problem areas and solutions:

Proper skinning from the start saves up to 60% of the animation rework budget. — and we add weight math and blendshapes to make movements look natural. To avoid similar issues on your project, get a rigging consultation right now.

Combat Animations and States

A combat animation system is not just a set of clips. It is a state graph with transition conditions and interrupt priorities.

Typical mistake: transition from Idle → Attack with Has Exit Time: true and Exit Time: 0.9. This means the attack will start only when idle has played 90% (0.5 seconds). The player presses the attack button and waits half a second. Solution: Has Exit Time: false, transition by trigger, Interruption Source: Current State with priority.

Combat states structure:

Any State → Hit Reaction (trigger: onHit, interrupts current)
Any State → Death (trigger: onDeath, interrupts all)

Attack Layer:
  Idle → Attack1 (trigger: attack)
  Attack1 → Attack2 (trigger: attack, exit time: 0.6)
  Attack2 → Attack3 (trigger: attack, exit time: 0.6)
  Attack1/2/3 → Idle (no trigger, exit time: 1.0)

Combo-window opens at ~40% of animation length and closes at ~80%. This creates a sense of responsiveness without breaking the animation.

When Should You Use Spine 2D?

Spine is the standard for 2D animation in mobile RPGs, idle games, action-platformers. The character mesh is split into parts attached to a 2D skeleton. Animation — bone transformations, mesh deformation via weighted vertices.

Advantages over frame-by-frame:

• Animation file size is kilobytes instead of megabytes (spritesheets). Typical savings — 80–90% of build size.
• Retargeting: same attack animations work on different characters with identical skeleton structure.
• Animation blending and IK — same concepts as in 3D.

Integration in Unity: official Spine Runtime for Unity. The SkeletonAnimation component controls playback, SkeletonMecanim allows using Animator Controller on top of the Spine skeleton. For programmatic animation — direct control via API: skeletonAnimation.AnimationState.SetAnimation(0, "walk", true).

DOTween is often used in conjunction with Spine to control non-skeletal animations of UI elements attached to the character (health bar, damage numbers) — not for the skeleton itself, but for synchronizing UI with game events.

How We Work

1. Analysis — examine gameplay, determine list of animations, rig type (Humanoid/Generic), IK and layer requirements.
2. Skeleton design — create bone hierarchy in Maya/Blender considering Humanoid Avatar, add twist bones, corrective shapes.
3. Skinning — manual weight refinement in problem areas, verification via Unity Avatar Tester.
4. Animation creation — locomotion, combat, reactions, cinematics. Set up Animator Controller with Blend Tree and Avatar Mask.
5. Testing and optimization — check in target scene, profile draw calls, eliminate stutter, configure asset streaming.
6. Delivery — hand over project with documentation and support.

What You Get

• Skeletal model with correct Humanoid Avatar (or Generic) — FBX/glTF file.
• Set of animation clips — FBX with AnimationClips.
• Animator Controller with configured layers, Blend Tree, and transitions.
• Documentation on controller structure and code usage.
• Support during integration — we answer questions, fix inaccuracies.

Estimated timeline: 5 to 15 working days depending on complexity (number of animations, rig type, Spine 2D presence). Cost is calculated individually after scope assessment — contact us for consultation and a rough estimate. Order game character rigging — and your characters will come to life without animation bugs.