Search Issue Tracker
Won't Fix
Unknown (hidden) 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X
Votes
0
Found in
2020.3.36f1
2021.3.4f1
2022.1.5f1
2022.2.0a17
2023.1.0a1
Issue ID
UUM-5510
Regression
Yes
NavMesh.Raycast doesn't return correct hit position
Steps to reproduce:
1. Open the user attached "NavMeshCastTest03.zip" project
2. Open SampleScene
3. Watch the Gizmo in the Scene Window that represents the NavMeshHit position
Reproducible with: 2020.2.7f1, 2020.3.0f1, 2020.3.36f1, 2021.3.4f1, 2022.1.5f1, 2022.2.0a17
Not reproducible with: 2019.4.40f1, 2020.2.6f1
Expected result: The Raycast returns false as there are no obstacles in the NavMesh
Actual result: The Raycast returns true with no obstacles in the NavMesh
Note: The NavMesh.Raycast is returning an incorrect hit. This appears to be related to some edge cases where the Raycast meets with problematic polygons
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
- [Linux] "Error while reading movie" errors are thrown when opening templates
- Shader warnings are being thrown after building Mixed Reality Template
Resolution Note:
The workaround provided to the customer fixed the issue:
Adding an offset to the NavMeshSurface, so that the tile-grid is not constantly aligned with the 2d walkable area. Moving the local transform of the object holding the NavMeshSurface can help creating the offset without having to move other objects in the environment.