I have a Modo job that is failing but when I look at the logs it shows that it’s getting through the entire frame, but then quits before the file can be saved. There is no useful error message that indicates why the frame failed. Except for this small bit in the error log:
2016-03-22 03:08:33: 0: STDOUT: ! (messageDialogs) [Yes/No/No To All] - File Not Found | asset:Images/HDR Images/Grid Room White 01.exr not found; select alternate file?
Normally I assumed that this kind of thing would stopped the render completely but for some reason it was allowed to continue. But I’m not sure if this is the reason that the job actually failed in the end.
Job_2016-03-22_01-41-49_56f1054d710bad0fa0036570.txt (797 KB)
Hello,
So an asset missing is not considered a fatal error, so the job does continue. As for why it’s dying, the process just seems to quit without error or notice. Can you try to render this scene in the Modo UI on the machine using the same system account that runs the deadline slave so we can see if Modo on this slave can even have a chance of rendering successfully? Hopefully if it dies, we can at least get some error to proceed with.
We think this issue is a Modo issue. The job was failing on every machine it got onto. We also we able to successfully render it locally, so we feel it’s specifically a problem with Modo_cl. We will probably submit a bug with Luxology if we can narrow down what is causing the issue.
It’s a bit annoying it just up and dies. Nothing to go on for either side.