Transformation constraint - ability to use self
Hi. I don't understand why I can't use the object as a target of transformation constraint of this same object. Making rotation depend on it's location, making scale X depend on scale Y etc. would really be useful. Currently it looks like I have to use drivers for that, but with drivers I can't specify when calculations happen in chain of constraints.
4 Comments
"It's Hacker Time."
When you are using Pose Menu → Constraints Sub-Menu → Copy Constraints to Selected Bones Operator, it is possible to create a "Self Target".
I've discovered when making this tutorial (check the behavior from this timed video; however, after the Copy is made, if you edit that Bone Constraint anyhow apparently (on the Bone that has Target on itself), the Self Target vanishes, so you need to have the Copied Bone Constraint perfectly edited from another Bone, before applying the Copying Operator): youtu.be/q9xdMXFvij4
I know this because then, by reading your topic, I've tried to create a Self Transformation Bone Constraint… and it worked. I recorded a video clip, but it can't be posted here unfortunately. But it's very simple; these informations should be enough.
Yeah… it should be "fixed": I mean, this Self-Target behavior (at least for some cases) should be improved and turned possible to edit normally by default.
Have you checked if this isn't a bug? Because you can see and click the
selfobject, it just doesn't give any result nor even an error message.Either it should be possible and devs need to fix it, or it isn't supposed to and devs need to fix the listing or at least make a warning message - in addition to consider this feature proposal.
You cannot use yourself as a fulcrum, because then you will not move. This is protection from recursion. Cause and effect don't have to be the same
No actually, In this particular constraint it would absolutely make sense to be able to use
selfas Target. Sure if you try to transfer one transform to the exact same transform, that would produce nothing. But in any other case like transfering LocationX to RotationX, it does make sense.