Creating Locomotion Animation Cycles (Walk, Run, Jump) for Games

We develop locomotion animation networks—from simple idle/run sets to complex setups with blend trees, foot IK, and root motion. With over 10 years in gamedev and dozens of projects for Unity and Unreal Engine, we know that a poorly made locomotion set makes the character slide, float, or jerk at transitions—visible from the first second of gameplay. We guarantee your animations will perform flawlessly.

Why Blend Tree Outperforms State Machine for Locomotion

A common mistake is building locomotion through separate animation states in a State Machine with cross transitions. It looks fine in the Animator window, but in practice, transitioning idle → walk → run requires managing three transition thresholds and crossfade times, and any change in speed parameter creates noticeable blending artifacts.

A 1D Blend Tree by Speed parameter elegantly solves this: Unity interpolates between idle, walk, run, and sprint along a single axis, automatically normalizing weights. Thresholds: 0 — idle, 0.5 — walk, 1.0 — run, 2.0 — sprint. Set thresholds via Compute Thresholds → Velocity Z, which auto-calculates values based on root motion velocity in each clip.

A 2D Blend Tree (Simple Directional or Freeform Directional) adds a second axis—Strafe. Needed for shooters and action games where the character moves in 8 directions. It's critical to set the center point (0, 0) correctly—it should reference an idle clip with zero movement; otherwise, diagonal movement blending yields incorrect weights.

Root motion is a separate concern. If animations are made with root motion (character movement encoded in root bone motion), ensure: identical cycle step between walk and run (otherwise foot sliding during blend), and correct bake axes in Unity (Apply Root Motion → Bake Into Pose for vertical and horizontal axes depending on the project). For a walk cycle, the loop length in Unity is set via Loop Pose + Cycle Offset—if the clip isn't perfectly looped, a visible "bounce" occurs at the end of the cycle.

Setting Up Foot IK for Perfect Surface Contact

Without Foot IK, the character's feet will sink into uneven terrain or hover above it. The Unity Animation Rigging package provides the Two Bone IK Constraint for legs—this is the preferred approach in Unity 2022+. The older approach using OnAnimatorIK + animator.SetIKPosition still works but is less flexible when switching between multiple rigs.

Correct Two Bone IK setup: Effector target is a transform that raycasts to the terrain surface. Hint target is the knee position. Weight is controlled by a curve based on the foot's phase in the step cycle (when lifting off, weight → 0; when contacting, weight → 1). Without this curve, the IK will snap the leg during lift-off.

The foot contact frame in a walk cycle is crucial: exactly at the frame when the foot should touch the ground, it must have zero vertical velocity. This is called the foot plant frame and must be set via Loop Pose curves or manually in the animation editor.

What's Included in a Typical Game Locomotion Set

Minimal set for a third-person action character:

• Idle (2–3 variants with additive breathing layer)
• Walk forward / backward
• Run forward
• Sprint
• Strafe left / right (walk and run)
• Jump start / in-air / land (heavy and light landing)
• Turn in place (45°, 90°, 180°—needed for correct Foot IK)

For mobile projects, the set is often reduced to 6–8 clips with aggressive blending. For AAA projects, we add: crouch locomotion, prone, climb transitions, root motion for turns.

Jump is especially complex—it's not one clip but three or five states: anticipation → take-off → peak → descent → land (+ heavy land at high speed). Transitions between them are controlled by parameters IsGrounded and VerticalVelocity, computed by CharacterController or Rigidbody. If the transition from in-air to land uses a fixed duration instead of Exit Time = 0 with a conditional trigger, the landing will lag or be interrupted.

How to Reduce Animation Debugging Time

Some issues are typical and avoidable. Here is a checklist from our engineers:

• Verify all clips are looped (Loop Pose) with zero offset.
• Ensure root motion is consistently oriented along the Z axis for all clips.
• Set Blend Tree thresholds based on actual velocity, not manual values.
• Use weight curves for Foot IK, not constant values.

Our Work Process

First, we analyze references and agree on key parameters: walk/run speed (units per second), jump height, movement style (heavy soldier vs. light ninja). Then we block key poses in Maya or Blender and export test FBX for mapping verification in Unity.

After approving the blocking, we perform spline interpolation and fine-tune secondary motions: arm swing, head bob, torso rotation. The final stage is integration into Animator Controller, setting Blend Tree parameters, testing foot IK, verifying loop points and transition timing.

Contact us to assess your project. We'll select the optimal animation set for your budget and timeline. Get a consultation—our engineers are ready to answer questions and propose a turnkey solution.

For more on Blend Trees, see the official Unity documentation.

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.