Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
2021.3.52f1
2022.3.63f1
6000.0.51f1
6000.1.7f1
6000.2.0b5
6000.4.0a1
6000.5.0a1
Issue ID
UUM-108989
Regression
No
Navigation Agent stops moving where multiple different NavMesh Surfaces overlap when the "NavMeshAgent.SetPath" method is used
How to reproduce:
1. Open the “BugTest.zip“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Observe the red Capsule Game Object in the Game view
Expected result: The red Capsule eventually reaches the purple Cube
Actual result: The red Capsule starts moving but then stops where different NavMesh Surfaces overlap
Reproducible in: 1.1.1, 2.0.8 (2021.3.52f1, 2022.1.0a1, 2022.3.63f1, 6000.0.51f1, 6000.1.7f1, 6000.2.0b5)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- Not reproducible by assigning a position to NavMeshAgent.destination
- In the reproduction project, the blue ball always reaches the purple Cube
- Disabling and re-enabling the “NavMesh Surface B” GameObject at any point will fix the issue for the time being
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment