Maya batch one frame error problem

Deadline
1

Dear Deadline Forumers,

I have a logfile for a problem I’ve been having with just one frame from a Maya render, which is weird because all that is in my scenefile is geo, textures, moving lights, and animation.

This is the log:

=======================================================
Error

Error: Monitored managed process “MayaBatch” has exited or been terminated.
at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)

=======================================================
Type

RenderPluginException

=======================================================
Stack Trace

at Deadline.Plugins.Plugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
at Deadline.Slaves.SlaveRenderThread.a(TaskLogWriter A_0)

=======================================================
Log

2016-04-13 17:33:00: BEGIN - CHUNKER\5DN
2016-04-13 17:33:00: 0: Start Job timeout is disabled.
2016-04-13 17:33:00: 0: Task timeout is disabled.
2016-04-13 17:33:00: 0: Loaded job: mechspider TEST 02 (570e273bce9e330098ab6876)
2016-04-13 17:33:00: 0: INFO: Executing plugin script C:\Users\5DN\AppData\Local\Thinkbox\Deadline7\slave\Chunker\plugins\570e273bce9e330098ab6876\MayaBatch.py
2016-04-13 17:33:00: 0: INFO: About: Maya Batch Plugin for Deadline
2016-04-13 17:33:00: 0: INFO: The job’s environment will be merged with the current environment before rendering
2016-04-13 17:33:00: 0: INFO: Rendering with Maya version 2016.0
2016-04-13 17:33:00: 0: INFO: Setting MAYA_DISABLE_CIP (ADSK Customer Involvement Program) environment variable to 1 for this session
2016-04-13 17:33:00: 0: INFO: Setting MAYA_DISABLE_CER (ADSK Customer Error Reporting) environment variable to 1 for this session
2016-04-13 17:33:00: 0: INFO: Not enforcing a build of Maya
2016-04-13 17:33:00: 0: INFO: Setting PYTHONHOME to C:\Program Files\Autodesk\Maya2016\Python for this session
2016-04-13 17:33:00: 0: INFO: Starting monitored managed process MayaBatch
2016-04-13 17:33:00: 0: INFO: Stdout Redirection Enabled: True
2016-04-13 17:33:00: 0: INFO: Stdout Handling Enabled: True
2016-04-13 17:33:00: 0: INFO: Popup Handling Enabled: True
2016-04-13 17:33:00: 0: INFO: QT Popup Handling Enabled: False
2016-04-13 17:33:00: 0: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: False
2016-04-13 17:33:00: 0: INFO: Using Process Tree: True
2016-04-13 17:33:00: 0: INFO: Hiding DOS Window: True
2016-04-13 17:33:00: 0: INFO: Creating New Console: False
2016-04-13 17:33:00: 0: INFO: Running as user: 5DN
2016-04-13 17:33:00: 0: INFO: Not enforcing a build of Maya
2016-04-13 17:33:00: 0: INFO: Executable: “C:\Program Files\Autodesk\Maya2016\bin\MayaBatch.exe”
2016-04-13 17:33:00: 0: INFO: Argument: -prompt -proj “E:/Rorschach Spider”
2016-04-13 17:33:00: 0: INFO: Startup Directory: “C:\Program Files\Autodesk\Maya2016\bin”
2016-04-13 17:33:00: 0: INFO: Process Priority: BelowNormal
2016-04-13 17:33:00: 0: INFO: Process Affinity: default
2016-04-13 17:33:00: 0: INFO: Process is now running
2016-04-13 17:33:00: 0: Plugin rendering frame(s): 43
2016-04-13 17:33:00: 0: INFO: Waiting until maya is ready to go
2016-04-13 17:33:03: 0: STDOUT: Initialized VP2.0 renderer {
2016-04-13 17:33:03: 0: STDOUT: Version : 6.3.16.0. Feature Level 4.
2016-04-13 17:33:03: 0: STDOUT: Adapter : GeForce GTX 960/PCIe/SSE2
2016-04-13 17:33:03: 0: STDOUT: Vendor ID: 4318. Device ID : 5121
2016-04-13 17:33:03: 0: STDOUT: Driver : .
2016-04-13 17:33:03: 0: STDOUT: API : OpenGL V.4.5.
2016-04-13 17:33:03: 0: STDOUT: Max texture size : 16384 * 16384.
2016-04-13 17:33:03: 0: STDOUT: Max tex coords : 8
2016-04-13 17:33:03: 0: STDOUT: Shader versions supported (Vertex: 4, Geometry: 4, Pixel 4).
2016-04-13 17:33:03: 0: STDOUT: Shader compiler profile : (Best card profile)
2016-04-13 17:33:03: 0: STDOUT: Active stereo support available : 0
2016-04-13 17:33:03: 0: STDOUT: GPU Memory Limit : 4096 MB.
2016-04-13 17:33:03: 0: STDOUT: CPU Memory Limit: 15503.5 MB.
2016-04-13 17:33:04: 0: STDOUT: }
2016-04-13 17:33:04: 0: STDOUT: OpenCL evaluator is attempting to initialize OpenCL.
2016-04-13 17:33:04: 0: STDOUT: OpenCL evaluator failed to initialize clew.
2016-04-13 17:33:05: 0: STDOUT: mental ray for Maya 2016
2016-04-13 17:33:05: 0: STDOUT: mental ray: version 3.13.1.2, Jan 22 2015, revision 236291
2016-04-13 17:33:05: 0: STDOUT: mental ray: started on “Chunker”, Wed Apr 13 17:33:05 2016
2016-04-13 17:33:13: 0: STDOUT: Result: untitled
2016-04-13 17:33:13: 0: STDOUT: mel: READY FOR INPUT
2016-04-13 17:33:13: 0: INFO: Rendering with file
2016-04-13 17:33:13: 0: INFO: Rendering to network drive
2016-04-13 17:33:13: 0: INFO: Creating melscript to execute
2016-04-13 17:33:13: 0: INFO: Executing script: C:\Users\5DN\AppData\Local\Temp\tmpAA8D.tmp
2016-04-13 17:33:14: 0: INFO: Waiting for script to finish
2016-04-13 17:33:14: 0: STDOUT: mel: Loading scene: C:/Users/5DN/AppData/Local/Thinkbox/Deadline7/slave/Chunker/jobsData/570e273bce9e330098ab6876/BEAST VID TEST 003.mb
2016-04-13 17:33:16: 0: STDOUT: File read in 1.8 seconds.
2016-04-13 17:33:20: 0: STDOUT: API 0.0 132 MB warn 302004: while defining object “head_shellShape”: ccmesh tri-quad mesh, barys requested, not using native 3-4 subdivision
2016-04-13 17:33:20: 0: STDOUT: API 0.0 136 MB warn 302004: while defining object “mech_c1|mech_c_a|mech_c_aShape”: ccmesh tri-quad mesh, barys requested, not using native 3-4 subdivision
2016-04-13 17:33:21: 0: STDOUT: API 0.0 168 MB warn 302004: while defining object “body_topShape”: ccmesh tri-quad mesh, barys requested, not using native 3-4 subdivision
2016-04-13 17:33:29: 0: STDOUT: SHDR 0.8 773 MB warn : object “body_btmShape”, ptex information not available, must be turned on
2016-04-13 17:34:49: 0: STDOUT: SHDR 0.7 1331 MB fatal 141109: runtime exception 0xc0000005: access violation
2016-04-13 17:34:49: 0: STDOUT: SHDR 0.7 1331 MB fatal 141109SHDR 0.7 1331 MB fatal 141109: runtime exception 0xc0000005: access violation
2016-04-13 17:34:49: 0: STDOUT: SHDR 0.7 1331 MB fatal 141109: runtime exception 0xc0000005: access violation
2016-04-13 17:34:49: 0: STDOUT: : runtime exception 0xc0000005: access violation
2016-04-13 17:34:49: 0: WARNING: Monitored managed process MayaBatch is no longer running

=======================================================
Details

Date: 04/13/2016 17:34:50
Frames: 43
Elapsed Time: 00:00:01:51
Job Submit Date: 04/13/2016 12:02:19
Job User: 5dn
Average RAM Usage: 9713221632 (57%)
Peak RAM Usage: 11029561344 (65%)
Average CPU Usage: 65%
Peak CPU Usage: 100%
Used CPU Clocks: 2808781
Total CPU Clocks: 4321200

=======================================================
Slave Information

Slave Name: Chunker
Version: v7.2.3.0 R (d21b3e911)
Operating System: Windows 10 Home
Running As Service: No
Machine User: 5DN
IP Address: 192.168.1.3
MAC Address: F0:79:59:65:B9:AA
CPU Architecture: x64
CPUs: 8
CPU Usage: 100%
Memory Usage: 10.3 GB / 15.9 GB (64%)
Free Disk Space: 1.365 TB (9.622 GB on C:, 770.497 GB on D:, 182.292 GB on E:, 435.091 GB on H:)
Video Card: NVIDIA GeForce GTX 960

Hope someone can help :slight_smile: cos I’m proper confused

Thanks,

Nick.

2

Could it be because I got it for free? (as only one node) Frame 43. Four Three? Four Free? Or is this just a coincidence?

3

That error is because something inside of Maya tried to access a part of the computer memory it wasn’t allowed to. I’m not sure why it tried to do that.

I think I’ve seen this before where there was a single frame where a reflection got caught in an infinite loop because of the camera’s angle. Does your scene have any reflections?

You should see the same problem if you render frame 43 on your local machine. If not, try opening Maya on ‘Chunker’ and see if it fails there.

4

Yeh there are reflections in the scene. It is all rendering on Chunker anyway, but the problem is that MAya refuses to render anyway which is why I used Deadline in the first place.

5

Deadline runs an application for you so you don’t have to. The sad state is that if Maya can’t do it, neither can Deadline.

Now, if I’m right about this wonderful light bouncing… Are there render settings you can apply to limit the number of reflections done? Also, are there any ways you could cheat to work around it? I’m guessing there’s a panning camera of some kind, so people are going to notice if a frame gets repeated.

6

But this is where I am confused, because I started to use Deadline this time because Maya was refusing to batch render. And Deadline rendered when the Maya GUI wouldn’t.