I'm using rc1 and have not been able to divine the exact problem. If I run standard maya.standalone in our tool server there is no problem: userSetup is evaluated nice and early in the boot process. In our load process we are running pymel.
This problem only happens when we run pymel.core instead of maya.standalone. The strange thing is that pymel.core works fine for the toolserver copy of Maya. That is, pymel.core initializes maya and our tools run without issue in batch mode within our toolserver app. Then, if I attempt to run interactive Maya from the toolserver the userSetup.py is not called. I didn't have time today to get the logging going, but will take a look at that some time next week. I did take a quick look at the .conf file, but I'm not familiar with it and could use a little help getting it to output something useful. thanks, -Judah On Fri, Mar 12, 2010 at 5:37 PM, Chad Dombrova <[email protected]> wrote: > userSetup.py runs before userSetup.mel. > > but regardless, if this problem is the fault of pymel, i'd like to get to > the bottom of it. we use userSetup.py with pymel 1.0 without any problems, > but could be some other configuration difference. > > -chad > > > -- > http://groups.google.com/group/python_inside_maya > -- http://groups.google.com/group/python_inside_maya
