connect attributes with "percentage values"?


#1

Hi guys!
I’m new to this forum and also to rigging, so I hope my question isn’t too stupid.

My problem:
I added some custom attributes to my objects to specify limits for some transformations. I also added an locator to control everything from one location. Now to my question: is there a way to connect and control all attributes togeher with percentage values? Couldn’t find such an option in the connection editor (google couldn’t help me either…)

If the question wasn’t understandable I’ll give you an example.

(and sorry for my bad english)


#2

there’s no simple button for saying 0 to 100 means -3.45 to 4.5 in x translate for instance, but several ways to do this (and I’m sure there are scripts for automating the task on highend/creativecrash.com)

anyways:

-expressions: hard coded values, for instance if you add a float attribute to a controller, and in an expression map out the value of the new attribute to the one being driven (in the case above it would be obj.translateX = controller.val / 100 * ( 4.5 + 3.45 ) - 3.45

- set driven keys: would be my first choice for you, look it up in the maya manual, basically you set a driver object (the controller that goes from 0 to 100 for instance) and a driven object. You ‘key’ the extremes and can even modify the way the values are mapped, to ease-in/ease-out controls. Beware that animators sometimes get frustrated with it, because they like to ease shit themselves

- full nodes: using multiplyDivides, plusMinusAverage and direct connections, doing pretty much the same thing as epressions would, without being expressions. It’s my favorite way to do things, but to each is own (and it can be a little faster on heavy rigs)


#3

Not sure what the OP is asking, but for quote above, a setRange node can do this.


#4

thanks for the answers!
I’ll try the methods and look what works best for me.


#5

… or a Remap Value node.


#6

my bad. I do almost everything with multDiv&plusMinus =)


#7

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.