Search Issue Tracker
By Design
Votes
0
Found in
2021.3.30f1
Issue ID
UUM-49795
Regression
No
NavMesh Baked area is not visible when Gizmos is turned on and the Navigation window is closed
How to reproduce:
1. Open the attached "Robotory.zip" Project
2. Open the "SampleScene"
3. Turn on Gizmos in the Scene View
4. Observe the Scene View
Expected result: NavMesh is visible when Gizmos are turned on
Actual result: NavMesh is not visible and only seen when having the Navigation window/tab open
Reproducible with: 2021.3.30f1, 2022.2.0a13
Not reproducible with: 2022.3.10f1, 2023.1.15f1, 2023.2.0b11, 2023.3.0a7
Fixed in: 2022.2.0a14
Reproducible on: macOS Ventura 13.5 (Intel)
Not reproducible on: No other environment tested
Notes:
- A possible workaround is to have the “Navigation” window docked so that it would always be visible/focused
- Reproducible on a new Project
- The issue might be related to the “AI Navigation” Tool Bar missing from the Scene View
- The first time reproducing the issue, the regression point was visible, however now it reproduces only up to 2022.2.0a14, so it is highly inconsistent to look for the regression point
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
- Errors "InvalidOperationException: Trying to use a texture (_InternalGradingLut)..." and “Render Graph Execution error” shown and Scene turns black when 16 or more Render Objects are used
- GameObjects in the Game View are rendered differently than in the Scene View when the Rendering Path is set to "Deferred" and Screen Space Shadows Renderer Feature is added
- Errors “InvalidOperationException: Trying to use a texture (_CameraDepthTexture)...” and “Render Graph Execution error” shown when selecting GameObjects with Mesh Renderer from the Hierarchy
- macOS stutters in a minimal project
- [Usability] HDRP Wizard calls for VR fixes when opening the HDRP Wizard a second time after they have already been applied and the Wizard has finished checking
Resolution Note:
I have verified this same behavior in 2020.3 LTS.