FBX adding mandatory Empty as parent #63240
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#63240
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows 7 Pro 64Bit
Graphics card: NVidia Quadro 5000
Blender Version
Blender 2.8 Beta
Build Date: 2019-03-31
Hash: b936d7b16c62
Short description of error
FBX Exporter cannot save a bone rig without adding an empty object on top of the hierarchy. Sometimes it might be desired to have a bone hierarchy resting on the highest level.
For example: This creates compatibility issues with at least Unity which has its own bug with transferring Animation Data from a Rig with null as parent.
There might be other cases as well where a bonestructure being located on the root level instead of a parent is preferred or necessary.
Exact steps for others to reproduce the error
Create any bone rig hierarchy and export the rig only with either 'Null', 'Root' or 'limb Node' (doesn't matter) then open the FBX file in another application like Maya.
See screenshot:
Added subscriber: @A.Lex_3D
Added subscriber: @DanielGrauer
Changed status from 'Open' to: 'Archived'
this has already been said numerous times: Blender armatures are objects, which are de facto a 'root empty' for the bones hierarchy in FBX. Getting rid of it would be a lot of work, rather risky, and it's definitively not a bug, at best a known TODO. Thanks for the report anyway.