is there any news on this?
with the batch plugin this doesn’t work at all and with the other plugin it doesn’t work great. there were some computers on our farm that didn’t want to render with it at all until I removed the -nogui option for the commandline (which is strange, that this does something).
And then there is the problem that the c4d commandline seems to have a bug (at least with redshift). if you just want to render the multipass image and add AOVs to it, it will not output the AOVs. it also won’t render in the format it is supposed to. if you set the “multipass image” format to exr and the “regular image” format to tiff, but disable the save toggle in the rendersettings, it will always render tiffs not exrs. I think this format and AOV issue is related. Just seems to take the wrong output.
Is C4D 2025 officially supported? I have still problems when achtivating the batch mode in the submitter?
Cinema4d - 2025.2.1
Redshift - 2025.3.0
I’ve got it working fine on a Windows machine running the above. The Batch plugin was working but giving some issues in regards to Deadline accurately reporting the task progress.
Our version of the Repo only has up to 2024 as standard, so I had to manually edit the param and submission .py to include 2025 with the correct path. Then run the CLR on each node locally first to get the licensing details set correctly. In terms of inbuilt support for C4D2025, I don’t know if there are any big changes that would be included beyond having the extra information for 2025 executable location. Before this setup, we had a repo that by default was only including up to R23, and could get it running 2023 with just the above changes.