Nodes Render output nodes
Render nodes are “drivers” for rendering out the scene into various formats, often using external programs. For example, the mantra node uses mantra to render the scene, while the RenderMan node uses RenderMan.
Output driver nodes translate the scene into the format expected by a renderer and run the renderer on it. Houdini includes render drivers for the built-in mantra renderer, as well as RenderMan, other RIB renderers, and mental ray.
Output driver nodes live at the Render Outputs (ROP) level. They let you set up renders for different rendering methods, programs, and/or settings, and switch between them based on your needs at any given moment.
For example, you can set up different output nodes for different render qualities (such as test render and final render) and independent render passes. Or, you can render various scenes with different renderers.
Each driver renders the view of the scene through a camera . For a driver to work correctly, the camera associated with the driver must still exist.
Use Render > Create Render Node to create a new output driver.
Use Render > Edit Render Node to select and edit an existing render driver.
How to temporarily disable outputs
ROPs have bypass flags and lock flags, which you can use to disable ROPs without disconnecting them from the network.
Bypassing a ROP will stop it from rendering. Input ROPs will still render.
Locking a ROP will stop it and all its input ROPs from rendering. This is a good way to 'lock off' a branch of renders. If some input ROP has another ROP that is dependent on it, and that ROP isn’t locked, it will still render. Locking a ROP will only block the one dependency path through the locked ROP.
Bypassing or locking a subnetwork will prevent any of the ROPs inside from rendering.
You can still force a bypassed or locked render node to render using the “Render All Bypassed Nodes” and “Render All Locked Nodes” options in the render control window.
Usages in other examples
|Example name||Example for|