Search Issue Tracker
Duplicate
Votes
11
Found in
2018.4
2019.2
2019.3
2019.3.0f1
2020.1
Issue ID
1210662
Regression
No
Path is not calculated between two points located in the same NavMesh Node when using NavMeshQuery
How to reproduce:
1. Open the attached project's Scene labeled "SamePolyIssue"
2. Enter the Play Mode
3. Click the "Calculate&DrawPath-Experimental" Button
4. Click the "Calculate&DrawPath-Experimental - Secondary" Button
5. Observe the drawn path
Expected result: Path between two points in the same NavMesh Node is drawn
Actual result: Path between two points in the same NavMesh Node is not drawn
Reproducible with: 2018.4.15f1, 2019.2.18f1, 2019.3.0f4, 2020.1.0a18
Couldn't test with: 2017.4.36f1 (Package Manager does not exist)
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
- Application.systemLanguage returns "Unknown" when system language is set to Norwegian Bokmål/Nynorsk
- Project fails to load scene in WebGL due to lack of memory
- Particle System's Point Light flickers while Looping is on and Emission Rate over Time set to 0 with Bursts Count set to 1
- [GLES2] [iOS] UnityGet2DClipping function returns wrong values
- Lightprobes influencing object shading on specific position is not deterministic and causes artefacts
This is a duplicate of issue #1210587