We use a launcher here, pretty useful. Tied into our asset tracking system too, so anything rendered not only has a dependency graph of the scenes and references used to create it, but versions of software, versions of script paths, versions of libraries.... everything. Means we never get stuck with the 'but this shot used to render!' problem, as resurrecting an old shot also resurrects all the versions of all the tools and scripts used when that frame ran.
On Mon, Feb 8, 2010 at 10:47 AM, Keir <keirr...@gmail.com> wrote: > Yes do the same thing, > Our version is a C# app that parses an xml launcher definition, sets > environmental variables, copies files and launches Maya. <snip> -- http://groups.google.com/group/python_inside_maya
