Search Issue Tracker
Fixed in 2021.1.X
Votes
9
Found in
2018.4
2019.2
2019.3
2019.3.0f1
2020.1
Issue ID
1206120
Regression
No
Path is calculated outside of NavMeshLink and NavMesh connection when using NavMeshQuery
How to reproduce:
1. Open the attached project's "case_1206120-Project.zip" Scene labeled "SampleScene"
2. Enter the Play Mode
3. Click the "Calculate&DrawPath-Experimental" Button
4. Inspect the drawn Path
Expected result: Calculated Path is inside the NavMeshLink and NavMesh connection
Actual result: Calculated Path is outside the NavMeshLink and NavMesh connection
Reproducible with: 2018.4.15f1, 2019.2.17f1, 2019.3.0f4, 2020.1.0a18
Couldn't test with: 2017.4.36f1 (Namespace errors are thrown)
Comments (1)
-
adriant
Nov 20, 2020 12:13
Fixed also in 2020.2.0b10, 2020.1.12f1 and 2019.4.16f1 by the same solution as for https://issuetracker.unity3d.com/issues/navmeshquery-dot-createlocation-always-returns-the-same-point-when-using-a-navmeshlink-polygon-even-if-the-width-is-0 .
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
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
- Previously deleted “DefaultLookDevProfile“ is present when upgrading the Editor version
- [Ubuntu] UI text and buttons are missing spaces in Unity Version Control > New Workspace window
- "Inherit attribute is not supported" warning is shown but attributes are available in VFX Graph Output and Update blocks
Resolution Note (fix version 2021.1):
Fixed in Unity 2021.1.0a1