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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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