Search Issue Tracker
In Progress
In Progress in 6000.0.X
Under Consideration for 2021.3.X, 2022.3.X
Votes
0
Found in
2021.3.43f1
2022.3.44f1
6000.0.16f1
Issue ID
UUM-78679
Regression
No
NavMesh is incorrectly calculating the shortest path when the path is rotated over the edges of the NavMesh
Reproduction steps:
1. Open the attached “NavigationDebugging.zip“ project
2. Open the “Pathfinding XY” Scene and double click on “End” GameObject to focus on it
3. Move “End” GameObject to create a path between it and the start game object
Expected result: The path over the NavMesh is the shortest path between the start and end points
Actual result: The path over the NavMesh makes unnecessary stops increasing the path length
Reproducible with: 2021.3.43f1, 2022.3.44f1, 6000.0.16f1
Reproduced on: macOS Sonoma 14.5 (Intel), Windows 10 (by the reporter)
Note: Reporter noted that when a NavMesh is rotated using NavMesh.AddNavMeshData(navMeshData, Vector3.zero, Quaternion.Euler(-90, 0, 0)); instead of NavMesh.AddNavMeshData(navMeshData); the paths around the edges of the NavMesh no longer take the shortest route and now make unnecessary stops
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
Add comment