Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.4.1f1
Issue ID
1030046
Regression
No
Walkable Area randomly appearing on non-walkable meshes
Steps to reproduce:
1. Open attached project
2. Open _Scenes/StartZone
3. Bake out NavMesh/Observe the already generated NavMesh
Expected result: the tops of trees are consistently baked or not baked
Actual result: some tree tops are baked, others are not
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
Resolution Note (2021.2.X):
- If the goal is to remove every walkable surface on top of the tree pine. By design, it requires to use a NavMeshModifier attached to each Tree or use a 'non-walkable' NavMeshModifierVolume that encompass them all.
- If the goal was to make every surface on top of the tree pine being walkable, the changeset 08098fb allows that by reducing the 'Minimum region area' settings