1. How Flagship works

A DCC add-on writes a small work-order file and a temporary project copy to shared storage. The Manager detects the work order, divides it into tasks, and assigns them to compatible Workers. Workers read shared projects and assets, write render output, and report progress. Any computer on the LAN can open the Manager's web interface.

2. Before you begin

Software and access

• All computers should be Windows systems on the same trusted LAN or VPN.
• Computer 2 needs the render applications required by its jobs. Submission add-ons are not required on a render-only Worker.
• Computer 3 needs Blender and/or After Effects.
• Computer 1 should have a stable hostname or IP address. A DHCP reservation or static address is recommended.
• The Windows accounts running Flagship need read/write access to their shared locations.
• Workers need access to footage, textures, caches, fonts, plug-ins, color-management resources, and final output locations.
• Install matching DCC versions, render engines, codecs, fonts, and third-party plug-ins on Workers.

Create shared folders

\\FILESERVER\Flagship
├── Work Orders
├── Temporary Projects
└── Temporary Output

Prefer UNC paths over mapped drive letters. A mapped drive such as L: might not exist for another user, an elevated process, or a process launched at startup.

Open Manager network ports

If UDP discovery cannot cross a VLAN or VPN, configure the Manager IP manually in Worker Settings. TCP 32761 must still be reachable.

3. Install and configure the Manager

1. Copy or extract the complete Flagship Manager version folder to a permanent local folder. Keep its packaged files together.
2. Run Flagship_Manager.exe. On the activation page that opens, enter the promo code supplied by MutinyFX and select Start 30-day trial. Activate on the Manager computer while it has internet access.
3. Allow Flagship through Windows Firewall if prompted. On an organization-managed computer, ask an administrator to run Configure Flagship Firewall.cmd from the release package or deploy TCP 8008, TCP 32761, and UDP 32762 for the Manager.
4. After activation, on the setup page enter:
   • Work Orders: \\FILESERVER\Flagship\Work Orders
   • Temporary Projects: \\FILESERVER\Flagship\Temporary Projects
   • Blender Temporary Output: \\FILESERVER\Flagship\Temporary Output
5. Leave Create folders that do not already exist enabled if the Manager account may create them.
6. Select Save and continue. Flagship verifies write access and opens the main interface.
7. Leave the Manager running whenever jobs are submitted or rendered.

From Computer 3, open http://MANAGER-IP:8008, for example http://192.168.1.25:8008.

Verify the Manager

1. Confirm Flagship_Manager.exe is running.
2. Use ipconfig on Computer 1 to confirm its IPv4 address.
3. Test the exact IP-based URL from Computer 3.
4. Check TCP 8008 and the active Windows network profile.

4. Install and configure a Worker

1. Install Blender and/or After Effects on Computer 2, including matching project dependencies.
2. Copy or extract the complete Flagship Worker version folder locally. Keep the executables, FFmpeg, and packaged files together.
3. Run Flagship Worker Settings.exe.
4. Enter a unique name such as RENDER-02.
5. Browse to aerender.exe and blender.exe. The current Settings utility expects both to be valid. Fusion is optional future support.
6. Enter Computer 1's IP and port 32761.
7. Choose None (accept any job) for a general Worker, or restrict its default render application.
8. Choose Render-only node unless the machine uses a licensed full After Effects installation.
9. Select Save, then start FlagshipWorker.exe.
10. In the Manager UI, confirm the Worker appears. Click its name to review reported applications, paths, address, GPU capability, and status.

Worker settings are stored at C:\Users\Public\Documents\Flagship_Worker_Config.txt. Restart the Worker after changing them.

5. Install the Blender add-on

The current file is Blender Flagship Output Panel v2_2.py and declares Blender 5.0 or later.

1. In Blender, open Edit > Preferences > Add-ons.
2. Use the add-on menu and choose Install from Disk (wording can vary).
3. Select Blender Flagship Output Panel v2_2.py and enable Flagship Output Panel if needed.
4. Open Output Properties > Flagship.
5. Set Database Path to the shared root: \\FILESERVER\Flagship.

Enter the root, not a child folder. The add-on automatically appends Work Orders, Temporary Projects, and Temporary Output; these must match the Manager paths.

6. Install the After Effects panel

1. In After Effects, choose File > Scripts > Install ScriptUI Panel.
2. Select AE Flagship UI Panel 1.3.3.jsx, then restart After Effects.
3. Open Window > AE Flagship UI Panel 1.3.3. The panel title is Flagship Renderer.
4. If prompted, enable Allow Scripts to Write Files and Access Network in Scripting & Expressions preferences.
5. Choose Path Settings in the panel and enter:
   • Work Orders: \\FILESERVER\Flagship\Work Orders
   • Temporary Projects: \\FILESERVER\Flagship\Temporary Projects
6. Select Save.

Settings are saved for the current user as Flagship_Renderer_AEPanel_Settings.txt in Documents.

The optional Flagship_AE_Render_Settings.json and [Flagship Render Output Modules].aep support project settings and previews. A normal Flagship Render can proceed without valid preview settings after confirmation; Flagship Render w/ Previews requires them.

7. Submit the first job

Start with a small, low-resolution test of a few frames, with every asset on shared storage.

Blender

1. Open and save the project; configure the render engine, frame range, and output format.
2. For production output, configure one active compositor File Output node using a shared destination. Except for multilayer EXR, only one linked output item is supported. Without an active File Output node, output goes beneath Temporary Output.
3. Confirm all assets and final destinations are accessible from Computer 2.
4. Under Output Properties > Flagship, verify the Database Path.
5. Set Priority (larger values render first), Frames Per Task, Timeout, and Overwrite Existing Frames.
6. Select Submit Render to Flagship and wait for confirmation.

After Effects

1. Open and save the project. Confirm footage, fonts, plug-ins, and outputs are available to Computer 2.
2. Add compositions to the Render Queue and configure output modules/files, or use Add to AE Render Queue with valid Flagship project settings.
3. Review Auto-Reopen Project, Overwrite, Render Full Comp Length, Priority, and Workers. Use ∞ or 0 to let the Manager calculate the split.
4. Choose Flagship Render, or Flagship Render w/ Previews when previews are configured.
5. Confirm any output-module warnings. The panel copies the project and publishes its work order.

8. Monitor and control the job

1. Browse to http://MANAGER-IP:8008.
2. Confirm the job appears and Computer 2 changes from available to rendering.
3. Expand the job to inspect tasks, current Worker, progress, metadata, and logs.
4. Use Pause / Resume, Cancel, Restart, or Archive as needed. The Worker Black List prevents selected Workers from taking the job.
5. After completion, verify files at the final destination.

9. First-job acceptance checklist

• The web interface opens from Computer 3 at http://MANAGER-IP:8008.
• Computer 2 appears in the Worker list and reports the intended renderer.
• All three computers resolve the configured UNC paths.
• Each account can create and delete a test file in its required shared folders.
• A test job appears shortly after submission.
• The Worker accepts a task and launches the correct renderer.
• Progress and logs update in the web interface.
• Rendered files appear in the intended output location and open correctly.
• No assets, fonts, plug-ins, or color-management resources are missing.

10. Troubleshooting

11. Adding more Workers

Repeat the Worker setup on every additional render computer. Give each Worker a unique name, use the same Manager IP and TCP port 32761, and verify that its renderer versions and access to project dependencies match the jobs it will accept.