...
Broadly speaking, AOVs in RIS fall into three these main categories: built-in, integrator (global), custom, and light path expressions.
| Info |
|---|
For users interested in what is typically referred to as "render passes" for compositing a beauty image, look at the page on light path expressions (LPE). |
...
Built-in AOVs
The built-in AOVs display mostly geometric information pertaining to points on the visible surfaces seen by the camera. These values are automatically generated by the renderer and are available as AOVs regardless of the active integrator. Here is the current list of available builtin-ins:
| Info |
|---|
Notice that data passes (normals, z-depth, world position, etc) are not filtered by default. Filtering together values may result in errors and nonsense values so it is avoided. Additive passes meant for beauty compositing are typically filtered the same to provide clean images and improved anti-aliasing.
id, rawId, z all use zmin filtering by default. cpuTime and sampleCount use the sum filter by default. |
| Info |
|---|
Post motion blur (2D Motion Blur vectors) can be important to a pipeline. While we recommend using motion blur in the render, sometimes a lack of resources forces this to post processing. dPdtime AOVs are useful for post blurring in 2D but this does not contain camera motion blur (the camera movement) dPcameradtime AOVs are available for camera motion blur. This means motion blur can be separated and controlled with finer detail, especially if the camera movement introduced more blur than you'd like artistically, you can adjust it separately. A static camera will produce no results for this AOV and thus no example below. If you render from a locked camera then it can be omitted without penalty. |
| Carousel Image Slider | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
On top of regular LPE-based AOVs, this integrator ouptuts outputs a number of standard AOVs typically used by compositors.
...