Search Issue Tracker
By Design
Votes
1
Found in
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1127193
Regression
No
Malformed .fbx mesh causing extremely large UV Metrics
How to reproduce:
1. Open attached project "MeshMetrics.zip"
2. In Project window, find and select a mesh named "103" a child of "liangyimenposui.FBX" model
3. In Inspector window, observe "Mesh Metrics[0]"
Expected result: the "Mesh Metrics[0]" is small or equal to 1
Actual result: "Mesh Metrics[0]" is equal to 2.6e+07
Reproducible with: 2018.3.6f1, 2019.1.0b3, 2019.2.0a6
Could not test with: 2018.1.9f2 and older, Inspector window had no "Mesh Metrics" value
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2019.2.X):
The current behaviour is the expected one, large faces with small UV areas require a high mipmap level and this mesh has a good amount of faces with collapsed UVs.