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][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.0a8
Backported to: 2018.4.5f1, 2019.1.14f1, 2019.2.0b10