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
- Tile Palette Edit mode turns off in Play Mode
- The Editor crashes when Generating Font Atlas in the Font Asset Creator with “9999999999” padding and 256x256 Atlas Resolution
- [iOS] An “ArgumentNullException” error is thrown when GetIntroductoryPriceDictionary() method is called
- Memory leak warnings are constantly thrown when Generating Font Atlas in Font Asset Creator with 4096x8192 Atlas Resolution
- “Glyph rendering has been aborted due to sampling point size” Log is printed and Font Atlas is not generated when Atlas Resolution is 8192x8192, and the Render Mode is SDF
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