I have a stereo job that is giving us some problems with a chunk of frames. I’m not able to determine what the errors mean and we haven’t yet found anything in the scene that could be causing the issue. I was hoping someone might see somethign we missed in the error logs.
Job_2014-01-31_14-04-14_52ec1dde27f3da607cd6126b.txt (11.8 KB)
Update:
We feel that this is an internal issue, but I am still curious if any information can be gleamed from the job report.
Hello,
I was wondering if you have had a chance to try running this outside of Deadline? That would help us narrow down the issue. Thanks.
Oh sorry. We ended up figuring out that we had a corrupted EmReader cache. At the time I was just taking shots in the dark trying to figure it out. Modo is terrible at error reporting and so I have learned to cast a very wide net.
Hi James,
Is this “EmReader” error something that Deadline could help recognise in the future? ie: Is there anything unique, like a unique set of issues which when combined in various error messages, then Deadline could be enhanced to identify and flag this issue?
Let us know if anything can be done here (although it sounds like the first step is to get Modo to improve their STDout)
Cheers,
Mike
I’m uncertain if there is. In this instance these were geo cache files rewritten out of Softimage and read into modo through the Mootzoid emReader plugin. We would have to find someway to make modo aware that there is a file corruption going on. I’m assuming that it had issues loading the geo cache file for those particular frames and thus times out while on the farm. I’ll have to talk to the artist more today and see if I can get a clearer picture of this.
James