Tutorials · Distributed rendering

Submit once.Render everywhere.

Use the submitter in your DCC, choose how Eclipse accesses your files, and distribute the work across your Render Nodes.

4/4

Choose your application

Each video shows a supported renderer and its packaging workflow. Modes vary by DCC and renderer; Octane Studio submits an ORBX package.

Shown with a supported renderer. Check the modes available in your submitter.

Watch out

If the submitter shows no Shared Folder or an old path after farm setup, close your DCC, reinstall its Eclipse integration from Manage Integrations, then reopen the DCC.

Choose how nodes access the files

Shown in the videos

Collect & Package

Copies the scene and supported dependencies to the Shared Folder and updates paths. Use it for assets on local drives; review any missing-file warnings.

Alternative

Shared Path

Keeps asset paths instead of collecting them. Use it when all dependencies are accessible to every node; Eclipse may still copy the scene or create an export.

Check this first

Save the scene first. With Shared Path, every node needs valid asset and output paths. Standalone Renderer needs a licensed CLI; USDZ Package is Solaris-only where offered.

Choose how the job is split

Choose how frames are assigned. These four strategies cover weighted shares, equal shares, a single task, or individual frames.

By node weight

Gives larger frame shares to nodes with higher weights. Choose it when machines have different rendering speeds.

Equal per node

Divides frames into equal shares, regardless of node weight. Choose it for similarly fast machines or an even split.

Single task

Keeps the whole submitted range in one task for one node. Choose it when the job should not be divided across the farm.

One frame per task

Creates a separate task for each submitted frame. Choose it when frame times vary and nodes should pick up individual frames.

Max frames per task segment caps timeline segments when enabled with By node weight. Set the cap in Distributed settings; each segment is then divided by node weight, not treated as one task.

Optional notifications

Enable Discord notifications, select Connect Discord Link, and paste the copied link into your browser. Authorize a server/channel, return to Connected, then select Test.