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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment