Search Issue Tracker
Fixed in 2020.3.45f1
Won't Fix in 2022.1.X
Fixed in 2020.3.X, 2021.3.X, 2022.2.X, 2023.1.X, 2023.1.0a22
Votes
0
Found in
2020.3.36f1
2021.3.6f1
2022.1.8f1
2022.2.0b1
2023.1.0a3
Issue ID
UUM-8240
Regression
No
[NavMesh] NavMeshObstacle placed near the edge of a NavMesh causes isolated polygons where NavMeshAgents can get stuck
Steps to reproduce:
1. Open SampleScene in the attached project ("TestNavMesh2.zip")
2. Enter Play Mode
3. Select the Scene View
4. Select the Agent GameObject in the Hierarchy
5. Manually drag the Agent towards the narrow path between the NavMeshObstacle and the edge of the NavMesh
6. Leave the Agent in the spot where it cannot traverse anymore
7. Disable and Enable the NavMeshAgent Component
Expected result: The NavMeshAgent can still be manually dragged
Actual result: The NavMeshAgent is stuck (see attached AgentStuck.mp4)
Reproducible on: 2020.3.36f1, 2021.3.6f1, 2022.1.8f1, 2022.2.0b1, 2023.1.0a3
Notes:
-See attached AgentStuck.mp4 for help in reproducing the issue
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 2023.1):
Fixed in 2023.1.0a22
Resolution Note (2022.1.X):
Backport to branch 2022.1 has stopped as it reached end of life.