Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.4.1p2
Issue ID
836000
Regression
Yes
[NavMesh] [Bake] Regions of different areas are removed if area is less than "Min Region Area"
Repro steps:
1. Open "PathError.zip" project
2. Load "Test" scene
3. Open the Navigation window and select the Bake tab
4. Bake Navmesh
Navmesh does not connect around two blocks if the Plane object is under the "floor_01" prefab and set to Not Walkable/Jump/Dirt, if you disable Plane object in the hierarchy or set it's Navigation Area to Walkable it connects correctly.
Actual: Navmesh baked on a prefab doesn't connect between cubes if the Plane object under prefab is set to Not Walkable/Jump/Dirt.
Expected: Navmesh baked on a prefab should connect between cubes if the Plane object under prefab is set to Not Walkable/Jump/Dirt.
Reproduced on: 5.4.1p2, 5.5.0b3
Did not reproduce on: 5.3.6p5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment