Okay, apperantly a clean install fixed it for me. Renders with your fix.
1 Like
It is hard to say that issue was on the side of Maxon. But deprecated function was not on the list of changes of the latest release,
at least I didn’t find it. You really need to dig in. And it’s a bit frustrating that support was not aware of changes that could break compatibility. Ticket [#730618]
My Maxon support gave me some tools to troubleshoot the commandline renderer. Turned out that the commandline renderer works as expected when you directly use it without Deadline.
So for now, the fix provided by lurii should be the go to fix. Plus checking/upgrading drivers is recommended. My fix was also to clean install C4D 2025, also deleting the %appdata% folders.
For all the folks that are uncomfortable to edit the Script, here is the basic version that worked for me:
Cinema4DBatch.py (71.3 KB)
3 Likes
@Iurii Thank you SO much for the investigation you did and for the solution! I can also confirm that going into the Cinema4DBatch.py file, searching for “GetData()” and replacing specifically THAT with “GetDataInstance()” does work for me aswell! Hurray!! 
1 Like
Thanks!!!Soooo Helpful…
1 Like
Any updates here? Is this the ‘final fix’ thread or is this C4D 2025 workaround/support one newer? My take away from reading both is that its still broken…