DCC production guide
Rig Constraints and Rotation Order Guide
Direct answer: Assign every constraint to a named owner, choose Rotation Order from the axis that animates last, test Euler Rotation for Gimbal Lock, select the bind method from mesh topology and joint distance, and publish Corrective Shape fixes only after deformation evidence passes.
Aim ConstraintCorrective ShapeEuler RotationGeodesic Voxel BindRotation Order
Constraint ownership map
Every Aim Constraint, Orient Constraint, Parent Constraint, and Point Constraint needs an owner: animator control, technical rig node, export skeleton, or temporary setup helper. If ownership is not written, someone will bake the wrong node or delete the driver during cleanup.
Aim and up-vector rules
Aim Constraint failures usually come from missing up-vector policy. Record aim axis, up axis, world up object, and whether flipping is allowed. Eyes, weapons, cameras, and tentacles need different rules: an eye can aim from a control, while a weapon socket often needs parent space stability.
Symptoms include sudden flips at 180 degrees, mirrored side drift, or controls that look correct until the character turns. Fix by adding a stable up object, changing local axes, or moving the constraint above the export layer.
Euler rotation order choice
Euler Rotation is predictable only when Rotation Order matches the animation job. Put the axis with the largest continuous motion last in the order, because it is evaluated with the most freedom. A shoulder that lifts and twists may need XZY or YXZ, while a door hinge should use an order that protects the hinge axis.
Gimbal lock test
Gimbal Lock is not a theoretical warning; it is a pose test. Rotate the control into its production extreme, then try the secondary axis. If the manipulator loses a degree of freedom or channels spike, the order is wrong or the control needs a different rig design.
Bind method selection
Heat Map Binding is fast for clean meshes with reasonable joint proximity. Geodesic Voxel Bind is better when limbs are close together, meshes overlap, or standard heat maps leak through geometry. Record bind method, max influences, dropoff, normalization, and excluded joints before painting weights.
Corrective shape ownership
Corrective Shape targets should belong to the deformation layer, not to animator controls. Name the driver pose, affected mesh, side, and combination rule. Correctives for shoulder collapse, elbow candy-wrapper twist, or knee volume need documented triggers so later rig edits do not orphan them.
Export skeleton constraints
Game export usually wants baked transforms on a clean joint hierarchy. Keep constraints, IK solvers, and helper nodes outside the export skeleton unless the pipeline bakes them deterministically. Write which controls are baked, which joints are exported, and where bind pose is stored.
Failure symptoms: engine skeleton imports with extra nodes, animation offsets after retargeting, or constraints evaluated differently between Maya and engine. Fix by baking export joints from the rig layer, then validating curves on the exported file.
Creature head rig decision
Example: a creature head tracks a target while the neck deforms. Put Aim Constraint ownership on the head look control, use a world up object parented to chest space, choose Rotation Order for the head control after testing yaw-heavy motion, bind the neck with Geodesic Voxel Bind if volumes overlap, and add Corrective Shape targets for extreme twist.
Constraint failure evidence
Attach constraint list, owner map, rotation order table, gimbal test poses, bind settings, corrective driver list, exported skeleton hierarchy, and engine playback screenshot. The evidence should prove whether the bug is rig evaluation, skin weighting, corrective triggering, or export baking.
Rig constraint terminology
| zh | en | ja | Production context |
|---|---|---|---|
| 目标约束 | Aim Constraint | エイムコンストレイント | 绑定、蒙皮与高级角色技术 |
| 校正形状 | Corrective Shape | 補正シェイプ | 绑定、蒙皮与高级角色技术 |
| 欧拉旋转 | Euler Rotation | オイラー回転 | 绑定、蒙皮与高级角色技术 |
| 测地线体素绑定 | Geodesic Voxel Bind | 測地線ボクセルバインド | 绑定、蒙皮与高级角色技术 |
| 万向节锁 | Gimbal Lock | ジンバルロック | 绑定、蒙皮与高级角色技术 |
| 热力图绑定 | Heat Map Binding | ヒートマップバインド | 绑定、蒙皮与高级角色技术 |
| 方向约束 | Orient Constraint | オリエントコンストレイント | 绑定、蒙皮与高级角色技术 |
| 父约束 | Parent Constraint | ペアレントコンストレイント | 绑定、蒙皮与高级角色技术 |
| 点约束 | Point Constraint | ポイントコンストレイント | 绑定、蒙皮与高级角色技术 |
| 旋转顺序 | Rotation Order | 回転順序 | 绑定、蒙皮与高级角色技术 |
Rig Constraints and Rotation Order Guide FAQ
Who should own constraints in a production rig?
Animator-facing behavior belongs on controls, technical evaluation belongs in the rig layer, and export joints should usually receive baked transforms only. Ownership must be named so cleanup and export do not remove the wrong dependency.
How should Rotation Order be chosen?
Choose it from expected motion, not from defaults. Test the production extremes and put the axis with the largest continuous motion last so Euler Rotation has the lowest chance of Gimbal Lock in real poses.
When is Geodesic Voxel Bind safer than Heat Map Binding?
Use Geodesic Voxel Bind when nearby limbs, overlapping surfaces, or complex volumes cause heat map leakage. Validate with posed deformation screenshots before painting detailed weights.