Search Issue Tracker
Fixed in 2021.3.26f1
Fixed in 2021.3.X, 2022.2.X, 2023.2.X, 2023.2.0a17
Votes
3
Found in
2020.3.4f1
2020.3.33f1
2021.3.0f1
2022.1.0b16
2022.2.0a10
2023.2.0a1
Issue ID
UUM-5814
Regression
No
Creating a mesh in Play Mode causes an "abnormal mesh bounds" error
Reproduction steps:
1. Open the user's attached project
2. Enter Play mode
Expected result: No error message
Actual result: Error message in the Console: "abnormal mesh bounds - most likely it has some invalid vertices (+/-inifinity or NANs) due to errors exporting"
Reproduced with: 2020.3.4f1, 2020.3.33f1, 2021.3.0f1, 2022.1.0b16, 2022.2.0a10
Not reproduced with: 2019.4.38f1, 2020.3.3f1
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 (fix version 2023.2):
Verified the error no longer shows in console in 2023.2.0a17
Resolution Note (fix version 2022.2):
Verified the error no longer shows in console in 2022.2.19f1
Resolution Note (fix version 2021.3):
Verified the error no longer shows in console in 2021.3.26f1