Search Issue Tracker
Fixed in 2021.3.13f1
Fixed in 2021.3.X, 2022.1.X, 2022.2.X, 2022.2.0b10, 2023.1.X
Votes
2
Found in
2021.3.3f1
2022.1.3f1
2022.2.0a13
Issue ID
UUM-3457
Regression
No
Navmesh modifiers influence Navmesh areas far above them on Asset edges when using "NotWalkable" or "Water" modifier
How to reproduce:
1. Open the user's attached project "navmesh_issue.zip"
2. Open Assets/Scenes/modifier_issue.unity
3. In the Hierarchy window select "NavMeshSurface"
Expected result: Navmesh modifiers does not influence Navmesh areas above them
Actual result: Navmesh modifiers influence Navmesh areas above them on Asset edges
Reproducible with: 1.0.0-exp.1 (2020.3.13f1, 2021.1.13f1, 2021.2.0b1)
Could not test with: 2018.4.28f1 (NavMeshComponents package unavailable), 2019.4.35f1 (compilation errors)
Notes: Navmesh agent height does not influence the height influence of the modifier
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
Add comment