Search Issue Tracker
By Design
Votes
0
Found in
5.1.0f3
Issue ID
704820
Regression
No
[NavMesh] Not walkable plane under walkable one causes not walkable region on walkable mesh
Steps to reproduce:
1. Open attached project
2. Open scene "navtest"
3. Notice that "navtest > c(1)" is not walkable mesh. Others are walkable.
4. Bake NavMesh and notice that instead of one, we are given two separate NavMeshes.
Note: Setting Navigation voxel size to 0.025 fixes this issue. Moving c(1) in Y axis (setting value to 13.8, for example) so that space between floor and wall segment, which is under door, would increase also fixes this issue (picture attached).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Sampling overlap causes graphical errors on specific Graphics APIs and Devices when using Framebuffer Fetch
- [Android] AssetBundle loading performance degradation when loading from a local Assetbundle
- [iOS][Android] Reflection with Generic Class returns unexpected values
- Shader Variant Collection Asset UI is hard to read when multiple Shaders and keywords are added
- Regression for "WebGL build is missing "malloc" and "free" functions when passing "-sERROR_ON_UNDEFINED_SYMBOLS=0" to emscriptenArgs"
Add comment