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
- 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
Resolution Note (2018.4.X):
In repro project, arrays which hold data about the trajectory were too small.