job file from Maya.īut then once the job reaches the farm I get the same errors that I originally posted about.
#WHAT IS ARNOLD FOR MAYA 2017 CODE#
So the only way i can get the job to render is to a) manually run the chunk of code from the submitter script, then b) unblock that. So I have to manually force Maya to unlock that file. Because the script didn’t complete, it never told Maya to release it’s hold on that file. But at this point Maya already has a hold on the maya_deadline_info.job file and thus this is why I’m getting the error I posted above. For some reason this then allows the submit script to successfully run. The only way I can get the job to go to the next step is to manually run that bit of Mel script that checks for the camera in the Maya script editor. Error: file: O:/Assets/Animation_Share/Maya/Modules/VISMO_Deadline/Maya2017/scripts/VISMO_l line 4000: Error evaluating argument at position 1 in procedure "CheckSlashes".
Error: file: O:/Assets/Animation_Share/Maya/Modules/VISMO_Deadline/Maya2017/scripts/VISMO_l line 1573: Number of arguments on call to getRenderableCameras does not match number of parameters in procedure definition. Running deadline command: -getmaximumpriority Running deadline command: -GetCurrentUserHomeDirectory When I try to submit my Maya job I get the following error: But I want to post my experiences for posterity. I’m sure you guys are already aware of most of this. I should also note an important licensing caveat that Arnold inside Maya is ONLY licensed to work in GUI mode, so our Maya plugin’s would fail to render, unless you own network render licenses of Arnold. Hence, bake to *.ass and then kick the *.ass file. That isn’t ever going to be the most memory efficient way of doing it. The downside using the above technique is Maya is needed to be started, the potentially large scene file is opened into memory and then your chosen renderer tries to open and render your scene data. In the case of Arnold, we just expose a log verbosity override:ĭ/produc … ic-options With renderer only jobs, a few options are available, depending on renderer chosen. So you just don’t select to submit an “Export” job at job submission time. We have always supported the direct rendering of your Maya scene file via your chosen renderer. I will add this thread to our internal ticket so we can keep track here and get this fixed ASAP for you. I believe this issue was also reported by someone else this week and a developer is already looking into as of late last night.