← All ideas
  • Published 28 Apr 2024

Improve FBX exporter to better support game engines

Here's a prime example of a developer who has managed to fix some of the issues of FBX exporter for Blender. It is being maintained, but this frankly needs to be done baseline to vastly improve compatibility with game engines such as Unity and Unreal.

github.com/A-Ribeiro/CustomBlenderFBXExporter

My biggest issue with current FBX in Blender is that the Armature becomes a ghost bone at the top of the hierarchy when importing into game engines. That makes it also impossible to set up your own "Root" bone inside the Armature to have specific controllers for it when using drivers. In game engines it also causes headaches where you want to animate from the root bone, so any additional bloat bones should never appear.

Here's how the skeleton looks like in Blender:

Skärmbild 2024-04-29 012838.png

This is how it looks like in Unreal if the Armature is being named something else, such as "Skeleton": Skärmbild 2024-04-29 012635.png

This is how it looks like when using the modified FBX exporter from GITHUB:

Skärmbild 2024-04-29 013630.png

Skärmbild 2024-04-29 013238.png

Please add this option in for future versions of Blender!

100%

Development Status: Open

Upvote 9 Downvote 0
Frozen_Death_Knight
28 Apr 2024

4 Comments

Lauloque

I think it would be clever to edit the title to specifically mention the actual request: allow to remove the armature node in FBX export.

But regardless, this has been requested already: optional fbx export without mandatory Armature bone in hierarchy ⁠— Right-Click Select

1
Frozen_Death_Knight Author

Yeah, but considering that the add-on does more than just remove the Armature as a root bone, I made the title more generic and gave a specific example of what it helps solve.

Lauloque

Well then it would be pertinent to detail here what the proposal is about rather than leaving people with just an external link.

mont29

Since there's already code implementing the suggested change, the best way to move forward here would be to submit pull requests to the official gitea repo . One per updated/modified feature. ;)