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
- 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
This is a duplicate of issue #1210587