Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2017.4
2019.3.0f6
2020.2
Issue ID
1249726
Regression
No
OffMeshLink does not calculate the path correctly after carving a NavMesh at runtime
How to reproduce:
1. Open user-submitted project (New Unity Project.zip)
2. Open the scene.unityscene
3. In the Scene View note the red line indicating the path between the small and the large islands
4. Enter Play Mode
Expected result: the path remains the same as in Edit Mode
Actual result: the path fails to cross the off mesh link in Play Mode
Reproducible with: 2017.4.40f1, 2018.4.24f1, 2019.3.15f1, 2020.1.0b10, 2020.2.0a12
Notes:
Disabling the 'Obstacle' GameObject prevents this issue
Rebaking the NavMesh with step height >= 0.1 prevents this issue
Disabling and re-enabling the OffMeshLink GameObject in Play Mode prevents this issue, but disabling and re-enabling NavMeshObstacle breaks it again
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a21
Resolution Note (fix version 2020.1):
Fixed in 2020.1.4f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.9f1