Yeah same deal with mayabatch plugin. It isn’t a simple scene, a lot of dense references, but lighting wise it’s pretty simple, just a sun/sky system. I’ll try with a simpler scene now.
Ah also the odd thing is that it all works fine if I submit from deadline monitor rather than the shelf button in maya.(before the fixes provided)
Thanks!
Edit:
We may have found the issue with animation in the actual maya globals being checked off rather than the one in the vRay globals. This might be the difference in the two submission scripts?
Edit2: That seems to have fixed it, though one or two machines get the -1073741819 error. Looking at the FAQ the fix is below, but there’s no maya directory in the plugins folder. Neither of the .dlinit files(cmd or batch) have that “RenderStartupDir=…” line either, is this still the fix for deadline 4?
The error code -1073741819 is equivalent to 0xC0000005, which represents a Memory Access Violation error. So Maya is either running out of memory, or is touching memory that it shoudn’t. If you find that your frames are still being rendered, you can modify the Maya plugin in Deadline to ignore this error.
Just add the following line of code to the Maya.dlinit file in //your/repository/plugins/maya. Note that the code below must be all on one line, and can be added after the “RenderStartupDir=…” line.
CheckReturnCode=if( ReturnCode() != 0 ) { if( ReturnCode() != -1073741819 ) { FailRender( "Renderer returned non-zero error code, " …ReturnCode() ); } }