Game Character Skeletal Rig Development
We know that a rig for a game is not the same as for film. Here, bones work in real-time, fit within the draw call budget, and don't break when imported via FBX. Artists from film pipelines often learn this when it's too late to redo. Let's be direct: a typical film skeleton with 300+ bones, nCloth, and deformers is a guaranteed stutter on a mobile platform. Our experience (over 50 projects over 9 years) shows that a balanced skeleton saves up to 30% of animation time. According to the Unity Manual, Humanoid Avatar supports a mandatory set of 15 bones (Body, Head, arms, legs) and optional fingers.
How to distinguish a game rig from a film rig
In film, you can have 300+ bones, deformers, and nCloth. In real-time, this is unrealistic. Unity Humanoid Avatar supports a mandatory set of 15 bones (Body, Head, arms, legs) and optional fingers. Generic rig has no limitations but lacks Humanoid features.
Bone counts per platform:
- Mobile (GPU skinning): We recommend up to 75 bones, hard limit depends on GPU.
- PC/Console (Compute skinning): 100–150 is realistic without loss.
- VR: Due to frame budget, no more than 60–80.
Every extra bone is a bone that the animator must account for or exclude via Avatar Mask. Minimal sufficiency is a principle that saves money at all stages.
How many bones does your character need?
The optimal number depends on the tasks. For NPCs, 15–25 bones are enough. For a main character with detailed fingers and facial expressions, up to 100. We test on the target platform to avoid FPS drops. For example, in a recent project, we reduced the bone count from 120 to 70—stutter disappeared, and deformation quality did not suffer. Compare: Humanoid Avatar in Unity processes up to 100 bones faster than Generic with the same count, thanks to optimized blending.
Hierarchy and naming conventions
Root bone is Root (or Hips in Mixamo). Everything else is child. Root is on the ground under the character, not at the center of mass. This is critical for Root Motion: Unity reads movement from Root, and if it's at the pelvis level, the character "floats."
Standard naming without issues:
-
Hips,Spine,Spine1,Spine2,Chest,Neck,Head -
LeftShoulder,LeftUpperArm,LeftLowerArm,LeftHand -
LeftUpperLeg,LeftLowerLeg,LeftFoot,LeftToe
These are Mixamo-compatible names that Unity maps automatically. Any deviation (L_Thigh, Bip001) requires manual mapping on every reimport.
Why correct hierarchy matters?
Incorrect hierarchy is the cause of 90% of IK and retargeting problems. For example, if LeftUpperArm is not a child of LeftShoulder, Unity cannot correctly calculate shoulder rotation. This leads to "dislocations" in animation.
Axis orientation and Bind Pose
Axis orientation in Blender (Y along the bone) differs from Maya (X along). We account for this when setting up IK solvers. Check: Edit Mode, Display → Axes. All axes should point from parent to child. If chaotic—Recalculate Roll via Ctrl+N with Global Positive X option.
T-Pose for Bind Pose is the standard for Humanoid Avatar. A-Pose is technically acceptable, but Unity's auto-mapping may err. Safer: export in T-Pose, then provide an additional clip with A-Pose for skinning.
How to avoid deformation problems?
Use Twist bones. Without them, forearm rotation during pronation/supination creates a "twisted tube." Unity Humanoid supports Upper Arm Twist and Lower Arm Twist as optional. They are added between Shoulder → Forearm and Forearm → Hand.
Weight for Twist bone: 0.5 in the middle, 0 at ends. In Maya—Advanced Twist Controls in IK Handle. In Blender—Bone Constraint → Copy Rotation with Factor 0.5.
Comparison of Humanoid and Generic rigs
| Parameter | Humanoid Avatar | Generic |
|---|---|---|
| IK support | Automatic | Manual setup |
| Animation retargeting | Built-in | Requires conversion |
| Max bone count | Limited (practical up to 200) | Unlimited |
| Performance | Optimized for Unity | Depends on implementation |
Rig development process
Mesh and specification audit → Hierarchy assembly → Axis orientation → Bind Pose check → IK setup → Test animation → Export → Verification in Unity Avatar Configuration.
| Character type | Estimated time |
|---|---|
| Humanoid without fingers (NPC, simple character) | 3 to 6 hours |
| Full humanoid with fingers + Twist bones | 1 to 1.5 days |
| Quadruped or non-standard creature | 2 to 4 days |
| Rig with dynamic elements (tail, cloak) | 3 to 5 days |
What's included in the work
- Ready FBX with correct skeleton (hierarchy, axes, naming).
- IK and Twist bones setup.
- Verification in Unity: Avatar Configuration without warnings.
- Rig documentation (bone list, weights, limitations).
- Post-delivery support: bug fixes, engine adaptation.
Final result: a character that works in real-time without surprises. Order rig development—contact us for a consultation. Our experience and certified specialists guarantee quality. Get a consultation on skeleton optimization for your project.