3Delight

3delight.com ↗

Render scene layers locally or in the cloud, with separate preview and file modes

SI Score
80/100
Pricing
Freemium AI reading, not confirmed
Free plan
Yes AI reading, not confirmed
Sign-up required
Not confirmed

Ask SI about 3Delight

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the 3Delight homepage

What it does

3Delight supplies a renderer, host integrations and command-line tools. Its Houdini integration groups camera, quality, image-layer and preview settings in render nodes, with local CPU, network and cloud processing options. Free local rendering is available alongside paid licences and cloud credits.

In the Houdini integration, create a render node through Render > Create Render Node > 3Delight, or use the 3Delight shelf. Choose the camera and environment under Scene Elements, set image quality and add the image layers needed for the result. Overrides let an interactive preview use different settings from the final render.

The default Beauty layer contains the main RGBA image. Additional layers can carry depth, unlit surface colour, shading components or contributions from selected lights. Each layer can be displayed, saved to a file or both, which keeps the compositing outputs separate from the viewer.

Interactive preview (Live IPR) continuously follows scene changes, but it does not write image files and omits motion blur. Use a normal frame or sequence render for saved output, or enable Image File output for batch rendering. The Processing panel selects the local CPU, 3Delight Cloud or a network Collective.

Pre-generated NSI scene files can be rendered with the renderdl command without loading Houdini for that stage. The free NSI renderer does not need a licence file. Paid licences need the appropriate server configuration; an unlicensed paid installation produces a watermark. Cloud credits use a separate account, so free local rendering and cloud processing have different access arrangements.

Strengths

  • Image layers can be routed independently to the viewer and saved files.
  • Interactive overrides and final render settings can serve different stages.
  • NSI files provide a command-line render handoff outside the host application.

Watch out for

  • Live IPR omits motion blur and produces no image files.
  • Paid installations watermark renders when the required licence is unavailable.
  • Cloud rendering requires separate account credits.

Best for

  • Houdini rendering with separate compositing layers
  • Pipelines switching between interactive preview and file-based rendering

Sources