Integrations
Submitting jobs
How artists submit from supported DCCs: panels, HDAs, and submission modes.
Every DCC integration follows the same idea: install Eclipse into the DCC, open the Local or Distributed submit UI, choose a submission mode, fill frames and metadata, then Submit. Eclipse writes a job to the local spool or to the farm coordinator.
Install the integration first
- In Eclipse, open Manage integrations.
- Select the DCC you use (Houdini, Maya, Blender, Cinema 4D, 3ds Max, …) and Install / Reinstall for the versions you need.
- Close and reopen the DCC so packages, plug-ins, or add-ons load.
- Confirm Local capabilities sees the DCC and required renderers.
Local Queue vs Distributed Queue
Each DCC exposes two submit surfaces (separate HDAs in Houdini/Solaris, separate dock panels or N-panels elsewhere):
- Local Queue: jobs run on this workstation via the Eclipse local worker.
- Distributed Queue: jobs go to the coordinator and are claimed by render nodes. Requires a shared root and Distributed mode configured in Eclipse.
Submission modes
Submission Mode controls how the scene and assets reach the worker. Names are consistent across DCCs where the mode exists. Not every mode is available for every engine (see Compatibility).
| Mode | Where | What it does |
|---|---|---|
| Standard | Local | Render with the DCC batch tool on this machine (hbatch, Maya batch, Blender, C4D commandline, Max batch). No farm collect. |
| Standalone Renderer | Local or Distributed | Export engine intermediates (.rs, .ass, .vrscene, ORBX, …) and render with the engine CLI. Farm nodes may not need a full DCC install for that engine. |
| Shared Path | Distributed | Copy the scene onto the share and render in place. Use only when every texture and cache path already resolves the same way on every machine. |
| Collect & Package | Distributed | Collect dependencies into a portable project folder on the share, repath assets, then spool. Safest default when machines differ. |
| USDZ Package | Distributed (Solaris) | Pack the Solaris look as USDZ for travel. Available for Redshift and Karma; not for Arnold (Auto-TX cannot read textures inside .usdz). |
Common fields on every submit
- Frame range: Start, End, Step (often driven from the ROP, render settings, or scene).
- Job metadata: Project name, Submission label, Artist, Department, Priority.
- Output: resolved from the DCC/engine settings; farm modes may remap under the shared project.
- Optional farm controls: project picker, render-node filter, single-slice / no slicing.
After you submit
- Switch Eclipse to Local or Distributed to match where you submitted.
- Select the job in the queue to watch Logs and Preview.
- On the farm, open the job for slices/tasks and relaunch failed ranges if needed.