Search Issue Tracker
By Design
Votes
1
Found in
2019.3
2019.3.0f6
2020.2
Issue ID
1237479
Regression
No
Armature corruption when importing FBX Binary files exported from Blender 2.8
How to reproduce:
1. Open the attached (Debug_FBX.zip) project
2. Open the "SampleScene" Scene
3. See the "legs_binary" model in Scene View
Expected result: Model exported as Binary FBX from Blender looks the same as the model exported as FBX ASCII
Actual result: Model exported as Binary FBX from Blender has armature corruption
Reproducible with: 2019.3.16f1, 2019.4.1f1, 2020.1.0b13, 2020.2.0a15
Notes:
- Support for FBX ASCII was removed in Blender 2.8 and the only way to import FBX models into Unity is to use FBX Binary
- Could not test in 2018.4 and older versions, because Style Sheet Import Errors
-
max_autious
Oct 13, 2020 10:07
Has there been any cross-report to blender on this issue? It's causing us to hold back to blender 2.79b and unable to update to blender 2.83.7 LTS or 2.90.1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Light brightness gets intense until the 'Lightmap Encoding' quality is changed when baking Lightmap
- Crash on LinearCollectionField::LinearCollectionField after a 'm_ArrayField != SCRIPTING_NULL' assertion when opening a project
- Import Activity Window takes long time to open
- [Android] Artifacts appear in texture Preview Window on Android Platform when selected Override ETC2 fallback is 16-bit
- Child Canvas' Sorting Layer is changed to the same value as the parent Canvas after interacting with Dropdown UI object
Resolution Note (2020.2.X):
There appears to be an issue in the Blender FBX Exporter. In the supplied files with this bug, we see the same erroneous results outside of Unity in the FBX Viewer.
In this instance, the Unity Importer correctly represents what is within the FBX file.