Search Issue Tracker
Fixed
Fixed in 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Votes
0
Found in
6000.0.57f1
6000.2.4f1
6000.3.0b1
6000.4.0a1
Issue ID
UUM-117115
Regression
No
NavMesh Surface bakes a NavMesh when the Terrain Collider is disabled
Steps to reproduce:
- Open the attached "NavMeshOnTerrainColliderBug" project
- Open the "5_sliding_window_terrain" scene and make sure the terrain's collider is disabled
- Select the NavMesh Surface and check that "Use Geometry" is set to "Physics Colliders"
- Click bake and observe that a NavMesh is created over the terrain
Actual results: NavMesh is baked when the terrain collider is disabled although it shouldn't
Expected results: NavMesh is not baked on terrains with their collider disabled
Reproducible with versions: 6000.0.57f1, 6000.2.4f1, 6000.3.0b1, 6000.4.0a1
Not reproducible with versions: -
Can’t test with versions: -
Tested on (OS): Win 11
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
Add comment