Loving the documentation for the retargeting tools. I am doing a full match setup between two skeletons that need a bit of rotation tweaks to get things oriented. Is there a way to mirror the tweak pose values from r <> l so I don't need to do each side manually?
It would need to properly invert some rotations, but not all rotations. Who doesn't love those little gotchas with rotations?
Any help would be greatly appreciated.
Rig Match Pose SOP: Mirror tweak rotations across skeleton?
1248 6 2- benfox
- Member
- 9 posts
- Joined: Aug. 2017
- Offline
- edward
- Member
- 7868 posts
- Joined: July 2005
- Offline
- benfox
- Member
- 9 posts
- Joined: Aug. 2017
- Offline
Thanks for the info. I gave it a shot, and while the mirror pose SOP seemed to do the trick, for some reason it is breaking the skeleton animation when I put it back into the stream. The blue skeleton has the animation on the way into the rest of the network. I had used a stash pose higher up to store the original rest, and that works without issue. Not sure what breaks with this one. The white skeleton is the mirrored one I am storing, which is correct. But the main skeleton that comes out from the rig stash pose is the red one, which is the original rest_transform I extracted to mirror. I know that sounds a bit confusing, but maybe it makes sense.
Any more tips would be appreciated. Thanks
Any more tips would be appreciated. Thanks
- edward
- Member
- 7868 posts
- Joined: July 2005
- Offline
The "rigstashpose_No_Animation" node's first output should look the same as its input (ie. the "ANIMATION" node) since we just want to copy the mirrored pose into rest_transform. You're not seeing that? I'm not sure which poses you're tweaking on the Rig Match Pose though, because I think it writes to both the rest_transform in either its first or second output.
- tamte
- Member
- 8769 posts
- Joined: July 2007
- Online
the mode is set to Restore, and even though it's grayed out, that's what it is doing
so your main skeleton will become restored from original rest_transform
(the UI and functionality of that node is a bit confusing, probably a BUG, not only it's Restoring, it will also pass the second input pose as the Stashed Pose even though it is not really stashing it in that mode)
If you just want to store the new rest_transform, RMB on Mode and do revert to default, or disconnect second input change it to Store and connect back
so your main skeleton will become restored from original rest_transform
(the UI and functionality of that node is a bit confusing, probably a BUG, not only it's Restoring, it will also pass the second input pose as the Stashed Pose even though it is not really stashing it in that mode)
If you just want to store the new rest_transform, RMB on Mode and do revert to default, or disconnect second input change it to Store and connect back
Tomas Slancik
FX Supervisor
Method Studios, NY
FX Supervisor
Method Studios, NY
- benfox
- Member
- 9 posts
- Joined: Aug. 2017
- Offline
- edward
- Member
- 7868 posts
- Joined: July 2005
- Offline
-
- Quick Links