Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0a12
2018.4.5f1
2019.1.13f1
2019.2.0f1
2020.1.0a1
Issue ID
1185336
Regression
No
The NavMeshAgent can not arrive at the Destination if there is the Nav Mesh Obstacle
To reproduce:
1. Download attached "New Unity Project.zip" project and open in Unity
2. Open "SampleScene" scene
3. Enter to Play mode
Expected results: The NavMeshAgent easily arrives at the Destination even if there is the Nav Mesh Obstacle
Actual results: The NavMeshAgent can not arrive at the Destination if there is the Nav Mesh Obstacle
Notes:
- This issue reproduces on Editor, Standalone and other Platforms
- Sometimes the NavMeshAgent can easily arrive at the Destination even if earlier it could not
Reproduced on Unity 2018.4.5f1, 2018.4.10f1, 2019.2.7f1, 2019.3.0b5 and 2020.1.0a6
Not reproduced on Unity 2018.3.14f1 and 2018.4.4f1
Regression on Unity 2018.4.5f1
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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Resolution Note (2020.1.X):
The issue stems from an inconsistency in the agent radius setting for the navmesh and the NavMeshAgent obstacle avoidance radius (0.06 vs 0.5), leading the agent to attempt to follow a path through a gap that is too narrow. The recommended solution is to bake the navmesh with the correct agent radius (0.5). For scenes with multiple agents of varying radii, use NavMeshComponents.