Creating a Base Skeleton | Maya Python Rigging Series

Before automating joint placement, this lesson builds a manual reference on one side of a character. The reference supplies positions for later Python work. The instructor explicitly defers joint orientation and scripted naming, so the result is a placement template rather than a finished deformation skeleton.

Start with the character visible in Maya and be comfortable creating joint chains and switching between orthographic and perspective views. The exact Maya release is not identified in the transcript.

Establish the center chain and limb landmarks

During 00:02–04:02, the instructor places the center chain from the pelvis through the waist, rib cage, neck and head. He includes a top-of-head point and an aim/reference point to indicate the facing direction. Their role in this lesson is to supply positional information for the subsequent script.

The arm begins at the clavicle, continues through the shoulder and elbow, and ends at the wrist. The leg follows the hip, knee, ankle, ball of the foot and toes. These are landmarks on the demonstrated character, not a prescription for every character’s joint count.

Placement is checked in another viewport as the chains are created. The knee placement is undone and corrected before continuing down to the ankle. That revision illustrates the main task: resolve the intended pivot location before treating it as reference data.

At one point the instructor corrects his spoken display shortcut from F4 to the number 4. The correction matters when following the recording; do not preserve the first utterance as an instruction.

Use several views to place the hand

Around 04:02–07:04, a palm point and thumb chain are placed. The instructor notices an unwanted joint selection, ends that operation and starts again. Accidentally carrying a selection into joint creation can change which chain is being extended.

The hand is difficult to judge because geometry overlaps in the side view. The instructor checks the 3D view, finds a point too high and adjusts it. He also undoes a finger placement and inspects the pivot from several angles before proceeding.

The important comparison is between a point that looks plausible in one projection and a point that occupies the intended volume in three dimensions. A side view can help establish a profile while leaving depth uncertain. Use the other views to resolve that uncertainty before extracting positions for the script.

Adapt the repeated finger chains

The remaining fingers begin as repeated copies of a roughly positioned chain. The instructor then adjusts each to fit the hand rather than accepting the copied placement unchanged.

Around 08:03–09:01, the pinky needs particular attention because it is shorter and lower than the other fingers. Reusing a chain saves construction effort, but its copied coordinates are only a starting point. Check the base, intermediate pivots and endpoint of each finger against the character.

The source repeatedly states that position is the current priority. The later Python process will address alignment. This does not mean orientation is unimportant to the final rig; it means orientation is not established by this reference-building pass.

Connect the reference and define the handoff

In the last minute, the instructor parents the separate chains together by selecting child, then parent, and pressing P. The purpose is to inspect the connected skeleton layout. Although the speech briefly calls it a single mesh, the demonstrated operation connects joints into a hierarchy; it does not merge character geometry.

By 10:01, the source has the half-skeleton needed for the next lesson. The useful handoff is a reference whose joint positions have been checked across views and whose connections can be inspected. Scripted coordinate extraction, mirroring, joint orientation and skin binding remain separate work. Automating this template will reproduce its placement decisions, so resolving an ambiguous pivot now is more valuable than reproducing that ambiguity quickly in code.