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
4
Found in
2017.3.0b6
Issue ID
962825
Regression
No
NavMesh Agent stuck for a while at deadlock, only then moves straight to target on a specific labyrinth
To reproduce:
1. Open repro project
2. Open 'NavMeshTest' scene
3. Bake NavMesh
4. Play scene
Expected: capsule gameObjects will move straightly to the target(particles effect in right upper corner)
Actual: they stucks at the deadlock near target, and only after a while moves straightly to the target
Reproduced: 5.6.3p4, 2017.1.2p1, 2017.2.0p1, 2017.3.0b6, 2018.1.0a1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Will be fixed as part of substantial refactoring work planned for the NavMeshAgent.
More information will be communicated on the Navigation forum. https://forum.unity.com/forums/navigation.79/