Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.1p4
Issue ID
925424
Regression
No
NavMesh Surface components don't take the Transform scale into account
How to reproduce:
1. Open attached project
2. Open scene Main.unity
3. Open the Navigation window
4. Play the scene
- Note that one of the cubes is not properly carved around
- Can also be reproduced by having a NavMesh Modifier Volume, a NavMesh Surface then baking the Surface normally
- This issue affects the NavMesh Modifier Volume and the NavMesh Surface "Volume" Object Collection mode
- This is inconsistent with Physics Colliders scaling with the game object scale
- Reproduced with 2017.1.0f2 (66e9e4bfc850), 5.6.0f3 (497a0f351392)
- Won't Fix: Unlike the Physics system, the navigation system has a low level component-less API. Additionally, scale does does not work with baked Navmesh data, because the agent radius and height affects the tessellation.
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