


Simple enough fix, just clean up unused nodes. As mentioned before, the scene did, in the beginning, contain old models referenced in with mental ray nodes causing issues and errors.So I’m back, after a week (or more) of going through the file I think I’ve finally gotten it nailed down to a few specific things that were tripping up Arnold and deadline. Job_14-28-38_5bd0657482ac9b2bf0b97143_nonbatch.zip (4.4 KB)Īppologies for not directly pasting them here, it exeeded the maximum word count. Heres the report for the non-MayaBatch job: We have an OCIO file setup with an environment variable on every machine/node where the variable points to the file laying on a server, don’t know if that helps. It all seems to stem back to color management warnings, four of the repeating for what I assume are multiple objects or multiple textures. I’ve tried both with and without “MayaBatch” and end up with different “final” error codes depending if I use batch or not but the same “non-issue” warnings.

It looks like it’s trying but it encounters a lot of (what at least to me) seems like none issues causing it to fail. I’m having an issue submitting a render from Maya using Arnold as the renderer.Įvery time I submit it is unable to render any frame.
