I’m trying to use xform -q -ws -t to query the position of the FK wrist, then use xform -ws -t (object) to move the IK wrist controller (I know this picture has me trying to use the elbow - that was a starting point
xform -ws claims to operate in world space, but it seems like when I set it the xform worldspace translations, they appear somewhere else. Does anyone know what’s going on?
I know that I could use constraints to achieve my ends, but if I can go for an option that’s less bulky, all the merrier.
xform -q -ws always works fine for me, but xform -ws -t to position it does not always work as fine as it would seem. had this problem since maya 2009.
so whenever in code i need to position something i use the “move” command, it does not look as clean as the xform but it does the trick
Odd. Even with xform -q -ws it gives me the odd coordinates.
I wonder if it’s a bug and Autodesk broke something without realizing it. Also, move isn’t queryable, which makes me a sad panda.
edit: It seems xform doesn’t work with true world space, just some odd calculation from local space, which is really weird. I fixed it by using locators parented under a group at (0,0,0). It gave me their true location. Now I have to apply the transformation to the wrist controller, which is an issue because even with the move command, it still operates inside that arbitrary space.
I’ve had this for a while, and never found the root cause. Sometimes with xform, if you through in the -rp (for rotation pivot) you get a more accurate and reliable result. Or skin the cat another way like you’ve done.
Hi everybody!
Found to this site eventually =)
Nice to finally get this answered. Been bugging me to =/
Are there any reason why you can’t use delete parentConstraint ?
I kinda abandoned the xform command for the problems you’ve stated. It seems to work, but it doesn’t in every scenario :S
