Search Issue Tracker
By Design
Votes
0
Found in
2019.3.0a6
2019.4.2f1
2020.1
2020.2
Issue ID
1265117
Regression
Yes
Certain FBX files do not get broken down into multiple parts after importing
How to reproduce:
1. Open user-submitted project (848143_FBXBreaks.zip)
2. Expand the 'Models/starship_exploded_02.FBX' asset
3. Look for the parts with the name 'elevator'
Expected result: there are 2 parts with the name 'elevator'
Actual result: the 'elevator' consists of only 1 part
Reproducible with: 2019.3.0a6, 2019.4.5f1, 2020.1.0f1, 2020.2.0a19
Not reproducible with: 2018.4.25f1, 2019.3.0a5
Notes:
As an example, meshes with less than 2^16 vertices but more than 2^16 triangles are affected
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2020.2.X):
As of 2019.3, we have corrected a bug in the import system which erroneously resulted in meshes being split when they shouldn't have been.
In 2019.3 and above, those meshes will no longer be incorrectly split - this is the correct behaviour.