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
- Red spots appear when Blending Lighting Scenarios using Adaptive Probe Volumes
- [Windows] About Unity Window needs to be opened twice to adapt to resolution
- NullReferenceException and temporary graph corruption after entering playmode if output node connection was changed
- Sprite Renderer with Animation does not reflect Sprite changes in the Scene when switching Mask Interaction
- Error "NullReferenceException: Object reference not set to an instance of an object" is present when loading 3D text mesh in Player from an asset bundle that is built with an older Editor version
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.