13:46:57: 0: STDOUT: Redshift Debug: Status: Scanning Scene 13:46:57: 0: STDOUT: Rendering Phase: Finalize It’s not actually even an error according to Deadline as it just stays waiting and never kills the task or retries unless you manually do it. On tasks with multiple frames, the same worker might complete a few frames and then hang mid-task this way.
At this point, it’s already received the cli license successfully but doesn’t acquire a redshift license, so some licensing is working. But, occasionally when a tasks starts it will hang immediately after Render Begins. They’re available and it works fine about 75% of the time. This seems tied to when the task begins and redshift tries to acquire a license. I’ve also opened a case with Maxon about it. And I saw 10.2 had some release notes about Maxon App support, so I was curious if anyone else had the same issue I’m seeing. This doesn’t specifically seem to be a Deadline error, but it only happens when sending these jobs through Deadline…if I manually try and run the Commandline.exe commands to do the rendering, it succeeds each time in getting a license. Currently on the latest Deadline release, latest redshift, and R25.121 but I’ve seen the same with a test of C4D 2023 as well. We’ve had some issues with consistent tasks getting completed using Deadline with R25 and the past few versions of redshift and the Maxon app with their floating teams licensing.
0 kommentar(er)
