Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2019.4
2020.3
2021.1.4f1
2021.2
2022.1
2022.2
Issue ID
1405512
Regression
No
Navmesh.Raycast returns wrong position when NavMesh is generated in x,y plane
How to reproduce:
1. Open the attached project "NavMeshRayCastBug_19_4_2.zip"
2. Open Assets/Scenes/SceneZup.unity
3. Open Window>AI>Navigation
4. Enter Play Mode
Expected results: Navmesh.Raycast returns position on the outer edge
Actual results: Navmesh.Raycast returns position on the inner edge
Reproducible with: 2019.4.36f1, 2020.3.30f1, 2021.2.15f1, 2022.1.0b11, 2022.2.0a4
Not reproducible with: 2022.2.0a5, 2022.2.0a7
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2022.2):
Fixed by unknown PR in 2022.2.0a5