Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0f3
Issue ID
984522
Regression
No
NavMesh bakes inside collider marked as Not Walkable
Steps to reproduce:
1. Open attached project "New Unity Project (2).zip"
2. Make sure the cube scale is large enough (20,10,20 is fine)
3. intersect the cube with the plane
4. Make sure the cube is marked as "Not Walkable" in the Navigation > Object pane
5. Bake Navmesh
6. Observe the inside of the cube on the plane having a NavMesh
Expected: If the cube is not walkable, there should not be any surface inside of it that has a NavMesh
Actual: The plane that is inside the collider of the cube is marked as walkable terrain for a NavMesh agent
Reproduced on: 5.6.5f1, 2017.1.3f1, 2017.2.1p1, 2017.3.0p1. 2018.1.0b1
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
Add comment