Split translation constraint (different bones for x and y)

heyvern · Post by **heyvern** » Mon Feb 26, 2007 5:43 pm

Pretty simple. Instead of one bone as the control for both values allow a different bone for each value, x and y.

I have written a layer script to do this exact thing... but... I feel it would simpler to have it in the application.

-vern

Genete · Post by **Genete** » Mon Feb 26, 2007 6:58 pm

Extremly neccesary. I vote for it.

CartoonM!ke · Post by **CartoonM!ke** » Mon Feb 26, 2007 7:34 pm

Heck, it could go even further; it could be a constriant that requires two bones and you could have it average between the two bones, favor one bone over the other, average just the X,Y postions and/or the angle of the two bones.

Hmmm??

heyvern · Post by **heyvern** » Mon Feb 26, 2007 7:39 pm

Cool idea!

Never thought of that. Two bones are listed for the translation constraint. One bone has 0 for x the other 1 for x. If you mix and match values they "share" control.

This would be a lot harder to implement in AS than a simple split as it would require adding in features that don't already exist in the program. I would be happy with just the split for now.

-vern

CartoonM!ke · Post by **CartoonM!ke** » Mon Feb 26, 2007 7:47 pm

My thought is like this, ask for the Moon and Stars, but settle for the Moon

heyvern · Post by **heyvern** » Mon Feb 26, 2007 8:04 pm

Hee hee...

Not with programmers! Ask for the moon AND the stars they say "You're crazy!" and you get nothing.

I prefer to ask for the moon and hope they might add the stars in the future. (as long as the star isn't bald and in rehab of course.)

To go to the moon we had to orbit the earth first.

-vern