Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2020.1
2020.1.3f1
2020.2
Issue ID
1274343
Regression
No
NavMeshAgent oscillates across a point of NavMesh when moving close to edges using NavMeshLinks that connect different heights
How to reproduce:
1. Open user-submitted project (NavMeshBug.zip)
2. Open the NavigationBug scene
3. Enter Play Mode and watch the actor
Expected result: the actor fluidly moves between points
Actual result: the actor ends up moving in one place
Reproducible with: 2020.1.0a19, 2020.1.4f1, 2020.2.0b1
Could not test with: 2018.4.26f1, 2019.4.9f1, 2020.2.1.0a18(project setup incompatible)
Notes:
The project is made with 2020.1 NavMesh Components.
See NavigationBug - OffMeshLink fix for the expected result(which is using OffMeshLink instead of NavMeshLink)
-
adriant
Jan 04, 2021 10:37
The issue happens more often when the NavMeshLinks encountered on the path are very wide. As a workaround, try to reduce the width of the NavMeshLinks as much as possible, to values below 5. If possible, replace every very wide link with 2 narrower links.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a8
Resolution Note (fix version 2020.2):
Fixed in 2020.2.1f1