We just moved to deadline 7 to get integration with fTrack, and we are having this issue that is really bad for our pipeline at the moment. Is there anything I can do to get it fixed? We did not have any problem using deadline 5 or deadline 6 with yeti and we did not change nothing in the pipeline except the deadline version
we are working on windows 7 machines but we will move soon to centos 6.5
we are using solidangle arnold to render
2014-09-11 12:17:29: 0: STDOUT: pymel : ERROR : Failed to get controlCommand list from pgYetiMaya
2014-09-11 12:17:29: 0: STDOUT: pymel : ERROR : Failed to get modelEditorCommand list from pgYetiMaya
2014-09-11 12:17:29: 0: STDOUT: pymel : ERROR : Failed to get command list from pgYetiMaya
2014-09-11 12:17:29: 0: STDOUT: pymel : ERROR : Failed to get constraintCommand list from pgYetiMaya
2014-09-11 12:17:29: 0: STDOUT: pymel.core : ERROR : Failed to get depend nodes list from pgYetiMaya
2014-09-11 12:17:29: 0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2014-09-11 12:17:29: 0: STDOUT: Error: file: C:/Users/user/AppData/Local/Thinkbox/Deadline7/slave/rendernode03/jobsData/541176652ff2d207d8e76ee1/pupa_vfx_still_frame_lighting_cc_v002.ma line 8: initializePlugin function failed (pgYetiMaya)
Can you upload the full error report? You can export it from the report viewer by right-clicking on it in the list and selecting Save Report.
Also, if you’re submitting the Maya job with the Use MayaBatch option enabled, try disabling it to see if that makes a difference. Regardless of whether or not it fails or succeeds, can you also send us a report from that job as well?
Thanks for the logs! It looks like the plugin can’t get a license, which would likely explain this issue:
2014-09-12 09:23:31: 0: STDOUT: [Fri Sep 12 09:23:31 2014] Yeti 1.3.12: Yeti v1.3.12, built on Aug 6 2014 at 17:06:10
2014-09-12 09:23:31: 0: STDOUT: [Fri Sep 12 09:23:31 2014] Yeti 1.3.12: (c) 2010-Present Peregrine Labs a division of Peregrine Visual Storytelling Ltd. All rights reserved.
2014-09-12 09:23:31: 0: STDOUT: [Fri Sep 12 09:23:31 2014] Yeti 1.3.12: ERROR pgLicenseCheck - License system could not get a valid server handle, error: Can't read license data (-102)
Can you check to see if your Yeti license server is running?
The next step is to see if the same problem occurs outside of Deadline. Go to a slave that the error occurred on (in this case, rendernode03) and copy the BB_job_test.ma file to this machine. Then open a command prompt and run this command (note that I’m assuming the scene file is at C:\BB_job_test.ma, so if you copy it somewhere else, update the path as necessary):
This is the same command that Deadline is running when Use MayaBatch is disabled, so if you get the same error, then at least we’ve ruled out Deadline as the source of the problem.
The scene is able to render without using the license since it is just a cache.
Also in the past on deadline 6 and 5 we got the same error but it was not fatal and the fur was correctly rendered.
The yeti license is required only if you render a scene without a precalculated cache. And the scene we are rendering are pre cached
To be sure I made a test using a batch (through a bat file) on a blade and it works (without any license)
More in the past we rendered shows using yeti and older realese of deadline
Hmm… can you still run the command line from my previous post on a node and post the output? We can compare it to the output from the Deadline job to see if anything stands out.
Hi,
finally we switched to linux system. At the moment we are working on centos 6.5
Maya 2014 with the latest arnold and yeti realease. Everything is working inside maya but again when I submit the job to the farm I am getting strange errors. I triple checked all the environment variable but I cannot get a frame rendered. If I submit a scene without yeti everything is working correctly but the probllems comes in the moment I submit a scene containing a yeti node. I also contacted peregrinel labs to double check the license issue we had on windows and they said that when I run caches I don’t need at all to connect a license,
Anyway on the tests I made on linux the machine that I am using for rendering is my workstation that also have a yeti license connected.
I attach you two different error log, one with mayabatch activated and the other one without
In the maintime I am testing with the export ass and kick function, but without success
Let’s first focus on trying to get this to work with MayaBatch disabled. First, can you copy pupa_vfx_still_frame_anim_v003_cc_cache_cc_v003_light_cc_v006_linux_lowRes.ma to the Desktop on this machine, and then open a terminal on the “vfx10linux” machine (the one that the mayaSubmitSceneLog log is from), and run this command:
Note that this command line assumes you copied /home/cristiano/Desktop, so if it’s somewhere else, change the path accordingly. If this renders properly, try restarting the machine and then run this job through Deadline. Send us the log from both the command line test, and from the Deadline job the next time you run it after restarting the machine.
The error in the log appears to be the result of an environment that isn’t setup properly. Once you’ve run the tests and send us the log, we should know more and we can go from there.
Regarding the environment variables I set them up as required from the company that produce Arnold and Yeti. I attach you the configuration I have for them:
That’s the exact same error you’re getting when running through Deadline with MayaBatch disabled, so you’ll need to sort out this issue before you’ll be able to render with Deadline. From googling the problem, it sounds like you need to set the MAYA_RENDER_DESC_PATH variable to point to the folder that contains arnoldRenderer.xml (which should be in the Arnold installation folder). Once you have that set, try the command line again to see if that fixes the problem.