Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.3.X, 2022.1.X
Duplicate in 2021.3.X
Votes
1
Found in
2019.4
2019.4.6f1
2020.3
2021.1
2021.2
Issue ID
1328727
Regression
No
Unidirectional NavMeshLink results in NavMeshAgents pathing incorrectly
Reproduction steps:
1. Open project 'case_1328727-navmesh-link-breaks-pathing (1)'
2. Open 'SampleScene' in Assets\Scenes
3. Play Scene
4. Click on the middle of the platform on top in Game view
Expected result: Character can path correctly with NavMeshLink
Actual result: Character can't path correctly with NavMeshLink
Reproducible with: 0.1.0-preview.2 (2019.4.24f1, 2020.3.4f1, 2021.1.3f1, 2021.2.0a15)
Could not test with: 2018.4.33f1 (could not compile scripts)
Notes:
• This issue doesn't occur when you disable the NavMesh Link
• This issue doesn't occur when NavMeshLink is set to Bidirectional
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a10
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.1f1
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.2f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.34f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.40f1