Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.2.1f1
2019.3.0a1
2020.1.0a1
Issue ID
1177462
Regression
No
NavMeshSurface has visual artifacts/clipping when using Physics Colliders and a specific child with a collider is present
How to reproduce:
1. Open attached project "BugRepro_4.zip" and scene "Dungeon"
2. In Hierarchy window, select "Floor" object
3. In Inspector window -> "NavMeshSurface" -> "Bake"
4. In Scene window, observe the Floor
Expected result: no clipping and visual artifacts present
Actual result: clipping and visual artifacts are present
Reproducible with: 2018.4.7f1, 2019.2.3f1, 2019.3.0b1, 2020.1.0a1
Could not test with: 2017.4.32f1
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
- 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
Resolution Note:
Low priority defect and unlikely to be fixed for the near future