Search Issue Tracker
Fixed
Fixed in 6000.0.52f1, 6000.1.10f1, 6000.2.0b8, 6000.3.0a1
Votes
0
Found in
2022.3.60f1
6000.0.42f1
6000.1.0b10
6000.2.0a6
Issue ID
UUM-99801
Regression
No
NavMesh data triangulation result is always different when using NavMesh.CalculateTriangulation
How to reproduce:
1. Open the “NavMeshSeams.zip“ project
2. Open the “Layout“ Scene
3. Select the first GameObject in the Hierarchy
4. Clear and Bake the NavMesh Data in the Inspector
5. Observe the Scene view
6. Repeat steps 4-5 and observe the Scene view again
Expected result: The red triangle is in the same location
Actual result: The red triangle is in a different location
Reproducible in: 2.0.6 (2022.3.60f1, 6000.0.42f1, 6000.1.0b10, 6000.2.0a6)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- Repeat steps 4-5 if the triangle appears in the same place
- NavMesh Data is always randomly generated
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment