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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
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