Biped Character Rig Part 1 - Setting A Project and Referencing Files

The first biped-rigging lesson prepares the project and separates the character’s model file from the rig file. A stable current-model file is referenced into the rig, while numbered working files preserve development versions. The result is an organized starting scene, not a rigged or bound character.

The demonstration begins with an existing character model and its project folder. You should be comfortable saving Maya scenes and choosing files in the reference dialog. The recording does not establish an exact Maya release.

Set the project and separate the working areas

During 00:02–02:02, the instructor sets the character folder as the Maya project and creates the default workspace. He then adds folders for models, blend shapes and rigs as the organization develops.

The models area holds modeling work; the rig area holds rigging versions. The blend-shape folder anticipates facial work later in the series. Creating those folders does not generate any rig or facial shapes—it establishes places for the related work to live.

The instructor explains that modeling and joint placement can proceed alongside one another. He also qualifies that flexibility: topology changes affect binding and skin weights. A model update is not automatically harmless simply because the rig references a separate file.

Maintain a stable current model alongside working versions

Around 02:02–04:00, the model is saved using a current-file designation. A new scene becomes the rig scene, with both a current rig filename and a numbered initial working version.

These filenames have different roles. The numbered file identifies a working iteration. The current file is the stable destination the workflow intends other files to use. The instructor plans to update that current copy when a working version is ready to become the current result.

Inspect the save destination and filename at each step. Saving a working iteration and replacing a current file are separate actions, even if the scene contents happen to be identical at the beginning. The demonstration is a manual file convention; it does not implement automated version control or concurrent-edit protection.

Reference the model into the rig scene

At approximately 04:00, the instructor uses File > Create Reference to bring the current geometry file into the rig scene. The model appears as referenced content rather than as the rig scene’s original modeling work.

The intended dependency is now explicit: the rig scene uses the designated model file. Subsequent modeling work can be prepared separately and the current geometry source updated according to the project’s convention.

The video demonstrates creation of the reference but does not carry out a full model-edit and reference-reload cycle. It also does not test missing paths, namespaces or downstream deformation after a topology change. Those should remain separate checks when extending this setup.

Save the current rig and continue from a working copy

In the closing minute, the instructor saves the referenced rig scene to the current rig filename, deliberately replacing the initial copy. He then explains that development can continue in the working-version file until another current result is ready.

Before the next lesson, inspect the active project, the geometry reference and the saved rig locations. The important habit is to know which file is a working iteration and which file other work is expected to depend on. That distinction supports continued modeling and rigging without implying that every future model change will preserve a finished bind.