The Cinema 4D Wizard can be used to prepare and upload native C4D files rendered with either Octane or Redshift to the Render Network. The C4D Wizard packs a project into a zip-file which can then be dragged-and-dropped into the Render Network WebApp.
The Wizard can be downloaded from this link: https://renderfoundation.com/c4d-wizard
Once installed, the Wizard can be accessed from the Extensions menu (figure 1).
Figure 1: Accessing the Wizard from the Extensions menu
The following link demonstrates the overall process of using the Wizard inside of C4D, including the steps for proper installation.
https://know.rendernetwork.com/getting-started/cinema-4d-on-render-network-guide/c4d-wizard-plug-in
It uses a scene designed with Octane but the process is identical when using Redshift. The only difference is Redshift instead of Octane will be listed under the Render Engine entry in the Wizard window (figure 2).
Figure 2: Redshift is listed as the Render Engine in the Wizard window
Additional information regarding the Render Network can be found in the general Cinema 4D manual.
Considerations for Caching Simulations: https://know.rendernetwork.com/getting-started/cinema-4d-on-render-network-guide/preparing-your-cinema-4d-file-for-the-render-network/caching-simulations-for-the-render-network-advanced
Using Nested Scenes:
The following link provides an overview for preparing and uploading native C4D files to the Render Network manually, without the use of the Wizard:
Currently known limitations:
Available versions:
For Cinema 4D 2023 we support Redshift version 3.6.00
For Cinema 4D 2024 we support Redshift version 3.6.03
Available file types for rendering:
Redshift on the Render Network currently only supports PNG and EXR outputs.
Cryptomatte Rendering:
Cryptomatte rendering currently only works by choosing the single-layer EXR file type for your Multipass images. It is not supported for Multi-Layer EXR Multipasses.
If you choose PNGs as your Multipass file type, the Cryptomatte passes will be ignored.
Asset collection for .rs Proxy files:
Cinema 4D currently can not collect assets (for example texture files) belonging to an embedded .rs Proxy object. If your .rs Proxy files use external textures make sure they are stored next to the .rs Proxy object and the relative path linking to those texture files is correct.
- Example: Your .rs. Proxy object uses external textures, which are stored in the “tex” folder next to the .rs Proxy object. In this case keep the .rs Proxy object next to your .c4d file and store the textures inside the “tex” folder of your Cinema 4D project.
| C4D Feature Name | Supported: Y or N? | Additional Info |
| Additional File Formats (non PNG & EXR) | N | In development |
| Ambient Occlusion | Y | |
| Alembics | Y | |
| Audio Files | Y | |
| Capsules | N | In development (excluding Python reliant capsules) |
| C4D Render Effects (Denoise, Sharpen, Tone Mapping, etc.) | Y | |
| C4D Noises | Y | |
| C4D Procedural Shaders (effects and surfaces) | Y | |
| Cloners + Effectors | Y | |
| Deformers | Y | |
| Fields | Y | |
| Generators | Y | |
| Hair Object | Y | |
| Hair Shader | Y | |
| IES Lights | Y | |
| Magic Bullet Looks | N | External Plugin not currently supported |
| Metaball | Y | |
| Mograph Color Shader | Y | |
| Mograph Beat Shader | Y* | Standard/Physical supported, not Octane |
| Mograph Multi Shader | Y* | Standard/Physical supported, not Octane |
| Mograph Camera Shader | Y* | Standard/Physical supported, not Octane |
| Mograph Cache (Internal) | Y | |
| Motion Blur: Geometry | Y | |
| Motion Blur: Volumetrics | Y | |
| Motion Blur: Sub-frame Motion Blur | Y* | Standard/Physical supported, not Octane |
| Motion Blur: CameraMoblur (on/off) | Y | |
| Motion Blur: Lights | Y | |
| Motion Blur: Instances | Y | |
| Motion Blur: Pyro-generated volumetrics | Y* | Standard/Physical supported, not Octane |
| Multipasses | Y | |
| Octane Object Tag Hair Shading | Y | |
| Octane Light IDs | Y* | Octane supported |
| ORBX Files | Y | |
| Parenting/Constraints | Y | |
| Python/Python Tag | N | External Plugin not currently supported |
| Pyro (motion blur via velocity channel) | Y* | Standard/Physical supported, not Octane |
| Render Region | Y | |
| Simple XRefs | Y* | Standard/Physical supported, not Octane |
| Sketch & Toon | Y | |
| Stage Object | Y | |
| Substance Assets | Y | |
| Takes | Y | |
| Text/Mograph Text/Text Spline | N | Needs to be converted to paths or polygon objects |
| Thinking Particles | N | Workaround in progress |
| Vertexmaps | Y | |
| Viewport Rendering | N | Error under investigation |
| Volume Loader Object | Y* | Needs to be inside a "Volume Loader" folder with a relative path |
| Volume Builder Cache | N | In development |
| Volume Mesher | Y | |
| Watermark Effect | Y |
Machine Info not supported |
Additionally, during Alpha and closed Beta testing, certain features were discovered to need preparation in order to function currently. Those can be found in the table below alongside instructions for those features.
| Feature Name | Prep Instructions |
| Assets from the C4D asset browser | Needs to be saved into the project folder |
| C4D Particle Emitter | Needs to be cached |
| Dynamics: Cloner | Needs to be cached |
| Dynamics: Cloth | Needs to be cached |
| Dynamics: Rope | Needs to be cached |
| Dynamics: Soft Body | Needs to be cached |
| Dynamics: Rigid Body | Needs to be cached |
| Dynamics: Hair | Needs to be cached |
| IR/LM Global Illumination | Needs to be cached |
| Motion Blur: Hair | Needs to be cached |
| ORBXLoader | Relative path in PAI needed |
| Octane VDB Volume Object | Relative path in PAI needed |
| Physical/Standard Caustics effect | "Save Solution" needs to be turned off |
| XRefs | Relative path in PAI needed |