Sorry about the lack of updats! Quite busy at work and packing up my things and moving..
So, yesterday I made a few nice scripts. I have a global variable and if its 1, you can only select the DAG nodes that have a special attribute == “animatorSelectable” 🙂 This global variable can be set to 1 in animators userSetup. But can be turned on/off in the animators menu.
So, now I don’t have to worry too much about cleanness of hierarchy or locking stuff. I don’t use a seperate hierarchy for controls, so allthough I allready use custom pickwalking, this should be a VERY nice safety. I might set things up so that userSetup also turns of “key hierarchy” in the set key options… That one could get me in real trouble!
We are soon moving into production of “Hungry Hamsters”, so things are starting to be a diferent ballgame. When I started at the company we were about 10 people, soon we will be 20+ on the animator side alone. So, minimising support calls and covering places things can go wrong, seems to be extra important now.
I have to mention that Mikkel Jans (The guy that did the mjPolyTools, and is now working for us), made the scriptJob that runs and makes sure that “bad” DAG noges, get de-selected.. On my briliant request of course 😉 (Let’s see – this might turn out to be the worst idea of the century… Some of my ideas tend to do)
As allways, any comments, input or questions are most welcome!
Hope to see ya’ soon