Loic Le Goff

Quick update on this. There is actually no issue with this setup, the culprit was my blendshape that wasn't properly setup so targets were triggering via different ranges regardless of the sliders setup!

I will try using the abstract control for this, this might work value-wise but it's not going to be behaving like the usual face rig slider type I'm used to.
Will update tomorrow

Update:
Unfortunately it's the same with an abstract control. As the control moves away with the shape, it probably impacts the origin x and y

Hello,

I have the following setup, riveted controls drive blendshape targets, that then drives back the rivets. I use the promoted t of my transformObject to drive the blendshape target.

t seems to read the the position of the control relative to it's restlocal which is expected, if you remove the rivet from the equation and move a control along y by .25 units, ty would be .25

Now if you add the rivet in the equation, since it's driven by a blendshape, the rivet xform doesn't actually match with the amount of units I'm trying to move it by.
It's resulting in blendshape targets being triggered exponentially faster based on the amount of displacement of the prim driving the rivet.


If you see in the above gif, the first shape I trigger gets to its full target at around 0.0065 units when it's supposed to be 0.025 whereas the next one gets to full target around 0.020 since there is less displacement.

So I would like to know if there is a way to only get the value of my cursor instead of the the position of my xform relative to it's rest. That way I have a uniform range with my cursor to trigger my blendshape targets.

Hopefully this is clear enough.