> 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/cinema-4d-redshift.md). # Cinema 4D with Redshift Prepare Redshift assets, proxies, and render settings in a Cinema 4D project. ## Check Redshift assets Open the scene with **Redshift** selected in Cinema 4D's render settings. Use the **Redshift Asset Manager** to find missing textures, volume files, and other linked assets. Relink missing files before following the [Cinema 4D packaging procedure](/docs/prepare-your-scene/cinema-4d.md). In the asset manager, **Suggested Path** is the reference stored by the scene and **Real Path** is where the file was found. Check both when a scene renders locally but fails after moving it. See [Maxon's Redshift Asset Manager guide](https://help.maxon.net/r3d/cinema/en-us/Content/html/Redshift_Asset_Manager.html). ## Include proxy files and their textures For a **Redshift Proxy**, include the `.rs` file, its texture files, and every required frame of an animated proxy sequence. Keep the folder arrangement expected by the proxy's texture references. If the proxy was exported with unsuitable motion blur settings, correct those in the source scene and export it again. Some settings, including frame duration, are fixed in the exported proxy. Maxon's [proxy guide](https://help.maxon.net/c4d/2025/en-us/Content/_REDSHIFT_/html/Intro%2Bto%2BProxies.html) covers what the export retains. ## Prepare the render * Bake any simulation-driven hair, cloth, particles, or volumes using the [caching guide](/docs/prepare-your-scene/caching-simulations.md). * Set up the required [AOVs](/docs/prepare-your-scene/aovs.md) in Cinema 4D before saving. * Check [OCIO](/docs/prepare-your-scene/ocio.md) if you use a custom colour configuration. After uploading the Cinema 4D ZIP, the job form uses **Error Threshold** for Redshift quality. Review this with the other [render settings](/docs/web-app/render-settings.md), and choose the required [output configuration](/docs/web-app/outputs.md). The native upload is the Cinema 4D project containing these assets. A `.rs` proxy by itself is not an accepted upload file. --- # 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/cinema-4d-redshift.md?ask=&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.