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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
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.