Character FX & Animation / Houdini
Rigging Revolution | Guide Skeleton
Written guide

Playing loads YouTube content. YouTube processes data after activation.
Watch on YouTubeIf the player is blocked or unavailable, use Watch on YouTube.
Build a small guide skeleton alongside the character’s existing main skeleton. Its six points describe a root, a center of gravity and pole-vector guides for both knees and elbows. Later rigging components can use those locations without confusing them with the full set of deformation joints.
The lesson assumes the character’s main skeleton and a controller containing its name already exist. It creates a base guide structure that will be extended later; it does not build the IK solver or final animator controls. The exact Houdini version is unverified.
Create the root and derive a center-of-gravity guide
At 00:00, use Add to create one point for the guide root. Add a name that incorporates the existing character-name parameter through a relative reference. The instructor revises the suffix while typing, but the stable intent is a character-specific, center-side root name.
Use point names for this setup. At 02:00, the instructor explicitly corrects the naming class so the points receive their names. A label applied to the wrong element class will not provide the point identity expected by the subsequent joint workflow.
Import the pelvis location from the existing construction and rename that point for the guide’s center of gravity, or COG. Its position comes from the pelvis, while its name and later parent relationship describe a different responsibility. Keeping that reference to the original construction avoids manually recreating a location that already exists upstream.
Derive knee and elbow guides from the existing locations
At 02:00, repeat the import-and-rename pattern for the left knee, then copy it for the right knee. Change both the referenced side and the output name. The instructor briefly thinks a pnt suffix should be jnt, then recognizes that these source objects are points and restores the existing naming convention. Inspect the actual source names before “correcting” them.
At 05:03, move the knee guide points forward along Z so they sit ahead of the knees. The spoken value is revised around 3 and 2 units; the reliable lesson is the offset’s purpose, not a universal final distance. A later shared control for the offsets is proposed but not built here.
Around 06:03, derive the elbow guides in the same way and offset them in the opposite Z direction, with −2 used in this scene. Replace the knee reference with the elbow reference and update the side-specific name before copying for the other arm.
The imported position establishes which limb the guide belongs to. The offset establishes a separate location that a later IK component can use for bending guidance. These are scene-scale choices; this lesson does not test the resulting limb behavior yet.
Replace the manual line construction with explicit parenting
At 04:01, the instructor initially uses several Merge and Add branches to create connecting lines between guide points. This becomes cumbersome when the elbow guides need a different parent from the knee guides.
At 08:01, the approach changes. Merge the guide points, pass them through Rig Doctor, then use Parent Joints and the rig tree to establish the hierarchy. This is the accepted construction path; the earlier hand-built line network is an abandoned approach, not another required layer to retain.
At 09:00, the final relationships are:
| Child guide | Parent guide |
|---|---|
| COG | Root |
| Left elbow pole vector | COG |
| Right elbow pole vector | COG |
| Left knee pole vector | Root |
| Right knee pole vector | Root |
The hierarchy separates the upper-body guides from the knee guides while giving both a common root. Inspect the rig tree after assigning the parents. A merged collection of correctly positioned points does not by itself prove that these relationships have been established.
Publish a clear output for later rig components
At 09:00, organize the guide construction in a network box and add a named output null for the guide skeleton. The instructor corrects a color operation that affected the nodes when only the box was intended to change, then saves the scene.
Inspect the output for six distinctly named points and the intended hierarchy. The root and COG should remain separate identities even if their locations happen to be close in a particular character. Check that both elbow and both knee references belong to the proper side.
This output is a guide skeleton alongside the main skeleton, not a replacement capture skeleton. The later APEX IK lesson uses guide references and exposes why exact names and valid selections matter. Here the handoff is simply the saved positions, names and parent relationships needed for that later work.