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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
This is a duplicate of issue #1210587