Houdini Render Manager That Works Like You Do
Automate ROP submissions. Manage your local queue. Stop babysitting renders.
Eclipse integrates directly with Houdini. Submit ROPs from the HDA, let the queue run in the background, and get notified when renders complete or fail.
Built for Houdini Artists, Not Pipeline Engineers
Most Houdini render managers assume you want to build infrastructure. They expect network configuration, worker registration, and constant maintenance.
Eclipse works differently. Install it. Open the HDA. Submit your ROPs. That's it.
No complex setup. No manual network wiring. No pipeline engineering.
How Eclipse Automates Your Houdini Workflow
Direct ROP Submission
Connect supported Redshift, Arnold, or Octane ROPs to the Eclipse Submitter HDA. Frame ranges come from the ROPs. Standard uses Houdini; Standalone Renderer exports for a licensed engine CLI.
Local Queue Management
Your renders queue locally. Eclipse monitors progress and reports failures, with logs and relaunch controls when needed. You stay in your flow while renders run in the background.
Automatic Failure Handling
Spot failed frames, inspect the logs, and relaunch the work you need. Optional Discord notifications report the job statuses you choose, including completion and failure.
Redshift & Solaris Support
Use supported Redshift, Arnold, or Octane ROPs in Houdini. For Karma and other supported Solaris delegates, use the dedicated Solaris Submitter HDAs.
Why Eclipse Feels Different
Other Houdini render managers are built for studios managing render farms. They assume you have IT support, network infrastructure, and time to configure complex systems.
Eclipse is built for artists who render every day. It assumes you want your renders to run, not that you want to manage infrastructure.
Start the queue. Let it run. Focus on creating.