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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
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.