Guide created by legendary 3D artist, Brilly, walking you through using the Render Network Cinema4D Wizard for Redshift
The Render Network Cinema 4D Wizardcan 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
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 4Dmanual.
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.
