Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.2.X, 2022.1.X
Votes
1
Found in
2020.3
2020.3.11f1
2021.1
2021.2
2022.1
Issue ID
1373302
Regression
No
The navigation system returns an incorrect path when links are involved
How to reproduce:
1. Open project "Test.zip"
2. Open "SampleScene" Scene (Assets>Scenes>SampleScene)
3. In the Hierarchy window select "Target"
4. In the Inspector window change Position "X" value
5. Observe the green path in the Scene window
Expected result: Path is not ignoring the exit point
Actual result: Path ignores the exit point
Reproducible with: 2020.3.20f1, 2021.1.25f1, 2021.2.0b17, 2022.1.0a13
Could not test with: 2019.4.31f1 (Errors: "Assets/Scripts/NavMeshComponents/Editor/NavMeshAssetManager.cs(44,73): error CS1061: 'PrefabStage' does not contain a definition for 'assetPath' and no accessible extension method 'assetPath' accepting a first argument of type 'PrefabStage' could be found (are you missing a using directive or an assembly reference?)")
Note:
- When moving "Target" to different positions in some of them the path is working as expected
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a1
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b4
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.9f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.27f1