0
$\begingroup$

I am using blender 2.73a.

I rig a mesh with a armature and export it using FBX 6.1 ASCII exporter. However when I import it in UE4 there is a another bone named 'Armature' before root bone! This happens with every mesh-armature pair. This is undesirable as it shifts the origin of the mesh (Which is root bone in UE4)

enter image description here

$\endgroup$
2
  • $\begingroup$ Please note FBX 6.1 ASCII exporter is no more maintained and considered deprecated… Would advise to use 7.4 binary one, but it also has major issues with UE4 currently (regarding bones’ animations). $\endgroup$
    – mont29
    Commented Feb 27, 2015 at 13:12
  • $\begingroup$ yeah so blender is a no go for UE4 as far as animation is concerned $\endgroup$ Commented Mar 12, 2015 at 9:31

2 Answers 2

2
$\begingroup$

There is a lot of "fixs" for this problem. For me, this one do the trick Blender (2.83 y UE 4.20):

"As things stand right now, the importer for fbx is effectively patched (a nice word for hacked) to allow as exception for Blender made fbx files if the name of the root node is 'Armature'."

enter image description here

Source: https://forums.unrealengine.com/deve...blender-export​

$\endgroup$
1
$\begingroup$

Had this same problem and spent a day trying to work it out. Reverted back to Blender 2.74 and export with FBX 7.4 binary and it worked fine.

For some reason Blender 2.75 and 2.76 add this bone, which means enabling root motion in Unreal Engine does nothing. This sucks because replacing a skeleton in Unreal when you have heaps of animations and montages is annoying. Really hope this gets fixed.

$\endgroup$

You must log in to answer this question.

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