Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2017.4.X, 2018.4.X, 2019.3.X, 2020.1.X
Votes
2
Found in
2017.2.0p4
Issue ID
977653
Regression
No
NavMeshPath sometimes returns bad paths when using Obstacle Carving
How to reproduce the issue:
1. Open the attached project
2. Open the "NavBug" scene
3. Enter Play mode
4. Navigate to the area with text "Mouse around here"
Actual result: The generated path is wrong (screenshot attached).
Expected result: The path should be generated correctly.
Reproducible with: 2018.1.0b1, 2017.3.0f3, 2017.2.1p1, 2017.2.0b1.
Notes:
The bug is caused by the Sphere which has NavMeshObstacle.Carve set on.
The wrong path occurs when the path is going through the corner point of NavMesh Surface.
Couldn't test 2017.1 and earlier versions because of the compile 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
- [Hub][Linux] Hub .AppImage does not allow to upgrade the Hub from 2.4.5 to 3.0.0-beta.2
- [Profiler] Current frame button initially hides profile frame marker
- Missing function to reset or unset a specific resource in the local binding space of compute shaders
- [Linux][Hub] Unity Hub 2.4.5 does not open "Add modules" window when clicking "Install with Unity Hub" in Build Settings
- Multiple errors appear in the Console when building for IL2CPP
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a1
Resolution Note (fix version 2017.4):
Fixed in: 2017.4.40f1