Search Issue Tracker
Won't Fix
Votes
5
Found in
2017.3.0f3
Issue ID
984654
Regression
No
NavMesh Path does not wrap around the edges of an object
To reproduce:
1. Open the attached project "NAVMESHAGENT PATH EDGE WRAP.zip"
2. Open scene "scene"
3. Play
4. Open the Navigation tab to show the navmesh
5. Observe the path not wrapping around the edges of the top-right corner ("navMeshPath.png")
Reproduced with: 5.6.5f1, 2017.1.3f1, 2017.2.1p2, 2017.3.0f3, 2017.3.0p2, 2018.1.0b3
Note: Not reproducible after slightly moving the cube
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2021.2.X):
As a performance optimization, the current implementation of the Navigation system does not guarantee that the path found towards the destination is always the shortest one (i.e. optimal). In the cases when the path found through a section of the NavMesh (the game environment) is sub-optimal, it is recommended to slightly change the environment geometry in that area such that the NavMesh geometry improves. In turn this will increase the chances of obtaining the shortest path.