Just a quick word on userSetup.py: it is called later than userSetup.mel and prohibits some things to function correctly which would work fine if loaded through userSetup.mel (an example would be dirmap). I don't know why Autodesk made it this way... but it's truly annoying.
We also have V-Ray centrally installed, and I'm using a python wrapper script to set all environment variables based on OS and then execute the standalone vray executable via subprocess. Works like a treat and offers the capability to capture stdout and stderr. // F On Mon, Apr 7, 2014 at 9:43 PM, Justin Israel <[email protected]>wrote: > Also a side note: I've used the userSetup.py as well and actually just > hade it run an environment module that was maintained in a central network > location. That way the logic could easily be updated and picked up by new > launches of Maya without being disted to any user preference locations. > This was for a studio that also didn't require that people launch Maya > from a command line under a "set shot" type of environment management. > > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAD%3DwhWNgBh6eAJ5YyUJc6FgDDfjQqbmDYe5uhrWfU95aVMb%2BqA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
