Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2020.3.34f1
2021.3.0f1
2022.1.0b16
2022.2.0a11
Issue ID
UUM-3205
Regression
No
Baked NavMesh is dense when scene geometry includes diagonals
Reproduction steps:
1. Open the user's attached project
2. Open the 'SampleScene'
3. Enter Play mode
Expected result: The NavMesh is baked without unnecessary points on diagonal mashes
Actual result: The baked NavMesh is very dense
Reproducible with: 2020.3.34f1, 2021.3.0f1, 2022.1.0b16, 2022.2.0a11
Could not test with: 2019.4.37f1 (due to compile errors)
Note:
- Issue is no longer reproducible after rotating both 'TestMesh' and 'TeshMesh1' GameObjects 45 degrees on Y-axis
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
After evaluating the work associated with fixing this issue, we have concluded that it is a limitation of the current implementation that would require an important re-architecture to create a viable solution. We decided to add this work as a feature-request in our backlog.
It will not be addressed in the foreseeable future, so we are closing this issue as Won’t Fix.
Resolution Note (2022.2.X):
After evaluating the work associated with fixing this issue, we have concluded that it is a limitation of the current implementation that would require an important re-architecture to create a viable solution. We decided to add this work as a feature-request in our backlog.
It will not be addressed in the foreseeable future, so we are closing this issue as Won’t Fix.