Search Issue Tracker
Fixed in 2021.1
Fixed in 2018.4, 2019.4, 2020.1, 2020.2
Votes
24
Found in
2017.2.0a2
2017.4
2017.4.8f1
2018.4
2019.4
2020.1
2020.2
Issue ID
1072945
Regression
Yes
A NavMeshAgent GameObject teleports to a near NavMeshSurface when collided with a moving NavMeshObstacle
Repro steps:
1. Open QA attached project "repro_1072945"
2. Enter Play Mode and observe the Game View
Expected: The moving Cube moves the Capsule when collided
Actual: The Capsule teleports to a NavMeshSurface beneath the Plane when collided
Reproducible with:2020.2.0a20, 2020.1.3f1, 2019.4.8f1, 2018.4.26f1, 2018.3.0a10, 2018.2.6f1, 2018.1.9f2, 2017.4.10f1, 2017.2.3p4
Not reproducible with: 2017.2.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
- Shadows are not cast when you first Blit the Shadow map and then set it back to Buffer
- Changes to instanced detail mesh material don't immediately apply
- [uGUI] Vertices retrieved from GetUIVertexStream method cannot be modified when adjusting them through script
- Scroll bar scrolls less in the Package Manager packages than elsewhere when pressing on the empty scroll bar area to scroll
- Undo.RegisterCreatedObjectUndo dirties the scene, but no actual changes to Scene are made
Laika16
Jul 31, 2019 12:46
I hope this bug gets fixed soon, since it makes all games with navmeshagents walking on multiple floors completely unplayable. Any encounter with dynamically moving doors or boxes results in characters disappearing due to being teleported several floors up or down. I have this bug in 2017.4.30f1.