Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2020.3.6f1
2020.3.17f1
Issue ID
1364263
Regression
Yes
Creating a mesh in Play Mode causes an "abnormal mesh bounds" error when using UploadMeshData()
How to repro:
1. Open users' attached “ExampleProject.zip” project
2. Open “SampleScene” Scene
3. Enter the Play Mode
Expected result: No errors in the Console
Actual result: Error “Mesh 'mesh 1': abnormal mesh bounds - most likely it has some invalid vertices (/-inifinity or NANs) due to errors exporting.” appears in the Console
Reproducible with: 2020.3.6f1, 2020.3.25f1
Not reproducible with: 2019.4.34f1, 2020.3.5f1, 2021.1.0a1, 2021.1.24f, 2021.2.7f1, 2022.1.0b2
Notes:
- If the error does not appear in the Console close the Editor and repeat the steps (sometimes can take 5-20 tries)
Full error:
Mesh 'mesh 1': abnormal mesh bounds - most likely it has some invalid vertices (/-inifinity or NANs) due to errors exporting.
Mesh bounds min=(0.00, 0.00, -431602080.00), max=(340282346638528859811704183484516925440.00, 340282346638528859811704183484516925440.00, 352.00). Please make sure the mesh is exported without any errors.
UnityEngine.Mesh:UploadMeshData (bool)
MeshGenerator:LoadMesh (int,int,UnityEngine.Mesh) (at Assets/Scripts/MeshGenerator.cs:161)
MeshGenerator:LoadMesh1 (int,int) (at Assets/Scripts/MeshGenerator.cs:133)
MeshGenerator:SetTriangleInBuffers () (at Assets/Scripts/MeshGenerator.cs:127)
MeshGenerator:Awake () (at Assets/Scripts/MeshGenerator.cs:26)
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
- WebGPU: ASTC texture mip levels are corrupt
- [Vulkan] Crash on with multiple stack traces when rendering large Terrain with specific hardware
- Crash on SkinnedMeshRendererManager when interacting with a prefab generated with uncombined meshes using Synty Sidekick Character Creator
- Crash on folly::detail::safe_assert_terminate_v when updating the Meta XR SDK Packages
- The text font falls back on a different font depending on the fallback font used
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a1