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
- NullReferenceException is thrown when assigning an Object to a custom DebugUI.ObjectField in Rendering Debugger
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
This is a duplicate of issue #1210587