Using the C4D Wizard for Redshift

A Guide to Using the Cinema4D Wizard for Redshift

Guide created by legendary 3D artist, Brilly, walking you through using the Render Network Cinema4D Wizard for Redshift

The Render Network 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. This guide walks you through using the C4D Wizard for Redshift

The Wizard can be downloaded from this link: https://rendernetwork.com/integrations/c4d/

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.

C4D Wizard Plug-in | Render Knowledge Base

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

Caching Simulations for the Render Network (Advanced) | Render Knowledge Base

Using Nested Scenes

How to work with nested scenes (XRefs) in C4D for the Render Network (Advanced) | Render Knowledge Base

The following link provides an overview for preparing and uploading native C4D files to the Render Network manually, without the use of the Wizard

Cinema 4D on the Render Network with Brilly | Render Knowledge Base

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.

Redshift Feature Name	Supported (Y/N)	Additional info
Cryptomatte	Y	Only in Single-Layer EXR mode
.rs Proxy files	Y
RS Volume	Y
C4D Shaders	Y	If supported by Redshift
Hair Rendering	Y	Needs to be cached
Pyro	Y	Needs to be cached
Pyro Motion Blur	Y	Needs to be cached (including XYZ velocity)
OSL	Y
Deep Images	N	Still in development
Trace sets / C4D Light Linking	Y
Custom OCIO configs	N