Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.2.0a5
Issue ID
UUM-3204
Regression
No
NavMesh path is not taking the direct path when using "width > 0" NavMesh links
How to reproduce:
1. Open the attached “OG NavMesh Test.zip” project
2. Open the “SampleScene” Scene
3. Select the GameObject "Agent"
4. Slowly move it in the z-axis from one edge of the NavMesh to another
Expected result: There is always a straight direct path provided to the target
Actual result: The path is snapping to the start/end of the connection center point making it not the most direct path
Reproducible with: 2019.4.36f1, 2020.3.30f1, 2021.2.13f1, 2022.1.0b9, 2022.2.0a5
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
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.