OctaneRender’s Render Passes allow users to isolate different aspects of the scene, respectively rendering each aspect across multiple images. This is particularly useful in fine-tuning projects, compositing, and creating remarkably detailed and photo-realistic images.

 

Render Passes are processed differently by different render engines. Since OctaneRender is a separate render engine it also uses its own set of Render Passes and these can be found under Blender’s View Layer Properties tab (Figure 1).

Figure 1: Render passes settings.


The Preview Pass Type selects the pass that will rendered on the live render view (Blender 3D View window Rendered Viewport Shading method) or in the final render view (F12). The default Combined pass is the main beauty pass.

Cryptomatte Passes

Figure 2: Cryptomatte passes settings.

 

The Cryptomatte Passes work with the Direct Light and Path Tracing kernels to render Cryptomattes for use in compositing. They are rendered one at a time, and they contain the masks for all object layers or materials in a scene. The masks also have correct anti-aliasing, and they take into account other features such as motion blur, transparency, and depth-of-field.

OctaneRender® generates Cryptomatte Passes according to the following IDs:

    • InstanceID - The Cryptomatte channel is based on instance IDs.
    • MatNodeName - The Cryptomatte channel is based on the names of the existing Material nodes in the scene.
    • MatNode - The Cryptomatte channel is based on distinct Material nodes.
    • MatPinName - The Cryptomatte channel is based on the names of the existing Material pins in the scene.
    • ObjNodeName - The Cryptomatte channel is based on the names of the existing Object nodes in the scene.
    • ObjNode - The Cryptomatte channel is based on distinct Object nodes.
    • ObjPinName - The Cryptomatte channel is based on the names of the existing Object pins in the scene.
    • Channels - Amount of cryptomatte channels to render.

 

AOV Compositor Nodes

Arbitrary Output Variables (AOVs) are essentially the same as render passes. They contain additional information output from OctaneRender® that can be used for compositing, checking shader output, or debugging an issue. AOVs can include data passes such as normals, object positions and so on. In Octane AOVs can also include shading information, unlike other systems.