Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.4
2018.4.1f1
2020.2
Issue ID
1230443
Regression
No
[AI] Path of Agent is miscalculated when passing through a corner common to 4 NavMesh tiles
Reproduction steps:
1. Open the project from the attached file "1230443.zip"
2. Enter Play Mode and press the Start button in the Game View
3. Inspect the Game View
Expected result: Agent navigates from point A(marked as a red cube) to point B(marked as a blue cube)
Actual result: Agent gets "stuck" at the corner common to 4 NavMesh tiles(marked as a pink cube)
Reproducible with: 2017.4.39f1, 2018.4.20f1, 2019.3.8f1, 2020.1.0b4, 2020.2.0a5
Note - on 2019.3.8f1 and lower the agent does not get temporarily stuck on the first common corner
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
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Resolution Note (2021.2.X):
Will be fixed as part of work planned for improving Navigation links.