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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (2018.4.X):
In repro project, arrays which hold data about the trajectory were too small.