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.
And to make sure - yes i have the 2025 executable set up in the .param files in repository
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.
And to make sure - yes i have the 2025 executable set up in the .param files in repository
+1 for this and the new redshift USD render as an export option
I was scratching my head why deadline stopped working over the weekend. But seems like C4D got updated to 2025.1.0 and from what i am reading, that is the issue for all the failed tasks?
I am actually in contact with Maxon Support and they also dont know what is going on But yea its definitly some sort of issue with the Commandline Renderer. They also changed something about Redshift Installation process, so maybe there is somewhere a issue.
But for now, there is no way to get it to work as far as I and apperantly Maxon know about.
Much appreciated that you are reaching out to them.
I need deadline more then the new features at the moment so i am rolling back for the time beeing
Keep us posted on the progress!
After some useless conversations with Maxon support, I dove into the code and discovered that it uses the deprecated function GetData(). After replacing it with GetDataInstance(), my C4D 2025.1 finally works. Check the Cinema4DBatch.py file for the following line: deadlineC4DThreadScript.append( " results = documents.RenderDocument(self.deadlineDoc, self.renderData.GetData(), bmp, c4d.RENDERFLAGS_EXTERNAL | c4d.RENDERFLAGS_SHOWERRORS, self.Get())" )
This worked for me! The renders are now completing after failing endlessly.
@lurii Awesome mate. Will this have a effect on C4D 2024 renderings or is this working regardless of the version?
Good find, but did not solve it for me sadly.
Ofc might be me doing it wrong if it works for these other guys
It should work, as I remember, GetDataInstance was introduced few versions ago. But GetData was deprecated in the latest.
I’m not really a specialist in Deadline, and I just struggle with it from time to time. But if you could post the task report containing the error, it might help clarify the problem.
Check that you’ve updated your Nvidia Drivers as well; the latest version of RS requires them, and your renders will fail otherwise. I had both issues - Deadline + Nvidia Driver, and had to fix both before I could get back to rendering.
Can you maybe provide your Cinema4DBatch.py file? I did your changes but it still keeps crashing
Sorry, but my version of Cinema4DBatch.py has some injections of code that I use for my own purposes and it has dependences which could not work on your machine. Have you checked the license? Try to run Commandline.exe and check it on the first launch. And of course post your error log.
Yea, I also got some Logging tools from Maxon which use the Commandline Renderer, that works just fine. So I guess its not a fix for everyone.
Also updated the GPU drivers.
In my case crash happened just after executing c4d_Batch_Script.py that, in its turn, was generated by Cinema4DBatch.py. that how I tracked the source of problem. Check on what step it crashes.
2024-12-07 03:09:01: 0: INFO:
2024-12-07 03:09:01: 0: STDOUT: Running Script: C:\ProgramData\Thinkbox\Deadline10\workers\COMP_REN_03\jobsData\67531b042214de942c6822fe\thread0_temp01hGs0\c4d_Batch_Script.py
2024-12-07 03:09:08: 0: WARNING: Monitored managed process Cinema4DProcess is no longer running
2024-12-07 03:09:08: 0: Done executing plugin command of type ‘Render Task’
2024-12-10 17:41:32: 0: STDOUT: Redshift Debug: PreviewScheduler: Start
2024-12-10 17:41:32: 0: STDOUT: Redshift Debug: PreviewScheduler: Preview Mode:Suspend Context:0
2024-12-10 17:41:32: 0: WARNING: Monitored managed process Cinema4DProcess is no longer running
2024-12-10 17:41:32: 0: Done executing plugin command of type 'Start Job'
These are my last logs in Deadline. Just crashes
I see. It happens even before executing c4d_Batch_Script.py, so it is something different Maybe “Preview Mode:Suspend Context:0” means something. In my successful log it’s “Preview Mode:Background Context:1” But I have no expertise to say what does it mean.
Hi lurii!
Glad to hear you solved this issue, which from what I’ve read, doesn’t seem like it was an issue on the Maxon side. Am I correct?
Also, do you recall what your ticket number was with Maxon? I’d be curious to see how this “conversation” went. Perhaps there is something we can do on our end to improve. Thanks!