Your per-machine setup. Bind each project's folders to this computer, point at a shared configs folder, and choose what FabricatorStudio loads into Maya at startup.
WHAT IT DOES
Everything that belongs to you and this machine
Settings holds what belongs to you and this computer rather than to the project: where the shared configs live, where each project's folders sit on your drives, and which integrations load into Maya at startup. Mindmeld defines the project. Settings binds it to your machine.
Mindmeld
Defines the project: engine template, asset classes, subpaths. Shared across the whole team.
Settings
Binds it to this computer: drive letters, folder roots, and what loads into Maya. Local to you.
THREE PARTS
Configs root, project bindings, Maya integration
Shared Configs Root
Points at your studio's shared configs folder. Solo? The local default just works, so leave it alone.
Project Bindings
Per project: your Source Art Root (working files) and Content Root (where exports land) on this machine.
Maya Integration
Menu, shelves, hotkeys, and the animation marking menu. Choose what loads at startup. All on by default.
THE WINDOW
Bind and point, top to bottom
- 01
Shared Configs Root
One path to the studio's shared configs. Solo builds fall back to LOCAL DEFAULT.
- 02
Project Bindings
Pick a project, set Source Art and Content Roots, then Bind. Optional library overrides sit below.
- 03
Maya Integration
Toggle menu, shelves, hotkeys, and the marking menu. Applies at Maya startup.
- 04
Validation and Log
Collapsible panels surface problems and a filterable activity log as you bind.
- 1
Left-click the gear button on the FabricatorStudio toolbar. Right-click keeps the quick toolbar options.
- 2
Solo? Skip Shared Configs Root, the local default just works. On a team, click Browse and point at your studio's shared configs folder.
- 3
Under Project Bindings, select a project, browse to your Source Art Root and Content Root, and click Bind.
- 4
Under Maya Integration, choose what loads at startup: menu, shelves, hotkeys, and the animation marking menu. Everything is on by default.
Bind writes locally only
Bind writes a small file on this machine only. The shared project config never changes, so binding works even when the shared folder is read-only, like an unopened Perforce path.
Every machine binds its own roots
Teammates can use completely different drive letters and folder layouts. Each machine binds its own roots; the project does not care.
Overrides stay blank in the normal case
Pose Library, Anim Library, and Blueprints stay blank, meaning "under Source Art Root at the project's subpaths". Set one only when this machine keeps that data somewhere else.
Studio environment variable wins
If your studio sets FABRICATOR_PROJECT_CONFIGS, it wins over anything picked here and the field locks with a note saying so.
Toggles: on is immediate, off waits
Turning a Maya Integration toggle on builds it immediately. Turning one off takes effect the next time Maya starts.
A new teammate's whole setup is this one window
Point at the studio configs, bind roots per project, done. Every FabricatorStudio tool then resolves paths for that machine automatically.