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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
This is a duplicate of issue #1210587