Hello Ryan,
These are the results of two tests we did and we had some serious errors with both
Windows XP64
This mostly functions, except that once the job is submitted to deadline, it doesn’t actually start. Something like the command-line arguments that deadline sends to the toxik render engine aren’t correct. Also, why does deadline require a database name, when the new versions of Toxik, 2008/2009 work without a database, but a project-oriented workflow?
Tested with a Windows slave (on a different machine) and a repository located on a linux machine (same one we’re using for our production)
Linux
Now, as for publishing Toxik to deadline on Linux (Fedora8) - this mostly didn’t work for us. We needed to severely hack the SubmitToDeadline.py to actually have it show up, but crippled (missing interface controls such as the group/pool chooser widgets). It wasn’t possible to submit anything either, it only generated an error message.
did not get to testing with a slave since the job never actually showed up in the deadline monitor even though we do have write access to the deadline repository
General questions
Is there any special configuration for windows and for linux for it to work? (we have tested the autodesk backburner dispatcher and it works on both windows-to-windows and linux-to-linux jobs).
If a Toxik comp is published on Linux, can it render on Windows-based render blades with deadline? Is the reverse of this scenario possible?
The ideal scenario for us would be to be able to work and publish comps from Toxik on Linux, to have them render on Toxik windows, while using deadline as our render manager.
Thanks