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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
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.