Hi all,
We’ve been having a seemingly-random issue over here with C4D R12 Deadline renders.
Essentially, random tasks from nearly every job “stall”, in the sense that they never give any errors, but never finish (or even appear to begin) rendering. These stalls occur on every slave eventually (they aren’t happening on just one or two machines).
Here is an example of what I mean:
As soon as the individual tasks are re-queued, they render fine on the second go-around. Since this is occurring across the board on our files, I’m wondering if it’s a known issue with Deadline?
Thanks!
Dylan
In this example, were Rendernode20 and Rendernode04 still “rendering” the task? In other words, it wasn’t the case where the tasks got lost and the slaves had moved on?
I’ve heard of cases where C4D hangs during rendering like this, and unfortunately because C4D on Windows doesn’t flush it’s output until it’s finished, all Deadline sees is a happy rendering process. Note that Deadline just launches the C4D command line process and waits for it to finish, so if it doesn’t output anything indicating there is a problem, or it doesn’t exit, Deadline can only assume it’s rendering.
I’ve also heard of this issue with other render managers, which leads me to believe it’s a more general C4D command line rendering issue.
Cheers,
I’ve logged in remotely to these tasks before (am looking at some right now that are hanging) and they do appear to be rendering. Is this something we should address to MAXON?
Thanks!
-Dylan
It definitely won’t hurt to bring it up with MAXON. Maybe it’s something they’re already aware of. You can refer them to this thread if you want. Hopefully they have an idea what the issue is, or they can tell us what we’re doing wrong. 
Cheers,