Search Issue Tracker
Fixed in 2022.3.63f1
Fixed in 2022.3.X, 6000.0.X, 6000.1.5f1, 6000.2.X, future release
Votes
0
Found in
2022.3.42f1
6000.0.15f1
6000.1.0a7
6000.2.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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment