Search Issue Tracker
Duplicate
Duplicate in 1.0.X
Votes
1
Found in [Package]
Issue ID
NAVB-8
Regression
No
NavMeshSurface Component doesn't bake properly when Component NavMeshModifier Override Area is enabled
Reproduction steps:
1. Open attached project "case_1331858-BugReport (1)"
2. Open Scene "SampleScene" from Assets>Scenes
3. Select "NavMesh" GameObject
4. Observe NavMesh in Scene view
Expected result: NavMesh is baked in a smooth rectangle shape
Actual result: NavMesh has random cuts baked into it
Reproducible with: 1.0.0 (2018.4.33f1, 2019.4.24f1, 2020.3.8f1, 2021.1.4f1, 2021.2.0a17)
-
Resolution Note:
This issue is a duplicate of another issue
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-3457 -
Resolution Note (1.0.X):
This issue is a duplicate of another issue
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-3457
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #UUM-3457