|12 December 2007||#1|
los angeles, USA
umm, so I searched and searched and im finally aggravated enough to post and ask for help.
this is probably a stupid question, as im learning mel and this is my first macro.
Im writing an automatic leg setup that has ik/fk switch, no flip knee (cgtk style), reverse foot, and stretchyness. This is where im getting stopped:
Instead of being helpful, maya selects the plusMinusAverage node and spits out
// Error: No object matches name: connectAttr
Maybe that is helpful, i ain't gettin' it.
It is our duty to transcend words and images in order to encounter REALITY
|12 December 2007||#2|
triangle noodle makerportfolio
Join Date: Oct 2006
i think that's simply some syntax errors. from my experience, if maya said "No object matches name: blablabla", it's usually because i forgot to put ';' after a statement or '$' in front of a variable.
Last edited by r4inm4ker : 12 December 2007 at 06:16 AM.
|12 December 2007||#3|
No Coffee=Grumpy Riggerportfolio
Join Date: Apr 2003
I know how much writing an auto rgging script can be frustrating. One of the problems is trying to come up with all the senarios you may run into and try to accomodate it.
Just a few suggestions that may help you in building your script.
Q: How can I figure out which side I'm working on and name my controls accordingly
A: Based off what is selected, determine which world X axis are you on. If you are on the neg side then you are on the characters "Left" and so on for the right. Simple way to test for this and prefix your controls with either "L_"or "R_". This could also affect settings you have (maybe twist values?).
You don't need to have your script select a control to connect it.
So here is something you can do:
So by passing the variables around it makes it more modular, cleaner and less hard-coded elements that make it hard to expand your code for anything else down the line you may want to add in the mix.
Keep it up and happy holidays
|12 December 2007||#4|
Join Date: Apr 2005
maya doesn't really help you with those error messages. when i can't find the problem i often outcomment: /* ... */ some parts where i assume the problem and run the script. if the error disappears i reactivate some of the outcommented parts and again try the script until the error occurs. with this i can find the error quite quickly
|12 December 2007||#5|
Join Date: Sep 2003
Thread automatically closed
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.
Note that as CGTalk Members, you agree to the terms and conditions of using this website.
|Thread Closed share thread|