Cinema 4D

Job Submission

You can submit jobs from within Cinema 4D by installing the integrated submission script, or you can submit them from the Monitor. The instructions for installing the integrated submission script can be found further down this page.

To submit from within Cinema 4D, select Python -> Plugins -> Submit To Deadline. (For R15 and earlier, it should be just “Plugins -> Submit To Deadline.”)

integrated monitor

Submission Options

The general Deadline options are explained in the Job Submission documentation, and the Draft/Integration options are explained in the Draft and Integration documentation.

Cinema 4D Options

  • Cinema 4D File: The scene file to be rendered.
  • Take Name/List: The name of the take to render. This is optional, and if left blank, it will default to the current take (supported in C4D R17 and onwards).
  • Export Project Before Submission: If your project is local, or you are rendering in a cross-platform environment, you may find it useful to export your project to a network directory before the job is submitted.
  • Threads/Threads To Use: The number of threads to use for rendering.
  • Frame List: The list of frames to render.
  • Frames Per Task: This is the number of frames that will be rendered at a time for each job task.
  • Version: The version of Cinema 4D to render with.
  • Use Batch Plugin: If checked, the Cinema 4D batch plugin will be used to render Cinema 4D jobs, which keeps the scene file loaded in memory between tasks.
  • Build To Force: You can force 32 or 64 bit rendering with this option.
  • Submit Cinema 4D Scene: If this option is enabled, the scene file will be submitted with the job, and then copied locally to the slave machine during rendering.

Cinema 4D Output Options

  • Use Default Output From Scene: Enable this option to use the output path defined in the scene file.
  • Filename Prefix: If overriding the output, this is the file name prefix.
  • Output Folder: If overriding the output, this is the folder that the frames will be saved to.
  • Use Default Multipass Output From Scene: Enable this option to use the multipass output path defined in the scene file.
  • MP Filename Prefix: If overriding the multipass output, this is the file name prefix.
  • MP Output Folder: If overriding the multipass output, this is the folder that the frames will be saved to.
  • Enable Local Rendering: If enabled, the frames will be rendered locally, and then copied to their final network location.

Script Job Options

Script Jobs use the Cinema 4D Batch plugin and do not force a particular render.

  • Submit A Cinema4D Script Job (Python): Enable this option to submit a custom Python script job. This script will be applied to the scene file that is specified.
  • Python Script File: The Python script file to use *.py.

Cross-Platform Rendering Considerations

In order to perform cross-platform rendering with Cinema 4D, you must setup Mapped Paths so that Deadline can swap out the Scene and Output file paths where appropriate. You can access the Mapped Paths Setup in the Monitor while in super user mode by selecting Tools -> Configure Repository. You’ll find the Mapped Paths Setup in the list on the left.

When submitting the Cinema 4D job for rendering, you should enable the Export Project Before Submission option, and choose a network location when prompted for the export path. This will strip any absolute asset paths and make them relative to the scene file, and will also ensure the option to submit the Cinema 4D scene file with the job is disabled.

If you don’t enable the Export Project Before Submission option, you need to manually export the project to a network location. Then, you must submit the exported scene file from the Submit menu in the Monitor and you need to specify the output and/or multipass output paths in the submitter. Make sure the option to submit the Cinema 4D scene file with the job is disabled. If you leave it enabled, the scene file will be copied to and loaded from the Slave’s local machine, which will break the relative asset paths.

Plug-in Configuration

You can configure the Cinema 4D plug-in settings from the Monitor. While in super user mode, select Tools -> Configure Plugins and select the Cinema 4D plug-in from the list on the left.

Cinema4D

../_images/cp_c4d.png

Render Executables

  • C4D Executable: The path to the C4D executable file used for rendering. Enter alternative paths on separate lines. Different executable paths can be configured for each version installed on your render nodes. Note, in Cinema 4D R16 and onwards, using Commandline.exe instead of CINEMA 4D.exe on Windows is recommended as it will stop a command prompt window from appearing during rendering.

Cinema4DBatch

../_images/cp_c4d_batch.png

Render Executables

  • C4D Executable: The path to the C4D executable file used for rendering. Enter alternative paths on separate lines. Different executable paths can be configured for each version installed on your render nodes. Note, in Cinema 4D R16 and onwards, using Commandline.exe instead of CINEMA 4D.exe on Windows is recommended as it will stop a command prompt window from appearing during rendering.

Logging

  • Log Script Contents to Render Log: If enabled, the full script that Deadline is passing to Cinema 4D will be written to the render log. This is mainly useful for debugging purposes.

Integrated Submission Script Setup

The following procedures describe how to install the integrated Cinema 4D submission script. This script allows for submitting Cinema 4D render jobs to Deadline directly from within the Cinema 4D editing GUI.

You can either run the Submitter installer or manually install the submission script.

Submitter Installer

Manual Installation

  • Copy the file:

    [Repository]/submission/Cinema4D/Client/DeadlineC4DClient.pyp to [Cinema 4D Install Directory]/plugins
    
  • Restart Cinema 4D, and the Submit To Deadline menu should be available from the Python -> Plugins menu. (For R15 and earlier, it should be just “Plugins -> Submit To Deadline.”)

Custom Sanity Check

A CustomSanityChecks.py file can be created alongside the main SubmitC4DToDeadline.py submission script (in [Repository]\submission\Cinema4D\Main), and will be evaluated if it exists. This script will let you set any of the initial properties in the submission script prior to displaying the submission window. You can also use it to run your own checks and display errors or warnings to the user. Here is a very simple example of what this script could look like:

import c4d
from c4d import gui

def RunSanityCheck( dialog ):

    dialog.SetString( dialog.DepartmentBoxID, "The Best Department!" )
    dialog.SetLong( dialog.PriorityBoxID, 33 )
    dialog.SetLong( dialog.ConcurrentTasksBoxID, 2 )

    gui.MessageDialog( "This is a custom sanity check!" )

    return True

The available dialog IDs can be found in the SubmitC4DToDeadline.py script mentioned above. They are defined near the top of the SubmitC4DToDeadlineDialog class. These can be used to set the initial values in the submission dialog.

Finally, if the RunSanityCheck method returns False, the submission will be cancelled.

FAQ

Which versions of Cinema 4D are supported?

Cinema 4D 12 and later are supported.

When I use Adobe Illustrator files as textures, the render fails with “Asset missing”

While Cinema 4D is able to use AI files in workstation mode, there is often problems when rendering in command line mode. Convert the AI files to another known type such as TIFF or JPEG before using them.

Sometimes when I open the submission dialog in Cinema 4D, the pool list or group list are empty.

Simply close the submission dialog and reopen it to repopulate the lists.

Does rendering with Cinema 4D with Deadline use up a full Cinema 4D license?

There are separate Cinema 4D command line licenses that are required to render with Deadline. Please contact Maxon for more information regarding licensing requirements.

Can Deadline render with Cinema 4D’s Net Render Client software?

No. It isn’t possible for 3rd party software such as Deadline to control Cinema 4D’s Net Render Client, which is why it uses the command line renderer.

I have copied over SubmitToDeadline.pyp file but the integrated submission script does not show up under the python menu.

This is likely caused by some failure in the script. Check your repository path to ensure the client is able to read and write to that folder. Using the python console within C4D may provide more specific hints.

My frames never seem to finish rendering. When I check the slave machine, it doesn’t appear to be doing anything.

This can occur if Cinema 4D hasn’t been licensed yet. Try starting Cinema 4D normally on the machine and see if you are prompted for a license. If you are, configure everything and then try rendering on that machine again.

Why does a command prompt (black DOS window) appear whilst rendering on Windows?

In Cinema 4D R16 and onwards, using Commandline.exe instead of CINEMA 4D.exe on Windows is recommended as it will stop a command prompt window from appearing during rendering.

Error Messages And Meanings

This is a collection of known Cinema 4D error messages and their meanings, as well as possible solutions. We want to keep this list as up to date as possible, so if you run into an error message that isn’t listed here, please email Deadline Support and let us know.

Currently, no error messages have been reported for this plug-in.