Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2019.4
2019.4.0f1
2020.1
2020.2
Issue ID
1271682
Regression
No
Crash on CalculateMeshBounds when baking Navmesh
Reproduction steps:
1. Open user's attached project
2. Open scene "TestScene"
3. Go to Window > AI > Navigation and open the Bake tab
4. Press Bake
-- observe crash
Reproducible with: 2019.4.9f1, 2020.1.3f1, 2020.2.0a21
Could not test with: 2018.4.26f1 (assets serialized in a newer version error)
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 2021.1):
The crash is caused when the LOD version of a terrain specified to be used by NavMesh is missing an assigned mesh. Moving forward, trees with missing meshes will be skipped during the NavMesh baking process, and a warning will be emitted. Fixed in 2021.1.0a1