Rigging characters for animation system requirements
Skeleton that "just moves" in Maya preview – one thing. Skeleton that works correctly in Unity Animator with Humanoid Avatar, supports IK through Animation Rigging, doesn't break Blend Tree transitions, and properly transfers Motion Capture data – completely different story.
Most rigging problems manifest not during creation, but at engine integration stage. The later they're discovered, the more expensive the fix.
Key requirements for Unity Humanoid Avatar
Unity Mecanim with Humanoid configuration imposes strict skeleton constraints. System expects certain bone hierarchy: Hips → Spine → Chest → UpperChest → Neck → Head. Additional bones can be added, but main chain must match.
Problem starts when artist adds bones for convenience: additional Spine2.5 between Spine and Chest, BustBone for chest, BreathBone for breathing. Unity either ignores them during Avatar mapping, or breaks automatic mapping entirely, and rig must be assigned manually.
Second common error source – bone orientation. Unity Humanoid expects bones oriented along specific axes. Arm bone rotated "wrong way" in source space, on retargeting animation produces twisted elbow. Standard: arm bones' Y-axis points shoulder to hand, Z-axis forward along palm.
T-pose vs. A-pose. Unity Humanoid works with both, but for animation retargeting (especially Mocap libraries from Mixamo or Rokoko), T-pose is standard. A-pose gives better shoulder deformation in skinning, but creates offset when applying T-pose animations – needs compensating Avatar Mask or manual correction.
VR-specific rigging
In VR appear requirements absent in regular gamedev.
Full Body IK for avatars. If player sees their body in VR, head position and arm positions (controllers) must drive entire skeleton so avatar looks alive, not wooden mannequin with arms in right positions. Unity Animation Rigging package provides Constraints: TwoBoneIK for arms, MultiParentConstraint for torso, ChainIK for spine. Rig must be designed accounting for these constraints: separate target-bones for IK goals, correct influence bone hierarchy.
Finger joints critical in VR. If Hand Tracking used (Meta Hand Tracking SDK, OpenXR Hand Interaction Extension), joint position data arrives directly from headset. Skeleton must have exact hierarchy SDK expects: ThumbMetacarpal → ThumbProximal → ThumbDistal → ThumbTip and similarly for other fingers. Hierarchy deviation – retargeting broken.
Procedural animation support. VR-games often need procedural adjustment: character legs adapt to uneven floor through IK, head rotates toward point of interest independent of body. This requires separate IK chains with explicit constraint targets, not mixed with FK-bones.
Rigging process
Begin with analyzing technical requirements: engine, Unity version, Mocap needed, Hand Tracking required, Avatar Mecanim or Generic rig.
Building skeleton in Blender or Maya respecting axes and naming. Avatar mapping test in Unity before skinning – important step saving time. If mapping incorrect, fix skeleton before skinning.
Basic skinning with weight painting: automatic as starting point, manual correction of critical zones – shoulder, neck, fingers, knee. Deformation test on control poses.
If project requires – Corrective Shape Keys / Blendshapes for deformation artifacts (shoulder bulge, elbow kink).
| Task | Estimated timeline |
|---|---|
| Humanoid rigging for Mecanim (without skinning) | 4–8 hours |
| Rigging + skinning full character | 2–4 business days |
| VR Avatar rig with IK and Hand Tracking support | 3–5 business days |
| Revision/adaptation existing rig | 1–3 business days |
Cost determined after analyzing project requirements.





