Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0a6
Issue ID
755332
Regression
No
[NavMeshSurface] assigning usual navmesh on custom navmesh surface spawns it outside of navmesh area
Reproduction steps:
1.Open attached "New Unity Project 60"
2.Open "1" scene.
3.Select "Cube (1)" game object.
4.On "Nav Mesh Surface" component attach custom navmesh "NavMesh".
5.Select custom navmesh to "None".
Actual result: navmesh is set outside of object surface and it persists even when custom navmesh is changed "None".
Expected result: navmesh is set on object surface and it disappears when custom navmesh is changed "None".
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