Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.4.3f1
2020.2
Issue ID
1263441
Regression
No
Trajectory of the path is re-calculated incorrectly when using NavMeshSurface
Reproduction steps:
1. Open the attached project ("case_1263441-Pathfinding.zip")
2. Open the repro scene ("Test")
3. Enter Play Mode
4. Press A to start the pathfinding
5. Inspect the agent moving to the destination
Expected result: Agent avoid obstacles and reaches the destination
Actual result: Agent re-calculates the path and goes through the corner of the obstacle
Reproducible with: 2018.4.26f1, 2019.4.9f1, 2020.1.3f1, 2020.2.0a21
Note: The issue does not reproduce when using regular NavMesh instead of NavMeshSurface
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note (2021.1.X):
This issue is a limitation of the current NavMesh algorithm and cannot be solved without fundamental changes in the code. The current code, usually gives the global optimal solution, but it is not guaranteed. There can be some special cases (like this example) for which the code gives a near-optimal, not the global-optimal solution.