Integrations

Solaris

Submit Solaris / USD renders with the Eclipse Submit Solaris HDAs (HIP → USD → husk).

Solaris jobs use dedicated Submit Solaris HDAs in the /stage context. Eclipse exports USD from the stage and renders with husk (engineRef houdini_hydra), or with engine-specific standalones where offered. Supported delegates: Redshift, Karma XPU, Karma CPU, Octane, and Arnold.

HDAs

HDANode typeContext
Eclipse Submit Solaris (Local)Eclipse.Submitter.Solaris.Local/stage
Eclipse Submit Solaris (Distributed)Eclipse.Submitter.Solaris.Distributed/stage

These HDAs install with the Houdini integration. There is no separate Integrations tab for Solaris.

Local workflow

  1. Build the look in Solaris with a Render Settings LOP (and products/vars as needed).
  2. Add Eclipse Submit Solaris (Local) on /stage.
  3. Confirm the Hydra delegate matches the engine you want (Karma CPU/XPU, Redshift, Octane, Arnold).
  4. Set frame range and output path on the submitter / stage settings.
  5. Click Submit to Eclipse. Eclipse exports USD and runs the selected path locally.

Arnold in Solaris

When the Hydra delegate is Arnold (HdArnoldRendererPlugin), Local and Distributed HDAs offer two engines:

EngineTokenRunner
Standard (husk)standardhusk -R HdArnoldRendererPlugin
Standalone (sick)arnold_sickHtoA sick + USD (not kick/.ass from a ROP)
  • Farm packing: Collect & Package and Shared Path for both engines.
  • USDZ Package is not available for Arnold (Auto-TX cannot read textures inside .usdz).
  • No kick/.ass Solaris path and no redshift_usd_cmdline (Redshift only).
  • Runner remains houdini_hydra with constraints.solaris_submission_mode = standard or arnold_sick.

Distributed workflow

  1. Use Eclipse Submit Solaris (Distributed).
  2. Default farm mode is Shared Path under projects/solaris/shared_path/<Project>/ (usd/, desk/, render/).
  3. Configure Set $JOB / Set $HIP and optional per-OS (Windows + macOS) path pairs so the same USD resolves on every node.
  4. Submit. Farm nodes run husk (or the chosen standalone path) against the exported USD on the share.

Standalone / special paths

  • Redshift USD / cmdline paths exist for Solaris standalone-style local or farm exports when configured.
  • Octane Solaris can export ORBX-style packages for standalone Octane where supported.
  • Arnold uses sick + USD for standalone (see Arnold in Solaris above), not kick/.ass.
  • USDZ Package is for Redshift/Karma lookdev travel; not Arnold.
  • Prefer USD and cache paths that every farm node can resolve before choosing Shared Path.