# Ep.1 — Reference Pipeline 101 (Folder Structure Design Rules)

https://youtu.be/qGYcZd67eNA?si=5uRxdGBzGYs1O8aj

> **Summary**: The very first step to running a stable reference system is to **strictly separate the 'Master Rig folder' from the 'Animation Scene folder' and ensure they never mix.**

---

## 1. The Painful Background That Inspired This Episode

Maya-centric studios have long established the separation of rigs and animation as a baseline rule. However, when inspecting teams that grew around 3ds Max or Blender, a surprising number mix files haphazardly without any standardised folder convention.
In the presenter's experience, **6 out of 10 companies** have completely tangled folder structures. This problem is most severe in teams where there is no dedicated rigging department and a generalist handles everything.

If you have decided to adopt Fast-Ref, the **prerequisite of organising the folder structure** must be satisfied before even launching the tool — otherwise the pipeline will not function correctly.

---

## 2. The Two File Types You Must Never Mix

An animation pipeline should contain exactly two types of core files.

| File Type | What Goes Inside | ❌ **What Must Never Go Inside** |
|-----------|------------------|----------------------------------|
| **Original Rig File** | Skeleton, controllers, skin weights, mesh | **Animation keyframes** |
| **Animation Scene File** | Animation data keyed after linking (Add) the rig file | Any direct edit of the original rig source |

### 🚨 Common Anti-Patterns
1. **Saving test animation onto the original rig**: Testing "does this rig move well?" then absentmindedly saving keyframes into the master rig file. (Test keys must always be saved to a separate temp file or `.bip`.)
2. **Opening the rig file and 'Save As' to start animating**: The most common and destructive approach. It severs the original rig's connection relationships and creates a hardcoded single file, meaning any rig revision requires discarding the entire scene.
3. **Merging the full rig into the scene instead of linking**: The scene becomes locked with heavy rig data, making it impossible to reflect any rig revisions.

---

## 3. The Engine Catastrophe When Animation Ends Up in the Rig File

This is a true story from joining a Blender-based studio as an Animation TA. When asked "Where is the master rig file for Character A?", the rigger handed over a file that, when opened, had **the character's elaborate ultimate skill animation baked right into the default pose**.
A predecessor had worked on the animation and accidentally saved it directly on top of the master rig file.

### 😱 The Butterfly Effect of Bind Pose Corruption
- Importing a rig that has animation keys baked into it as a Skeletal Mesh in Unreal or Unity causes the **character's initial default pose (bind pose) as recognised by the engine to become completely distorted**.
- Because the baseline body shape data is corrupted, no matter how perfect the animation clips applied to that character are afterwards, **joints continuously twist and deform in hideous rendering bugs inside the engine**.
- Ultimately, a TA has to be brought in to manually strip all animation data and restore the rig to a clean A-pose/T-pose — unnecessary work that wastes everyone's time.

---

## 4. Clear 'Territory Separation' Between Departments (Recommended NAS Folder Structure)

In an environment where dozens of artists (e.g. a 35–40 person animation team) collaborate, completely isolated rules are essential.

```
Project_Super/ (Network shared drive)
  ├─ rigging/             ← Rigger territory only (riggers have write access)
  │   └─ CH_Mable/
  │       ├─ master_mable.max   (Clean rig — zero animation keyframes)
  │       ├─ textures/          (Texture folder referenced by relative path)
  │       └─ old/               (Old version history backup)
  │
  └─ animation/           ← Animator territory only (animators have write access)
      └─ Scene_Walk/
          └─ walk_mable_v01.max (File that 'Add'-linked master_mable.max via Fast-Ref)
```

### 🚫 Strict Access Rules
- **Riggers**: May view the animator folder but must never directly intervene and overwrite animator scenes.
- **Animators**: May open master rig files in the rigging folder as read-only references, but must **never create or overwrite any file inside the rigging folder.**

---

## 5. "Keep the Chaos Ratio Below 7%"

As production progresses, perfect adherence to rules is impossible — a certain level of file disorder (Chaos) will inevitably arise.
However, the presenter sets a guideline to keep the **pipeline's overall chaos index below at least 7%**, actively directing traffic whenever files start to tangle.

The driving force behind this tidying cannot be junior artists who feel too awkward to step in, so **the lead or practising TA must firmly hold authority, define folder hierarchies and file access permissions, and regularly filter things out.**

Only with a solidly designed 'Master Folder Rule' in place can Fast-Ref's automatic checking and replacement features truly spread their wings.