Search Issue Tracker
By Design
Votes
9
Found in
2018.4
2019.2
2019.3
2019.3.0f1
2020.1
Issue ID
1210587
Regression
No
High Cost Navigation Area is not avoided when finding path with Experimental.AI NavMeshQuery
How to reproduce:
1. Open the attached project's Scene labeled "AreaClippingIssue"
2. Enter the Play Mode
3. Click the "Calculate&DrawPath-Experimental" Button
4. Observe the drawn path
Expected result: Path is drawn around the high Cost Navigation Area
Actual result: Path is drawn through the high Cost Navigation Area
Reproducible with: 2018.4.15f1, 2019.2.18f1, 2019.3.0f4, 2020.1.0a19
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (2018.4.X):
In repro project, arrays which hold data about the trajectory were too small.