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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Resolution Note (2018.4.X):
In repro project, arrays which hold data about the trajectory were too small.