Search Issue Tracker
In Progress
Fix In Review for 6000.2.8f1, 6000.3.0b5, 6000.4.0a2
Fixed in 6000.0.60f1
Votes
24
Found in
2022.3.60f1
6000.0.43f1
6000.1.0b12
6000.2.0a7
6000.3.0a1
Issue ID
UUM-102676
Regression
No
NavMeshSurface ignores convex Mesh Colliders when using Physics Colliders
Reproduction steps:
1. Open the attached project "IN-98789_AiNavBakeFailure.zip"
2. Open the "test" scene and bake the nav mesh
Expected result: nav mesh covers all stairs
Actual result: nav mesh only covers some stairs
Reproducible with:
6000.2.0a7
6000.1.0b12
6000.0.43f1
2022.3.60f1
Reproducible on: macOS 13.2.1 (Intel)
Comments (7)
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
- StackOverflowException occurs and tests fail to load when the Test Runner window is opened while System.Windows.Forms.dll and System.Deployment.dll are present in the project
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
adriant
Sep 24, 2025 07:22
As a workaround try to set the NavMeshSurface to "Collect Objects" in "Volume" instead of "All Game Objects".
zalogic
Sep 12, 2025 20:28
The only workaround found for now is to have an editor script that switches all convex colliders to non-convex when baking navmeshes and switch them back to the original settings after. Works 100%.
But this would have been a good temporary workaround directly from the engine to be applied until a final fix from the physics team lands.
davidlovegrove
Sep 02, 2025 15:02
Hi,
I've looked into this. This isn't a navigation issue as such - part of the navigation process is to gather all colliders and in this case the underlying PhysX system is failing to capture some of the stairs.
The reason for this appears to be the unusual scaling in combination with rotation at certain angles. This is causing the GJK solver to fail to find some of the mesh colliders and therefore they don't get included.
Speaking to the physics team the general advise is to make sure the scales of the colliders are reasonable, though that's hard to define as it culminates in unusual floating point values which are hard to trace back to the cause.
I did prototype a fix that changes the way these colliders are gather and that's been handed off to the physics team. It's uncertain at this time if/when this will land.
Thanks
Unityraptor81
Jun 03, 2025 07:56
This is very limiting
ChocoAlex
Apr 05, 2025 19:07
Issue still happening on 6000.0.44f1
Decreationist
Mar 14, 2025 00:41
AI Navigation package version was 2.0.6.
Decreationist
Mar 14, 2025 00:40
This issue is re-appearing in 6000.0.41f1.
Using a stair-shaped collider (ramp) with a mesh collider, set to convex. NavMeshSurface incorrectly does not generate navmesh over the collider when set to use Physics Colliders.