# Cinema4D

# Setup

First of all:
Commandline rendering is not the same as the Cinema4D "NetRender" or "Team Render".
RR can only use commandline rendering.
This requires either a defaut UI license or a Commandline Render license.

Cinema4D has different license types:

1) Licenses via MAXON account.

Starting with version R21, there is a new license type.

It requires you to enter your credentials for your MAXON web account to get the licenses and lock it to your machine.

2) OLD: Node licenses

If you are NOT using a floating license server for Cinema4D:

You can use Cinema4D only to number of node licenses that you have.

This means you need one node license for each machine that should be used for rendering or UI or both. (You can render and work within the UI on the same machine).

3) OLD: Floating licenses

With Cinema4D R17, you need to buy commandline render licenses.

## License render farm nodes

Please see Maxon Licensing section of this help.

## Submission

First you have to run the rrWorkstationInstaller install the submission plugin.

In Cinema4D, you have to run the script as shown in the screenshot. |

## $take with or without parenttake

Background:
There have been some production scenes in which the artist used the same take name within different parent takes.
Example:
FG/ beauty
BG/ beauty
In this case one job would overwrite the frames of the other job.
Or you end up with a folder of mixed files.
Therefore RR adds the parent take name to "$take"

Change:

If you prefer that RR does not add the parent take name to $take, then

•Please edit the file RR\render_apps\_submitplugins\rrSubmit_Cinema 4d_23.0+__inhouse.ini

•Then re-install the Submission plugins.
Either via rrWorkstationInstaller
or via rrControl, menu Clients, Command Job, "Reinstall Artist Workstation".

# C4D Plugins

## Farm-wide plugin installation

You can define a folder for your Cinema4D plugins.

RR will cache the folder into the local drive to save network traffic and improve speed.

Please edit the file [RR]\render_apps\_setenv\all\cinema 4d__inhouse.rrEnv with a text editor or [RR]/bin/../baEnvEditor

Change the line

C4D_rrPluginFolder =

to any folder you like.

You should use the variable <rrExeVersionMajor> in the path, this will be replaced with the C4D version.

This way you have different paths for different C4D versions.

To verify the path, send a C4D job and check the render log in rrControl for the line

C4D_rrPluginFolder source path is set to

## Farm-wide Redshift installation

Farm-Wide installation:

•Install Redshift on your workstation.

•Edit the file [RR]\render_apps\_setenv\all\cinema 4d__inhouse.rrEnv
Change RR_REDSHIFT_NETWORK to 1.

•Submit a render and check the render log file in rrControl.
Search for the line "RedShift source path is set to".
Create this RedShift Source Path if RR has not already created it.
(Example RedShift source path: RR_ROOT\render_apps\renderer_exe\cinema 4d\win_x64\Redshift_2026.4.0 )

•Now you have to copy the Redshift application files into RRs "RedShift Source Path".
You have 2 options:
A) Copy your local installation.
By default, Redshift is installed into one of these folders.
Copy the contents of that folder in "RedShift Source Path".

Version | OS | Plugin location
Redshift 2026 and later | Windows | c:\ProgramData\Maxon Redshift xxxxx\
| Linux | /usr/Maxon Redshift xxxxx/
| MacOS | /Applications/Maxon Redshift xxxxx/
Redshift 2025 and earlier | Windows | c:\ProgramData\Redshift\
| Linux | /usr/redshift/
| MacOS | /Applications/redshift/

B) Windows only:
Download the "zero-install zip package" (download available in the Redshift Forum redshift.maxon.net ) and extract it.
Then copy the contents of the extracted Redshift folder in "RedShift Source Path".

•Hint: To minimize the folder size, you can remove all other software packages form the Plugins subfolder of Redshift

## Farm-wide Octane installation

Farm-Wide installation:

•Install Octane on your workstation.

•Edit the file [RR]\render_apps\_setenv\all\cinema 4d__inhouse.rrEnv
Change RR_OCTANE_NETWORK to 1.

•Submit a render and check the render log file in rrControl.
Search for the line "Octane source path is set to".
Create this folder.
(Example Octane source path: RR_ROOT\render_apps\renderer_exe\cinema 4d\win_x64\Octane_1.0 )

•Copy all files and subfolders from your local Octane installation into that folder

For Octane Licensing issues, please see Octane Standalone.

# Errors

### Language Selection

Cinema4D uses localized names for rendering.

E.g. if you render in Stereo, the files are rendered into "Channel Left" or "Kanal Left" or ...

If you experience differences between machines, then you need to login with the renderfarm user and change the language in the Cinema4D preferences.

You can could also copy the preference file from one machine to an other.

The file is located in:

c:\Users\%Username%\AppData\Roaming\MAXON\CINEMA 4D R14_4A9E4467\prefs\c4d_language.prf

### Agent does not respond

The Quicktime 64bit to 32bit agent is responsible for this message.

The bug was reported to MAXON.

If you do not use Quicktime, then you can rename the file "C:\Program Files\MAXON\CINEMA 4D R12\resource\libs\win32\qtguiagent.exe" to something else.

### Error rendering project

Cinema4D does not output any error message besides "Error rendering project" if you render via commandline.

(Perhaps if many users request it?)

So if you get this error, you have to open the scene manually on that machine and try to render an image.

It is usually a missing texture or a non-existing output folder.

### Stereo Render

There is a bug in Cinema4D (at least in C14):

If you check the setting to render into sub-folders, then Cinema crashes.

It even does not work with their own build-in render queue.

### redshift-core-hip-vc140.dll

Redshift prints this error:

Could not load the hip core library from .....\win_x64\Redshift_2025.5.0\bin\redshift-core-hip-vc140.dll

This does not mean that something is wrong.

This is the reply that MAXON gave about the file:
It means that RS can't load the renderer for the AMD GPUs because probably you don't have any, but this should not affect the rendering.
To ensure it, I have taken a closer look into the .dll file.
I can confirm that "hip" does not has anything to do with Houdini in this case.
It refers to the AMD library it uses: c:\Windows\system32\amdhip64.dll
"Heterogeneous-computing Interface for Portability (HIP) API"

Solution:

To get rid of the message, simply delete this dll.

Note that if the message states that the Dll is in RR_Localdata, then this is a cached version.

In this case you have to remove the file from the Redshift source folder in RR.
Otherwise it gets re-copied.