Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
0
Found in
2017.4.0f1
2018.3.5f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1144525
Regression
No
NavMeshAgent gets stuck at holes in NavMesh
How to reproduce:
1. Open attached project "agent_stuck_when_interrupting_path.zip" and scene "AgentGetsStuck"
2. Enter Play mode
3. In Game/Scene views observe the red agent
Expected result: agent reaches the TargetB object
Actual result: the agent gets stuck on the way and cannot advance
Reproducible with: 2017.4.28f1, 2018.4.1f1, 2019.1.5f1, 2019.2.0b5, 2019.3.0a4
Comments (1)
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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
tEFFx
Jul 11, 2019 14:08
I'm having issues that are possible related to this as it seems like they are indeed fixed in 2019.3.
Any ETA when the fix will arrive in 2018.4 so I can avoid using an alpha version in production?
Thanks!