0
$\begingroup$

Recently I've modelled and rigged a character using the included Human Meta-rig, and after editing out the bones I didn't need, I parented everything to a new single bone at the base of the character called root (Circled in Blue and selected)Root Bone Circled in Blue

Animating with this rig had so far worked just fine as all the actions I had made were in place, however, problems arose when I decided to animate my first root motion action. The animating process worked fine but as I imported the action into my game engine (Unreal Engine 5), the animation did not work as intended even with root motion active. It seems that the engine is reading the origin point of the Meta-rig (Called Meta-rig, circled in red below) as the root bone of the hierarchy, despite the actual root set in blender being the root bone circled before. enter image description here

enter image description here

As I said before, when imported into UE5, the root of the skeleton seems to be that origin point.enter image description here

Am I missing something? I have tried reparenting the root bone to be the first in the hierarchy and making it so that it replaces the "Metarig" in the object list to no avail, since it seems to not be possible. Am I doing something wrong? Should that tiny orange dot be moving at all or even considered a bone? Any help or insight is very appreciated.

Many thanks.

Improve this question
$\endgroup$
1
  • $\begingroup$ No one knows? Im truly at a loss here, my bone hierarchy in UE4 is considering that Metarig as the first bone of the chain and i have no idea how to get rid of it. $\endgroup$
    – Yareese Foxtrot
    May 8, 2022 at 19:36

2 Answers 2

Reset to default
0
$\begingroup$

I had to figure this out myself after all.

The problem is that UE5, for some dumb reason, takes the name of the armature object and makes it the first bone of the hierarchy if that object is not named "armature" in blender, hence why it was creating the "Metarig" bone at the beginning of my hierarchy. I only had to change the name to that and the root was correctly recognized.

Of course, that means that all my in place animations with the previous skeleton are now broken and I basically have to redo a lot of work I've already done. The joys of game dev, huh? At least I fixed the problem.

Thanks for nuthin bozos. jk I hope this helps someone at some point.

Improve this answer
$\endgroup$
-1
$\begingroup$

Unfortunately, the root movement animation still won't work. The solution to this is to create keys for the skeleton itself and move the animation keys of the root bone there. But that's not all, you need to set the rotation -quaternions on the stage and swap the keys of the Y and Z axes with the positions of the movement and rotation. And the y-axis is reflected in -.

Improve this answer
$\endgroup$
1
  • 1
    $\begingroup$ As it’s currently written, your answer is unclear. Please edit to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center. $\endgroup$
    – Community Bot
    Dec 15, 2022 at 18:18

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .