Search Issue Tracker
Fixed
Votes
2
Found in
2021.3.3f1
2022.1.5f1
2022.2.0a17
Issue ID
UUM-2969
Regression
No
NavMeshObstacles cause dead zones in the NavMesh pathing
How to reproduce:
1. Open project "NavMeshTest.zip"
2. Open the Navigation window (Window>AI>Navigation)
3. Choose the Bake tab and press the "Bake" button
4. Enter the Play Mode
5. In the Hierarchy window select "Agent"
6. In the Inspector window press the "Warp Agent to Dead Zone" button
7. Press the "Path Agent to point 1" or the "Path Agent to point 2" button
8. In the Hierarchy window disable "NavMeshObstacle2"
9. Press the "Path Agent to point 1" or the "Path Agent to point 2" button
Expected result: Agent can path with the Obstacles enabled
Actual result: Agent can't path and the warning appears
Reproducible with: 2020.3.20f1, 2021.1.25f1, 2021.2.0b16, 2022.1.0a12
Could not test with: 2019.4.31f1 (Error: Failed to load '/Users/adas.grinkevicius/Downloads/New Unity Project (77)/Assets/Scene/NavMesh.asset'. File may be corrupted or was serialized with a newer version of Unity.)
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-65656