AWS Thinkbox Discussion Forums

C4D 2025 workaround/support

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!

1 Like

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

1 Like

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.

1 Like
Privacy | Site terms | Cookie preferences