Search Issue Tracker
By Design
Votes
0
Found in [Package]
2019.4
2020.3
2021.1.28f1
2021.2
2022.1
2022.2
Issue ID
1394134
Regression
No
[NavMesh Components] NavMeshSurface includes non-Navigation Static setting of GameObjects as obstacles
How to reproduce:
1. Open the attached project "case_1394134.zip"
2. Open the "SampleScene" Scene
3. Open the Navigation window (Window > AI > Navigation)
4. Select the "Floor" GameObject from the Hierarchy
5. Bake using the Navigation window and the NavMeshSurface Component
6. Observe the NavMesh meshes
Expected result: NavMesh Component's mesh excludes non-Navigation Static GameObjects
Actual result: NavMesh Component bakes in non-Navigation Static GameObjects as obstacles
Reproducible with: 1.0.0-exp.1 (2019.4.36f1, 2020.3.30f1, 2021.2.14f1, 2022.1.0b10, 2022.2.0a6)
Note: Using Layers to exclude non-Navigation Static GameObjects resolves the issue
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
- 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
Resolution Note:
NavMeshComponent use a component called NavMeshModifier to select which objects should be included or not in the baking. The static value property was used in the legacy workflow, and it will be deprecated when NavMeshComponent package will be released.