This problem come out of nowhere while testing the submission of a XSI (Autodesk ((( ) scene to Deadline. This might be a submission script error, but not sure yet.
So I am trying to submit the scene with various settings. Everything works fine ( I mean I can submit the scene to deadline) than suddenly I get an error message, this:
// ERROR : Traceback (most recent call last):
// File “”, line 92, in Main
// XSIToDeadline.Main()
// File “\zinc\dlr3\submission\XSI\XSIToDeadline.py”, line 15, in Main
// SubmitToDeadline()
// File “\zinc\dlr3\submission\XSI\XSIToDeadline.py”, line 198, in SubmitToDeadline
// framestr = framestr + “x” + GetFrameStep(scene.ActivePass)
// UnboundLocalError: local variable ‘framestr’ referenced before assignment
// - [line 91 in D:\Softimage\XSI_7.0\Application\Plugins\SubmitXSIToDeadline.py]
\zinc\dlr3 is our Repository.
Few words about why I am testing the submit: it seems to me that somehow the settings get stuck in the deadline custom property parameter. Especially if I first submit with scene render options and than I change the settings in pass frames dialog of Render Managers.
Thanks for the info! We’ve figured out the problem and posted the patch here (we think the problem only occurs when the frame step in the scene options is greater than 1). To install, first make a backup copy of the files in \your\repository\submission\XSI, then unzip the attached file to the same folder. Restart XSI and see if you continue to have problems.
If I am here another question Our sysadmin install every program to “d” drive not the default “c” it could be a problem? On the render farm he use the same way which cause some problem. Deadline can’t find the files although they were there. After we reinstall the XSI to the “c” drives this problem solved.
This shouldn’t be a problem. We would definitely need specifics (ie: which software are you using, what errors are you getting, etc) to investigate further.
Seems to me your patch working fine! No time to test it unfortunately, but I won’t forget it.
Have you any idea about the second error issue (error message when opening keyboard mapping)?
We seemed to have fixed this, and I’ve attached the patch here. This patches the client setup XSI script, so you can unzip it to \your\repository\clientSetup\XSI, and then distribute it to your workstations. After restarting XSI, the error shouldn’t appear when you launch the keyboard mapping window.
((( ) scene to Deadline. This might be a submission script error, but not sure yet.
Our sysadmin install every program to “d” drive not the default “c” it could be a problem? On the render farm he use the same way which cause some problem. Deadline can’t find the files although they were there. After we reinstall the XSI to the “c” drives this problem solved.