Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
0
Found in
2018.3.0a1
2018.3.12f1
2019.1.0a1
2019.2.0a1
Issue ID
1144605
Regression
No
NavMeshAgent gets stuck on its path when a NavmeshObstacle with carving is toggled on/off nearby
How to reproduce:
1. Open the attached "bug-carve-stuck-new.zip" project
2. Open the "scene_new_case" scene
3. Open the "Navigation" window to see the NavMesh. Go to top menu -> "Window" -> "AI" -> "Navigation"
4. Enter Play Mode
5. Disable 'Carver' GameObject (remove the tick of checkbox near the object's name in the Inspector tab) after 'Agent' object crosses 'TargetA' object
Expected result: NavMeshAgent is not affected
Actual result: NavMeshAgent gets stuck
Reproducible: 2018.3.13f1, 2019.1.0f1, 2019.2.0a11
Can't reproduce: 2017.4.25f1, because of `UnityEditor.PrefabUtility' does not contain a definition for `GetCorrespondingObjectFromSource' error
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 (fix version 2019.3):
Fixed in: 2019.3.0a8
Backported to: 2018.4.5f1, 2019.1.14f1, 2019.2.0b10