You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I could be misunderstanding the control/driver relations but to it seems like the default Metahuman mGear rig is not attaching itself to the neck_01_drv and neck_02_drv bones.
Symptom:
The EPIC Metahuman template (z-up, didn't test y-up) controls neck_C0_fk0_ctl and neck_C0_fk1_ctl don't affect the corresponding driver joints. The head is moving correctly but the neck_0x_drv joints are not linked to any controls.
Expected behaviour:
I fixed it by manually creating mgear_matrixConstraints that take the neck fk controls and neck driver joints as inputs.
Would be nice to check this against the Metahuman rig and implement an automatic fix.
Thank you!
The text was updated successfully, but these errors were encountered:
@wgergely I have checked this and I can't reproduce it with the latest mGear version. Maybe It was fixed with another ticket, since many changes have been made in this area
I am closing the ticket, Please check again with the next release 4.1 will be available very soon. Thanks
I could be misunderstanding the control/driver relations but to it seems like the default Metahuman mGear rig is not attaching itself to the neck_01_drv and neck_02_drv bones.
Symptom:
The EPIC Metahuman template (z-up, didn't test y-up) controls neck_C0_fk0_ctl and neck_C0_fk1_ctl don't affect the corresponding driver joints. The head is moving correctly but the neck_0x_drv joints are not linked to any controls.
Expected behaviour:
I fixed it by manually creating mgear_matrixConstraints that take the neck fk controls and neck driver joints as inputs.
Would be nice to check this against the Metahuman rig and implement an automatic fix.
Thank you!
The text was updated successfully, but these errors were encountered: