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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.