Home Website Youtube GitHub

Matahuman Guide IK / FK Hand axis doesn't match the guide orient before build

Hello guys,
I’ve looked around in the forum and i haven’t seen this , or i think :frowning:

We are using the défault Epic Metahuman Template Y UP, with EpiC Metahuman Snap
The guide are well oriented with the same axis of the metahuman bone hand
.
But after the build of the template, the IK and FK are slightly offsseted from 20° from the original axis of the bone and guide.

Wich i think it shouldn’b be ?!


is there a original settings that we are missing, or it’s by default?
Is there any solution? Because it’s hard to animate with it.

Thank you

2 Likes

Can confirm recreating this issue, getting similar offset when building a metahuman Y up template with the snap option.

Hello! I am checking that and other issues found on the metahuman template. It should be fixed in the new mGear release :smiley:

3 Likes

Thanks for looking into it! I’ve noticed the same thing happens to the foot joint orientation with the EPIC_leg_02.

1 Like

Hello @wasp0r
I have been checking this, and I don’t think it is a bug, but a lack of clarity in what the blade does.
Please check the video and let me know your thoughts

Added clarity on the setting description:

Thank you for the clarification - I’m not currently generating the skeleton through the guide, I already have the skeleton in the scene before building the components, as I already have a metahuman skeleton with a skinned mesh in the scene. With this approach, I don’t think the blade does anything to solve my issues with the hand and leg orientations. Currently, my work-around is to straighten the legs and rotate the wrists joints ~22.5 degrees along the X axis prior to building the rig.

As you can see, the controls generated doesn’t line up with the default metahuman skeleton conventions (as this is a mesh & skeleton directly from the Metahuman Creator), which results in these odd rotation angles regardless of blade adjustments:


If this is intended behavior, fair enough - I’ll probably try to adjust the component’s construction code to account for this discrepancy. Let me know if you require a file to test with!