Deadline 5.0 - Maya2012 - VRay 2.0

Hi All

We have just started Rendering with VRay2.0 for Maya2012
When we submit to farm through Deadline5.0 the render does not make use of all the processors properly:

When we render Via [b]Deadline 5.0 > Maya12 > VRay 2.00.04[/b] = Processors on Render Machine running at [b]6%[/b] mainly using only one proc [b]23 mins/frame[/b]
Using Remote desktop and opening up Maya interactively on Render Node, loading scene and hitting render  16 x cores on Render Machine running at [b]100% [/b]- [b]1.5mins/frame[/b]

We have Deadline set to “0” to use all procs

Any suggestions welcome

Cheers

When you submit the job to Deadline, are you submitting from within Maya using the integrated submission script (thinkboxsoftware.com/deadlin … ript_Setup), or you submitting from the Deadline Monitor? If you’re submitting from the Monitor, do you have VRay selected as the renderer in the Renderer drop down?

Cheers,

  • Ryan

From the Deadline Monitor. Yes we have VRay set as Renderer, Version 2012, Build To Force 64bit (we are running on Windows 7)
We also tried setting Procs to 16 (instead of zero) but still whole farm only using one core per node - maybe this setting is not being passed to VRay via your VRay plugin?

Thanks for confirming. The next thing to do is see if the “Use MayaBatch Plugin” is enabled under the Advanced Options tab in the Monitor submitter. If it is, disable it and submit again. This will render in “command line” mode, and if this fixes the cpu usage problem, that means that our batch plugin isn’t setting the threads properly. If that’s the case, it’s likely that the vray threads setting name changed in 2.0.

If you are submitting jobs with “Use MayaBatch Plugin” disabled, and you still don’t get full cpu usage, then we need to look at the command line that Deadline is passing to Maya. Can you post a render log? You can find them by right-clicking on a job that exhibited this problem in the Monitor and selecting Job Reports -> View Log Reports.

Thanks!

  • Ryan

Managed to remove most errors by editing Maya Scene File. Renders fine with out Hair. Errors trying to find Hair Cache (even though it exists) but keeps going… I guess because Strict Error disabled. I have attached the log file.

Cheers

John

Deadline_Output.txt (8.29 KB)

Hi John,

Thanks for the log. It turns out that Deadline isn’t passing any thread information to vray via the command line, which explains the problem. Attached is an updated MayaCmd plugin file that should fix this issue (we’ll try to fix the MayaBatch version soon). To install, go to \your\repository\plugins\MayaCmd and backup MayaCmd.py (just in case). Then unzip the attached file to the same folder. Submit a new job (with MayaBatch option disabled) and with the Thread setting set to 0, and let us know if things improve.

Cheers,

Thanks Ryan

I will download and give this a test.

Cheers

John

Hi Ryan

Thanks for the updated MayaCmd.py this fixed our problem.

We still have Vray renders (with hair) that never actually write out the frame but I’m assuming this is a Vray rather than Deadline problem. Here is chunk from the log incase you happen to know the problem:
.
.
.
.
0: STDOUT: [2011/Jun/14|16:38:21] V-Ray: (Estimated time remaining: 0h 0m 6.5s): 96 % completed
0: STDOUT: [2011/Jun/14|16:38:25] V-Ray: (Estimated time remaining: 0h 0m 3.2s): 98 % completed
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray debug: Threads completed
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: Number of raycasts: 234944431
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: Camera rays: 221097863
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: Shadow rays: 8509872
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: GI rays: 0
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: Reflection rays: 1308050
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: Refraction rays: 29020
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: Unshaded rays: 4770
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray debug: Clearing global light manager.
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray debug: Clearing direct light manager.
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray debug: Clearing ray server.
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray debug: Clearing geometry.
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray error: Exception [module=1] : Clearing geometry
0: WARNING: Deadline is ignoring error “Error: Exception [module=1] : Clearing geometry” because plugin setting Strict Error Checking is disabled.
0: STDOUT: Error: Exception [module=1] : Clearing geometry
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: Number of intersectable primitives: 1611888
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: SD triangles: 12136
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: MB triangles: 0
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: Static primitives: 1599752
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: Moving primitives: 0
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: Infinite primitives: 0
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray debug: Clearing camera image sampler.
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray debug: Clearing camera sampler.
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray debug: Clearing DMC sampler.
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray debug: Clearing path sampler.
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray debug: Clearing color mapper.
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray: Total frame time 0h 4m 53.5s (293.5 s)
0: STDOUT: [2011/Jun/14|16:40:03] V-Ray debug: Calling endSequence().
0: STDOUT: [2011/Jun/14|16:40:04] V-Ray: Total sequence time 0h 8m 36.8s (516.8 s)
0: STDOUT: [2011/Jun/14|16:40:04] V-Ray debug: Exiting render().
0: STDOUT: [2011/Jun/14|16:40:04] V-Ray: Render interrupted
0: STDOUT: [2011/Jun/14|16:40:04] V-Ray: ========================
0: STDOUT: [2011/Jun/14|16:40:04] V-Ray: Clearing exporter memory…
0: STDOUT: [2011/Jun/14|16:40:04] V-Ray: Total time clearing exporter memory 0h 0m 0.0s (0.0 s)
.
.
.
.

Regards

John

Glad to hear that fixed the problem! We’ll be sure to include thread support for Vray for Maya in Deadline 5.1.

When these errors occur when rendering with hair, does Deadline detect the error and generate an error report? Or does it miss the error and mark the task as complete? If it’s the latter, does enabling Strict Error Checking make a difference? If not, then we may need to add an additional handler to deal with this particular error.

I wonder if it’s safe to assume that “V-Ray: Render interrupted” only gets printed out when the render fails. If so, I would prefer to fail the render on that line instead of the “V-Ray error: Exception [module=1] : Clearing geometry” line because we get some additional output after that line that may (or may not) be helpful.

Cheers,

  • Ryan

No Error is detected by Deadline so no error report generated. We (at Animagine Studios in London) are new to Vray so have forwarded these errors to the Chaos support team. I have set VRay to it’s most verbose error mode but get no more info back. Will let you know when I hear back from Chaos.

I am attaching the full log

Cheers

John

Animagine_Render_Log.txt (27.6 KB)

Hi John,

Thanks for confirming, and thanks for the log! Attached is an updated MayaCmd.py file that will look for the “Error: Exception” message when strict error checking is enabled, and fail the job if it is detected. Give it a try and let us know if it helps here.

Just follow the same installation instructions as before.

Cheers,