Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
Votes
0
Found in
2017.4.0f1
2018.2.20f1
2018.4.1f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1154946
Regression
No
[NavMesh] NavMesh fails to create all portals connecting two tiles when having obstacles aligned on the tile borders
To reproduce:
1. Open QA attached project "1154946-NavMeshObstacleRepro.zip", scene City
2. Observe the area between two Nav Mesh Obstacles
Result: NavMesh path is calculated incorrectly due to obstacle positioning breaking the NavMesh tile borders
Reproduced in: 2018.2.21f1, 2018.4.1f1, 2019.1.4f1, 2019.2.0b3, 2019.3.0a4
Note: changing the positions of obstacles will yield different results (correct / incorrect) which depend on their positioning
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
- Inconsistent help box font size in Project Settings window
- Local package MonoBehaviour scripts appear as missing after updating the project when the project and package paths share the same prefix
- AssetBundle Variants do not switch when a Sprite (2D and UI) texture is referenced from a Material
- Location tooltip in the Viewport of UI Builder window does not update when the UI Document Asset is moved to a different location
- Audio Clip Volume and Avoid Repeating Last fields values cannot be changed in Audio Random Container window
Resolution Note (fix version 2020.1):
Additional proposed workaround fairly easy to achieve for when the disconnected polygon edge is not on the tile border:
When two obstacles tend to align their edges with one another the user can try and very slightly offset or rotate one of them in order to avoid creating an edge between the obstacles that aligns perfectly with them both. (That edge leads to imprecise calculations later in the algorithm.)