Search Issue Tracker
Fixed
Fixed in 2022.3.63f1, 6000.0.50f1, 6000.1.5f1, 6000.2.0b1
Votes
0
Found in
2022.3.42f1
6000.0.15f1
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-78065
Regression
No
Height Mesh generation results in unexpected spikes/streaks across the whole map in the generated NavMesh Surface when re-baking
How to reproduce:
1. Open the “ReproProjectNavMesh“
2. Open the “Export“ scene
3. Open the “Navigator“ GameObject in the Inspector
4. Under the NavMesh Surface component Clear the baked NavMesh
5. Bake a NavMesh with the current settings
6. In the AI Navigation overlay toggle on the Show HeightMesh property
7. Observe the Scene view
Expected result: No streaks/spikes of Height Mesh are crossing the entire scene
Actual result: Streaks/Spikes of Height Mesh are crossing the entire scene
Reproducible with: 1.1.5 (2022.3.42f1), 2.0.3 (6000.0.15f1)
Could not test with: 1.0.0-exp.4 (2021.3.42f1) (Could not resolve the Console errors)
Reproducible on: macOS 14.5 (Intel), Windows 11 (Reporter’s)
Not reproducible on: No other environments tested
Note: The issue reproduces with both adding the “com.unity.ai.navigation“ as an embedded package, and downloading it from the registry
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
Add comment