Chapter 02 / Technical setup
Give the pose room
A good rig lets the animator concentrate on intention. A dependable game rig also makes clear what will survive the trip into the engine.
Test the performance, not the control count
More handles do not automatically create more useful expression. Start with the poses that define the character: a deep crouch, a reaching twist, a supported landing and the most demanding equipment interaction.
Those poses expose the real requirements. They show where a shoulder needs volume, where a wrist needs clean orientation and where the animator needs a simpler way to maintain contact.

Separate the authoring rig from the export contract
The animator may work with constraints, helper objects, custom attributes and procedural controls. The runtime skeleton usually needs a much narrower, explicitly supported representation. Document which joints are exported and how the authored performance is baked onto them.
Define units, axis conventions, reference pose, bone names and hierarchy before production grows. FBX and glTF 2.0 can carry animation data, but they do not guarantee that every authoring feature transfers identically. Treat the chosen format and exporter settings as part of the pipeline contract.
Make controls explain themselves
Group controls by the task an animator is trying to perform. Distinguish body placement from local shaping and make space switching legible. A hand following the world, a weapon or the chest should not require guesswork about which reference space is active.
Inverse kinematics helps preserve contacts; forward kinematics often gives direct control over arcs and overlapping action. Both have a place. Test switching between them without a visible pop, and provide predictable reset behavior so another animator can understand an unfamiliar scene quickly.
Evaluate deformation in motion
A joint can look acceptable in a still pose and collapse during the path into it. Scrub the shoulder through a reach, rotate the forearm under load and watch the pelvis during a deep step. Check volume, skin sliding and the way neighboring regions share the deformation.
Corrective shapes and extra joints can help, but each has runtime and maintenance implications. Confirm which correctives will exist in the target engine and how they are driven. Do not approve a beautiful authoring result that depends on a deformer absent from the shipped character. Include clothing, armor and attached props in the test; their intersections may matter more than a subtle improvement to bare anatomy.
Use representative bodies and equipment
If the production includes multiple proportions, test retargeting early. A motion that transfers cleanly between similar skeletons may fail when arm length, hip width or foot size changes. Check reach, ground clearance and contact rather than assuming that matching joint names will solve the performance.
Autodesk Maya and Blender offer different rigging workflows, while Unreal Engine and Unity have their own runtime systems and import expectations. Avoid treating a tool name as a complete specification. Record the relevant version, settings and supported features, then prove the route with one small asset before standardizing it.
Labelled pipeline diagram
One pose, four checks
Keep the same stress pose visible at every stage. A comparison is much more useful when the camera, character scale and frame are consistent.
Validation pathway · editorial example
- Author — pose using animator-facing controls
- Bake — sample the agreed export skeleton
- Import — apply the documented engine settings
- Compare — inspect contacts, scale and deformation
Budget for runtime behavior
Rig evaluation in the authoring scene is not the same as runtime cost. Bone counts, skin influences, corrective evaluation and procedural solvers interact with the game’s character population and target hardware. Agree on a representative scene rather than judging performance with a single character in an empty level.
Level-of-detail changes deserve an animation review too. Removing a joint or reducing influence quality can alter a silhouette, break a held object or weaken a facial expression. Decide which details are essential at each viewing distance, then verify transitions during actual movement.
Version changes as production events
Once animation production starts, changing a skeleton can affect existing clips, retargeting, attachment points and engine logic. Classify proposed changes: a control convenience may be source-only, while a hierarchy change can require broad migration. Name an owner for that decision and preserve an easy route back to the previous version.
A short rig release note should describe the change, expected impact and required animator action. Include a known-good scene and an export test. This small habit prevents repeated troubleshooting across many workstations and keeps a technical improvement from silently becoming a schedule risk.
Rig readiness checklist
- Approved stress poses work with current equipment.
- Space switches and IK/FK changes preserve the pose.
- Exported motion matches the authored result closely enough for the task.
- Correctives and attachments behave in the target engine.
- Skeleton version, known limits and migration steps are documented.
A rig is ready when it supports the intended work reliably, not when it can perform every imaginable trick. Preserve animator freedom where it affects the player’s reading, and simplify the rest wherever that makes production more dependable.