Search Issue Tracker
Active
Under Consideration for 2021.3.X
Votes
1
Found in
2021.3.3f1
2022.1.5f1
2022.2.0a17
Issue ID
UUM-2965
Regression
No
NavMeshSurface shows different result compared to Navigation system NavMesh with the same mesh and settings
Reproduction steps:
1. Open the attached project "Sample Project"
2. Open "SampleScene" scene (Assets/Scenes/SampleScene)
3. Open Navigation window (Window/AI/Navigation)
4. Bake the navmesh if it doesn't show up
5. Compare the right-most navmesh with the middle navmesh
Expected result: navmeshes are the same
Actual result: navmeshes are different
Reproducible with: 2019.4.22f1, 2020.3.0f1, 2021.1.0f1, 2021.2.0a11
Could not test (errors): 2018.4
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
Add comment