> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/prepare-your-scene/aovs.md).

# AOVs and render passes

Prepare AOVs in your renderer and check which passes are available when creating a job.

AOVs, also called render passes, show separate parts of a render, such as reflections or diffuse lighting, for use in compositing.

## Prepare passes before uploading

Set up the passes you need in the source scene, then save or export it. Only passes included in the uploaded scene are offered in the web app.

{% tabs %}
{% tab title="Octane" %}
In Octane Standalone, select the render target and add the required AOVs through **Render AOVs** in the **Node Inspector**. Use a **Render AOV Group** for several passes and make sure the group is enabled. Preview each pass using its button in the render viewport before saving the ORBX. See OTOY's [Render AOVs guide](https://docs.otoy.com/standaloneSE/RenderAOVs.html).

In Cinema 4D, use **Render Settings → Octane Renderer → Render AOV Manager**. If you build an AOV node setup, connect it to the **Octane Renderer** node. See OTOY's [AOVs and composites guide](https://docs.otoy.com/cinema4d/AOVsandComposites.html).
{% endtab %}

{% tab title="Redshift" %}
Add passes in the **AOV Manager** and check that each required AOV is enabled. A pass needs **Multi-Pass** or **Direct Output** enabled to be written, even if you can already see it in Redshift Render View. See Maxon's [AOV guide](https://help.maxon.net/r3d/cinema/en-us/Content/html/Intro%2Bto%2BAOVs.html).

Follow [Cinema 4D with Redshift](/docs/prepare-your-scene/cinema-4d-redshift.md) when packaging the scene.
{% endtab %}

{% tab title="Blender Cycles" %}
In **View Layer Properties → Passes**, enable the passes you need. For a custom shader AOV, add it in **Shader AOV**, then use an **AOV Output** node in the material with the same name. See the [Blender passes reference](https://docs.blender.org/manual/en/latest/render/layers/passes.html).

Follow [Blender with Cycles](/docs/prepare-your-scene/blender-cycles.md) when packaging the scene and its compositor outputs.
{% endtab %}
{% endtabs %}

## Check the job's pass list

When creating a job, check **Render Passes** in the [render settings](/docs/web-app/render-settings.md). If you are configuring several render targets together, the shared list contains only passes present in every selected target.

If a required pass is missing, check the selected target and [scene version](/docs/web-app/scenes-and-versions.md), then check the pass setup in the source scene. Save and upload the corrected scene before creating the job.

Choose how passes are written, including multilayer EXR where available, in [Output configurations](/docs/web-app/outputs.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://know.rendernetwork.com/docs/prepare-your-scene/aovs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.