I’m unsure if this is a Modo issue or something to do with Deadline. But there are two new Render Outputs from Modo 701 SP3. Diffuse Amount and Diffuse Energy Conservation. Neither will render any images while rendering on the farm via Deadline. If I render locally and then save, the image files get written.
I’m on:
Deadline Version: 6.1.0.54178 R
Windows 7
Modo 701 SP3
I have my scene set up to write out to manually made directories and I am rendering PNG 8-bit.
When you submit the job to Deadline, do you override the output in the submitter, or do you leave the override blank? If you are currently overriding the output, try leaving it blank and submit again to see if that makes a difference.
Cheers,
Ryan
No the overrides are empty.
Interesting. That would mean that Deadline isn’t touching any of the output paths, so it’s strange that they wouldn’t be saved. Can you post the render log? Maybe a sample scene file that we could use to test as well?
Sure! I’ll have to do it tomorrow since I’m working remotely today.
OK, so here is the task report log and my test scene. I’m assuming the task report and the render log are the same thing. If not please let me know where I can find the render log.
James
deadlineTest_02_v003_JB.rar (10.9 KB)
Job_2014-01-14_14-04-53_52d5b48691032623c410ef4f.txt (14.1 KB)
Thanks!
It look like my modo trial has expired, so we’re going to contact the Foundry to see if we can get some licenses for testing.
Cheers,
Ryan
Just an update that I now have modo set up on my machine, so time to start digging.
I tested the scene you posted, and I wasn’t able to reproduce the problem. I actually did two test jobs: one with no pass group specified, and one with Passes_Test specified. In both cases, I got all four output types. The only thing I changed in the scene file was the four output paths so that they pointed to an existing folder.
I checked the log you posted again, and noticed that the render executable path was “C:\Program Files\Luxology\modo\701\modo_cl.exe” and not “C:\Program Files\Luxology\modo\701_sp3\modo_cl.exe”. Is it possible that you still have an older version of modo 701 on the farm and that’s why you’re not getting those new output file types?
Cheers,
Ryan
Holy crap! That is very likely the reason and most likely the reason for a few other anomalies we’ve been experiencing.
This is what our plugin configuration looks like for modo 7xx setup:
C:\Program Files\Luxology\modo\701\modo_cl.exe
C:\Program Files (x86)\Luxology\modo\701\modo_cl.exe
C:\Program Files\Luxology\modo\701_sp3\modo_cl.exe
/Applications/modo.app/Contents/MacOS/modo_cl
Is this setup wrong?
When multiple executable paths are listed in the plugin configuration, Deadline will use the first path that exists on the machine the job is rendering on. So in this case, if both modo 701 and modo 701 SP3 are installed on the same machine, modo 701 will always be used.
To have Deadline use the modo 701 SP3 path, you’ll need to list it first (or just remove the modo 701 paths):
C:\Program Files\Luxology\modo\701_sp3\modo_cl.exe
C:\Program Files\Luxology\modo\701\modo_cl.exe
C:\Program Files (x86)\Luxology\modo\701\modo_cl.exe
/Applications/modo.app/Contents/MacOS/modo_cl
Cheers,
Ryan
That’s good to know.
Thanks!