Search Issue Tracker
Fixed
Votes
0
Found in [Package]
2018.3
Issue ID
1109195
Regression
No
NavMesh is created on top of the object when it is set as "Not Walkable" and the object is close to any "Walkable" object
How to reproduce:
1. Open attached project "NavMeshModifier_Bug.zip" and scene "SampleScene"
2. In Hierarchy window, select "NavMeshSurface" and press Bake in the Inspector window
3. In the Hierarchy window, expand "Greybox_NotWalkable" object and select "Cube_tilted (1)"
4. In the Inspector window, observe that "NavMeshModifier" -> "Area Type" is set to "Not Walkable"
4. In Scene View, observe the "Greybox_NotWalkable" object
Expected result: the NavMesh is not present on "Greybox_NotWalkable" object
Actual result: the NavMesh is generated on top of the "Greybox_NotWalkable" object
Reproducible with: 2018.3.2f1, 2019.1.0a14
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note:
Fixed in: 2021.2.0a11
Resolution Note:
Fixed in 2019.4.31f1
Resolution Note:
Fixed in 2020.3.16f1
Resolution Note:
Fixed in 2021.1.16f1