Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0a1
2018.2.5f1
2018.3.0a1
2019.1.0a1
Issue ID
1106847
Regression
No
Carving Navmesh can break AI path and there is no way to detect that
Steps to reproduce:
1. Download and open the attached project
2. Open Scene "test1.unity"
3. Enter Playmode
Expected result: when path breaks, auto repath activated and path gets fixed
Actual result: auto repath does not work as corner count is not properly reported when broken
Reproduced on 2017.3.0a1, 2017.4.16f1, 2018.3.0f1, 2019.1.0a11
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:
NavMeshAgent.path.corners can indeed report zero corners if the path gets modified by carving. We cannot change this nor can we provide a better status flag at this time.
The agent can still repair successfully the path in that situation, immediately or within a few frames, and then the number of corners will be reported correctly again.