Hi all, I’d like to know if there is offical integraton for C4D 2025 in the very near future?
I was able to edit my param file to get C4D jobs to submit and find the executable but… nothing is actually rendering. The process never starts.
Any ideas on this?
is it stuck on the CLR license request?
yes, 100% that was the issue… forgot about that after setting up a machine brand new!
What did you do to force deadline to use c4d 2025?
Follow this thread to patch the .param files, you should be able to use the same .py file in the plugins folder to submit
Yes… what Anthony linked you to. Here’s what I inserted into my param file. Make sure you backup your existing param to another directory first…
[C4D_2025_RenderExecutable]
Label=C4D 2025 Executable
Category=Render Executables
CategoryOrder=0
Index=20
Type=multilinemultifilename
Default=C:\Program Files\Maxon Cinema 4D 2025\Commandline.exe
Description=The path to the Cinema 4D executable file used for rendering. Enter alternative paths on separate lines.
I updated the param files in cinema4d and cinema4d batch, the jobs are submitted but they stuck in Starting Up. All c4d version are the same.
is it the second answer in this thread? it’s stuck on the license option?
If you open an command prompt and run
“c:\Program Files\Maxon Cinema 4D 2025\Commandline.exe”
does it prompt you for the license type, and do you have a CLR license attached to this account?
It worked, I didn’t expect a license problem, as we tried it with a workstation where c4d 2025 is already in use. I didn’t know that the commandline need an extra setting for its licensing.
Anyone got the new C4D + Redshift update to work with deadline? I’m talking C4D 2025.1.0 and Redshift 2025.2.0
I can submit, but every frame fails.
Same here. There seems to be an issue with the new release.
I’m in contact with Maxon for further investigations, but I don’t have an idea yet.
Can confirm that something funky appears to be happening with 2025.1; spent a good amount of time yesterday talking with Justin Younger (who is also experiencing the issue with 2025.1 but not 2025.0.2) and Toms Seglins (for whom everything is working fine).
On my end I get three different results from different machines:
My local machine renders the job fine.
Log File:
Letellier_Deadline2025_LogFile_01.zip (8.6 KB)
My boss’s machine fails, getting a collection of error codes that we initially thought was related to some changes in 2024.x; I patched the submitter with the code that Toms originally developed (and that was confirmed by the Thinkbox/AWS devs at that time), but that doesn’t appear to be helping.
Log File:
Letellier_Deadline2025_LogFile_02.zip (4.7 KB)
2024-12-05 16:56:11: 1: STDOUT: Drawport API initialized
2024-12-05 16:56:11: 1: STDOUT: Framework : DirectX
2024-12-05 16:56:11: 1: STDOUT: Vendor : NVIDIA
2024-12-05 16:56:11: 1: STDOUT: Device : NVIDIA GeForce RTX 2080 Ti
2024-12-05 16:56:11: 1: STDOUT: Framework version: 12
2024-12-05 16:56:11: 1: STDOUT: Driver version : 560.94
2024-12-05 16:56:15: 1: STDOUT: 24-12-05 16:56:14 [DBG] Pipe: Win32NamedPipeService is running
2024-12-05 16:56:19: 1: STDOUT: ================ AEC4D-PRO_v1.14 ================
2024-12-05 16:56:19: 1: STDOUT: AEC4D-PRO_v1.14: Registered to: <User> - License for 1 user (c) 2024 Lasse Lauch
2024-12-05 16:56:19: 1: STDOUT: =================================================
2024-12-05 16:56:19: 1: STDOUT: C:\Program Files\Maxon Cinema 4D 2025_v1\plugins\DeadlineC4DClient.pyp:1: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives
2024-12-05 16:56:19: 1: STDOUT: from distutils.spawn import find_executable
2024-12-05 16:56:21: 1: STDOUT: Appending "C:/Users/<user>/AppData/Local/Thinkbox/Deadline10/cache/4pxJODsm9eqB7ScD1IX6dxW0/submission/Cinema4D/Main" to system path to import SubmitC4DToDeadline module
2024-12-05 16:56:21: 1: STDOUT: C:\Users/<user>/AppData/Local/Thinkbox/Deadline10/cache/4pxJODsm9eqB7ScD1IX6dxW0/submission/Cinema4D/Main\SubmitC4DToDeadline.py:1321: DeprecationWarning: invalid escape sequence '\s'
2024-12-05 16:56:21: 1: STDOUT: render_element = re.sub("[\s-]", "_", render_element)
2024-12-05 16:56:21: 1: STDOUT: C:\Users/<user>/AppData/Local/Thinkbox/Deadline10/cache/4pxJODsm9eqB7ScD1IX6dxW0/submission/Cinema4D/Main\SubmitC4DToDeadline.py:1331: DeprecationWarning: invalid escape sequence '\O'
2024-12-05 16:56:21: 1: STDOUT: """
2024-12-05 16:56:21: 1: STDOUT: C:\Users/<user>/AppData/Local/Thinkbox/Deadline10/cache/4pxJODsm9eqB7ScD1IX6dxW0/submission/Cinema4D/Main\SubmitC4DToDeadline.py:1371: DeprecationWarning: invalid escape sequence '\.'
2024-12-05 16:56:21: 1: STDOUT: rgb_path = re.sub("\.?%s" % re.escape(token), "", rgb_path)
2024-12-05 16:56:22: 1: INFO: Process exit code: -1073740791
2024-12-05 16:56:22: 1: Done executing plugin command of type 'Render Task'
Log File:
Letellier_Deadline2025_LogFile_03.zip (4.3 KB)
2024-12-05 16:56:34: 0: STDOUT: Drawport API initialized
2024-12-05 16:56:34: 0: STDOUT: Framework : DirectX
2024-12-05 16:56:34: 0: STDOUT: Vendor : NVIDIA
2024-12-05 16:56:34: 0: STDOUT: Device : NVIDIA GeForce RTX 4090
2024-12-05 16:56:34: 0: STDOUT: Framework version: 12
2024-12-05 16:56:34: 0: STDOUT: Driver version : 537.13
2024-12-05 16:56:36: 0: STDOUT: 24-12-05 16:56:36 [DBG] Pipe: Win32NamedPipeService is running
2024-12-05 16:56:39: 0: INFO: Process exit code: -1073740791
2024-12-05 16:56:39: 0: Done executing plugin command of type 'Render Task'
–
I’ll add that my machine would only render things once I disabled ‘Use Batch Plugin’ from the submitter dialog.
I’m going to try using CommandLine only (without Deadline) on the headless nodes & see what kind of result I can get.
I’ll also try submitting from the Deadline monitor instead of using the C4D .pyp plugin submitter.
Now I just need to remember how to use Commandline by itself 
"/mnt/sw/c4d/2025.002/bin/Commandline" -nogui -noopengl -redshift-license-maxon-disable -arnoldAbortOnLicenseFail true -render "/mnt/jobs/tests/c4d/2025.0.c4d" -frame 0 0 -take "Main" -oresolution 1280 720 -oimage "/mnt/jobs/tests/c4d/out/Documents" -redshift-log-console Debug
This is how I test outside of Deadline on linux, I’ll try this next week, be good to have this working and the new RedshiftUSD render command as an export option.
I was able to create Out of Memory failures in essentially blank scenes on two out of four machines with just Command Line, and have reported it to Maxon.
Hi! Today Ive been able to render, but without using the batch parameter. wich so far is causing a bug. maybe it can help you
any updates on support for C4D/Redshift 2025 variants? I’ve prepared all the various steps/edited files etc. but can’t afford to actually implement it into a production environment if all these errors are going to crop up.
Why is there such a delay every time on compatibility with these new versions? Is it Maxon?
I’m having to field questions about alternative render mgmt programs now if my artists can’t use this new Redshift etc. 
Agree, this is getting ridiculous, I am stuck with another morning of working/not working with Deadline, its been like this for a year, I have Commandline licenses and redshift licenses and the Maxon app seems happy but with no ‘official’ c4d 2025 support, nearly half a year after public release whats the point in using deadline if its castings these issues
I am resorting to Team render as a solution today, and its working and more reliable than deadline :sigh:
Hi everyone,
after some frustration and trial and error, I finally got C4D 2025 and RS 2025 working smoothly with Deadline. The key was removing all older plugins (around pre-2022/2023) from the plugin folders on each machine.
Additionally, I make sure to leave the “Use Batch Plugin” option unchecked when submitting jobs. To prevent any licensing errors, I’ve stored the Maxon credentials in the config.txt file of each node as follows:
g_licenseUsername=“xxx”
g_licensePassword=xxx
g_hideaccountmode=false
From what I’ve observed, the issue appears to stem from a conflict between Python 2.x and Python 3.x. However, Maxon support has not yet confirmed or denied this theory.
I hope this helps anyone facing similar challenges!
confirmed I seem to be working again, if I switch off the ‘Use batch plugin’ on the submitter