Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2018.3.0b9
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1156590
Regression
No
[NavMesh] NavMesh Agent is occasionally blocked by obstacle that has been moved from the NavMesh
To reproduce:
1. Open QA attached project "1154946-NavMeshObstacleRepro.zip"
2. While in project, Enter Play mode and press "Toggle obstacle movement" button
3. Look for the agents near the obstacles being stuck moving back and forth (make sure to disable the obstacle movement when behavior is noticed)
Result: agents are unable to proceed to their target, moving back and forth
Reproduced in: 2017.4.27f1, 2018.3.0b9, 2018.3.12f1, 2018.4.1f1, 2019.1.4f1, 2019.2.0b3, 2019.3.0a4
Note1: this usually takes 10-40 seconds to reproduce, dependent on obstacle / agent / grid size set up (check Scene game Object for relevant script)
Note2: agents do not get stuck if obstacles are not toggled to move
Note3: seems to mostly reproduce on the zone near obstacle, however it is possible to get it stuck anywhere
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
Add comment