Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X, 2022.1.X
Votes
0
Found in
2020.3
2020.3.17f1
2021.1
2021.2
2022.1
Issue ID
1363972
Regression
No
Nav Mesh Agent gets stuck in the Play Mode when Nav Mesh Obstacles Position Z is set to 1.59
Reproduction steps:
1. Open the "TestWeirdNavMesh" Scene in project "TestNavMesh.zip"
2. Enter the Play mode
3. Observe the Game View
Expected result: The "Agent" GameObject starts going away and keeps going
Actual result: The "Agent" GameObject starts going away and gets stuck
Reproducible with: 2020.3.18f1, 2021.1.21f1, 2021.2.0b12, 2022.1.0a8
Could not test with: 2019.4.30f1 - (Errors in the Console because project was downgraded)
t seems that placing NavMeshObstacles in certain ways will block the NavMeshAgents from passing through areas that do not have obstacles
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a2
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b9
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.13f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.28f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.39f1