I’m having trouble getting 2011 Toxik to render through deadline. Are there any tricks setting up Toxik that I might be missing.
Ok, I thought it was transposing the name of the file but actually it is in the submission dialog that pops up after you submit to deadline. It isn’t getting the new comp name but is retaining some old comp that I had tried submitting directly through Deadline. When I click the button to choose the proper file, even though the extension is correct the files do not appear in the dialog box. I have to manually type in the file name for the comp.
So now that I have that figure out I am getting an error with an exit code of 3. Any clue as to what that is?
Error Message
Exception during render: An error occurred in RenderTasks(): Error in CheckExitCode(): Renderer returned non-zero error code, 3. Check the log for more information.
at Deadline.Plugins.ScriptPlugin.RenderTasks(Int32 startFrame, Int32 endFrame, String& outMessage)
Slave Log
uler Thread - Synchronization time for plugin files: 171.875 ms
Constructor: Toxik
0: Task timeout is disabled.
0: Loaded job: Toxik Test Frame (002_050_999_4f546c43)
0: INFO: StartJob: initializing script plugin Toxik
0: INFO: Any stdout that matches the regular expression “.*Progress: ([0-9]+) of ([0-9]+)” will be handled as appropriate
0: INFO: About: Autodesk Toxik Plugin for Deadline
0: Plugin rendering frame(s): 1
0: INFO: Stdout Handling Enabled: True
0: INFO: Popup Handling Enabled: False
0: INFO: Using Process Tree: True
0: INFO: Hiding DOS Window: True
0: INFO: Creating New Console: False
0: INFO: Render Executable: “C:\Program Files\Autodesk\Composite 2011\program\txrender.exe”
0: INFO: Render Argument: -p “C:\Documents and Settings\render\Local Settings\Application Data\Prime Focus\Deadline\slave\jobsData\10037_SeaWorld_Watercolor.txproject” -c “C:\Documents and Settings\render\Local Settings\Application Data\Prime Focus\Deadline\slave\jobsData\TESTFRAME.txcomposition” -v “TESTFRAME_v2.txcomposition” -s 1 -e 2 -userfilepath “C:\Documents and Settings\render\Local Settings\Application Data\Prime Focus\Deadline\slave\jobsData\Preferences.txuser”
0: INFO: Startup Directory: “C:\Program Files\Autodesk\Composite 2011\program”
0: INFO: Process Priority: BelowNormal
0: INFO: Process is now running
0: STDOUT: 00:00:00.02 [User Message ] [Messages ] Initializing media cache C:/DOCUME~1/render/LOCALS~1/Temp/toxik/mediacache/store/64.
0: STDOUT: 00:00:00.26 [User Message ] [Messages ] Allocating 4679 MB of memory for the frame buffer cache (maximum is 15447 MB).
0: INFO: Process exit code: 3
Scheduler Thread - Render Thread 0 threw an error:
Scheduler Thread - Exception during render: An error occurred in RenderTasks(): Error in CheckExitCode(): Renderer returned non-zero error code, 3. Check the log for more information.
at Deadline.Plugins.ScriptPlugin.RenderTasks(Int32 startFrame, Int32 endFrame, String& outMessage)
Error Type
RenderPluginException
Error Stack Trace
at Deadline.Plugins.Plugin.RenderTask(Int32 startFrame, Int32 endFrame)
at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask()
I’ve also noticed that after hitting submit job to deadline and it pops up the deadline submit window. If I hit close instead of submit it will lock up toxik and corrupt my preferences.
This sounds like a bug that may have already been fixed in our internal working version. I will try to confirm this as soon as possible.
I don’t see anything in the error reports that stands out. Is it at all possible to zip up your test scenario you’ve described and post it here? We could then try to reproduce it.
I haven’t seen this problem before. I will try to reproduce and get back to you.
We just tested our internal working version with Toxik 2011, and it worked fine. I’ve uploaded a Toxik 2011 patch here for Deadline 4.0 SP1 (which you are running) that you can test out to see if it makes a difference. Before installing the patch, first make backups of the following folders:
Unzip the attached patch to \your\repository (ie: your repository root folder). Then reconfigure your Toxik plugin in the Monitor as necessary. Finally, reinstall the clientSetup script as explained here: software.primefocusworld.com/sof … Toxik_2010
Try submitting a new job from Toxik, and you should see that everything is set properly in the submitter now. Let us know if you still have problems rendering after submitting the job.
Finally, I should note that we were not able to reproduce the Toxik lock up problem, so let us know if you still get this problem with the new script.
So I was able to get it working after updating those files. There are still some glitches that I found.
When you submit a job, the Composition path is always equal to whatever I had set last from a submission through the monitor.
When I click the “…” button to browse to the tmp composition created by the submit script I can not select it. Even though there is a .txcomposition file in the directory it does not show up. To get it to work I manually had to enter the path to the tmp composition.
Also the frame count toxik uses for the end frame is exclusive, or an out point. So even though the frame says End: 33 you are actually rendering frames 1-32. In the submission window the Frame list is inclusive setting the job to render 1-33. The since the output node is only set to render 1-32 frame, frame 33 will fail on the farm with error code 3. However if I correct the frame list to be 1-32, no problems on the render.
Thanks for the feedback. Attached is a patch that should address most of the issues you pointed out. Unzip the attached patch to \your\repository (ie: your repository root folder).
I can’t reproduce this. I tried submitted a job from the Monitor, and then submitting a job from within Toxik afterwards, and the Composition path was listed correctly. Can you give me the exact steps you follow to reproduce this problem?
This should now be fixed. Also, we had a problem here where the file selection window appeared behind the main submission window. This has been addressed as well.
We now subtract 1 from the end frame to set the default frame range correctly.
Thanks for the quick update. I have to say out of all the software we use I’ve never had such a fast response to an issue… THANKS!
The frame end fix as well as the composition selection is working fine now. I am still having the problem where it doesn’t fill in the composition field. Anything else you can think of on that one? Right now I’m just cutting an pasting the path from the project line and appending the comp version as a quick workaround.
Also, it only happens every so often, and it might be a Toxik issue, but after I hit start in the Toxik render window, and it pops up the Deadline Submission dialog, Toxik freezes and I have to kill it. When I do it corrupts my user preferences. Oddly enough I can still submit the render and it renders fine so all the files look like they get copied properly. It just never returns.
And 2 wish list items…
1)Is there a way to set the default name of the job to the Composition that is being rendered. Right now it is coming up Untitled.
2)Is there a way to report back to Toxik that the render is done? As it is now it leaves pending renders in the background progress bar at the bottom.
Now that I think about it, the problem could lie either in the SubmitToDeadline.py client setup script that you configure Toxik to run, or in the command line being passed to the script. I’ve attached our current working copy of SubmitToDeadline.py (SubmitToDeadline.zip). Unzip this file to your Toxik Scripts folder and have Toxik point to this new python script instead of the one you’re currently using.
Here is the full command that we’re using within Toxik, so double check this as well:
Note that the -r and -b options are optional - it just makes submission require a few less clicks. Give this a try and let us know if the composition problem continues.
The attached ToxikSubmission.zip patch does this now. Just unzip it to \your\repository (ie: your repository root folder).
Our tests show that this works fine, so maybe the updated SubmitToDeadline.py client setup script attached here might address this. When we submit, the status bar at the bottom shows 1 pending process, but when we close the submission dialog after a submission, it goes back to 0, and shows that the action is complete.