Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2019.3.4f1
2019.4
2020.2
Issue ID
1281314
Regression
No
NavMeshPath partial path calculation gets stuck on NavMeshLink
Reproduction steps:
1. Open attached project "NavMesh.zip" and scene "SampleScene"
2. Enter Play Mode and observe Character2 and Character1 GameObjects' movement
3. Exit Play Mode
4. In Hierarchy window, disable Issue_1/Issue_2/Issue_3/Issue_4/Issue_5/'NavMeshLink (19) ISSUE' GameObject
5. Enter Play Mode and observe Character2 and Character1 GameObjects' movement
6. Exit Play Mode
7. In Hierarchy window, enable 'NavMeshLink (19) ISSUE' and disable 'NavMeshLink (20) ISSUE' GameObjects
8. Enter Play Mode and observe Character2 and Character1 GameObjects' movement
Expected result: In all three Play Mode instances, the characters move through the NavMeshLinks uninterrupted
Actual result: The characters are stuck on 'NavMeshLink (19) ISSUE' and 'NavMeshLink (20) ISSUE' GameObjects
Reproducible with: 2019.4.12f1, 2020.1.8f1, 2020.2.0b6
Could not test with: 2018.4.27f1 (script compilation errors)
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
- Foldout arrow indent is misaligned in the Inspector when used in Custom Type
- [Android] The Player screen turns black when playing a video under certain conditions
- Search window icons at the bottom are cut off when Search window is resized vertically
- "Try something else?" text label is cut off when searching for a long text in the Search window
- Rendering Debugger window sections do not have a minimum width set when resizing with the slider in the middle of the window
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a3
The observed issue is caused by a misconfiguration of the NavMeshLinks. The NavMeshLink cost modifier should either be:
(a) -1, which instead uses the area type cost, or
(b) Non-negative, which computes the cost as (cost modifier * distance).
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b11