> 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/getting-started/cinema-4d-on-render-network-guide/preparing-your-cinema-4d-file-for-the-render-network/using-custom-ocio-configurations.md).

# Using Custom OCIO Configurations

If you want to use custom OCIO configurations in your renderings, please carefully read the current limitations.

## For Octane ORBX

* **Octane 2023 and prior**: Not supported
* **Octane 2024 and up**: During ORBX export the currently used view transform will be baked into a LUT and saved into the ORBX file.

## For Octane C4D

* **Cinema 4D 2023**: Not supported.
* **Cinema4D 2024/2025**: Octane will use by default the ocio.config file from the Cinema 4D resource folder found under resource\modules\c4d\_base\ocio. Other configurations are not supported.

## For Redshift C4D

* **Cinema 4D 2023**: Not supported.
* **Cinema 4D 2024 / 2025**: Redshift will use by default the ocio.config file from the Cinema 4D resource folder found under resource\modules\c4d\_base\ocio. Other configurations are not supported.


---

# 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/getting-started/cinema-4d-on-render-network-guide/preparing-your-cinema-4d-file-for-the-render-network/using-custom-ocio-configurations.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.