Integrations

Houdini

Install the Houdini integration and submit with the Eclipse Submitter HDAs (Local and Distributed).

Houdini uses Eclipse Submitter HDAs. You connect ROP nodes, choose a submission mode, and submit. Frame ranges come from the connected ROPs. Supported engines: Redshift, Octane, and Arnold.

Install

  1. Open Manage integrations → Houdini.
  2. Select Houdini versions and click Install / Reinstall Houdini integration.
  3. Close Houdini if it is open, then relaunch so packages and OTLs load.
  4. Confirm you can place Eclipse Submitter nodes from the Tab menu.

HDAs

HDANode typeContextUse
Eclipse Submitter (Local)Eclipse.Submitter.Local/outLocal Queue: Standard or Standalone Renderer
Eclipse Submitter (Distributed)Eclipse.Submitter.Distributed/out (and /stage for some workflows)Farm: Collect & Package, Shared Path, or Standalone Renderer

For Solaris /stage workflows use the dedicated Solaris HDAs (see Solaris).

Local Queue submit

  1. Save the .hip scene.
  2. In /out, create Eclipse Submitter (Local).
  3. Connect one or more supported ROPs (Redshift, Octane, Arnold).
  4. Choose Submission Mode: Standard or Standalone Renderer.
  5. Fill Project name, Artist, Label, Priority, and Houdini version if prompted.
  6. Click Submit. The job appears in the Eclipse Local queue.

Local modes

  • Standard: Eclipse runs hbatch against the HIP/ROP on this machine.
  • Standalone Renderer: Eclipse exports Redshift .rs, Arnold .ass, or Octane intermediates, then renders with the engine command line. Exports typically land under $JOB/exports/<ROP>/ or a local eclipse_standalone folder.

Distributed Queue submit

  1. Confirm ECLIPSE_SHARED_ROOT (or the farm shared folder) is set and reachable from Houdini.
  2. Create Eclipse Submitter (Distributed) and connect ROPs.
  3. Choose Submission Mode: Collect & Package, Shared Path, or Standalone Renderer.
  4. Pick or create a Project name on the share. Refresh the project list after creating folders.
  5. Optionally choose render nodes or leave the farm open to all capable workers.
  6. Run Shared Path preflight when offered (flags local-only texture risks).
  7. Submit. Watch the job under Distributed → Jobs in Eclipse.

Farm modes

  • Collect & Package: packages the scene and dependencies under projects/houdini/collect_package/<Project>/, then spools to the coordinator.
  • Shared Path: copies the HIP under projects/houdini/shared_path/<Project>/… and expects every dependency path to resolve identically on every node. Optional Set $JOB / $HIP and per-OS path pairs for mixed Windows/macOS farms.
  • Standalone Renderer: collect/export Redshift, Arnold, or Octane intermediates onto the share; farm nodes render with engine CLIs (engineRef *_standalone).

ROP-driven frames

Frame Start / End / Increment are read from the connected ROP. Adjust the ROP, not a separate export step. Drag additional ROPs into the Submitter when you need multiple outputs from one submit.

Related