Hi - This is a problem I opened with support on the 8.0 release, which Dwight believed was fixed in 8.1. I just gave it a test run and I’m seeing the same thing in 8.1.5.5-rc1 as I was in 8.0.11.2. I followed up on the support ticket and was advised to post about it here with a reference to the original ticket – [#597985] “extra jobs submitted for arnold export render”.
The summary is that we’re running maya 2017 and using the new render setup stuff. I believe (though no one is positive) that the scene started life pre-2017 new render setup. When I submit an Arnold export render with the export done locally and dependent render jobs submitted, Deadline creates jobs for layers that don’t exist rather than the ones that do.
The jobs created are for, “defaultRenderLayer”, “defaultRenderLayer1”, and “defaultRenderLayer2” but the Render Settings “Render layer” drop-down menu and Render Setup panel show the render layers are “masterLayer” and “rs_renderSetupLayer1”. Also, in the Render Setup panel only the masterLayer is enabled for batch rendering, so I’d only expect to see a job created for that layer.
When I create a new simple test scene this doesn’t happen but we have quite a few jobs where we load up a previous scene built for the job, make some updates, and re-render for a new delivery and it would be some trouble to rebuild them all clean in 2017 (assuming that would even solve it for the real production case).
The scene was provided in the investigation of the original support ticket if you need it and if there’s any other information I can gather here that might help please let me know. We’d love to be able to get renders running directly from arnold .ass rather than through maya, thanks for any help!
Would you be able to try this updated Maya submitter. it is using a different method of gathering the render layers so hopefully this will catch it correctly. All you should have to do is extract this to /submission/Maya/Main and then reopen maya and try submitting again.
Hi Grant - Loading the scene up here I don’t get any errors on that layer or the master layer. But it’s not enabled for batch so I’d expect it to be ignored for the export and render job submission anyway?
I did have the deadline submit running the arnold export locally before queueing up the job. The log message with the .ass export location appears to come from mtoa. We’re running mtoa-1.3.1.2, updated over the one that was installed with 2017, in case that matters?
I just opened the scene and submitted again for a sanity check. Here’s what I get in the script editor from Maya when it exports from the Deadline submitter:
[mtoa] Exported scene to file Z:/Personal_Folders/mplec/maya/test/data/masterLayer/LN_ThieveryCorp_LIT_TEST_944004_v014_test.ass
But in the job properties in the Deadline monitor, the Submission Params tab says:
This is what is being used under the hood to determine if the Render Layer should be included in the scene filename, and should let me know if it is seeing a second layer for some reason (unless this has changed, we are on mtoa 1.4).
