Search Issue Tracker
In Progress
Fix In Review for 6000.0.X, 6000.2.X, 6000.3.X
Fixed in 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
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Tags window completely breaks and throws Exception errors when Adding a Tag to a GameObject
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
Add comment