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
- Clear Dynamic Data On Build does not clear data after a clean build when the Atlas Population Mode is set to "Dynamic" or "Dynamic OS"
- A tile from the wrong layer gets selected in the Tile Palette when an Aseprite file with multiple layers is imported as a Tile Set
- Particle geometry is inverted, billboard is not lit, not receiving shadows in cubemap reflection when Render Alignment is set to View
- Menu bar list orders change when Domain Reload is performed
- Unity Hub Module icons wrap poorly when they occupy two rows
Resolution Note (2018.4.X):
In repro project, arrays which hold data about the trajectory were too small.