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
- Error "Objects are trying to be loaded during a domain backup. This is not allowed as it will lead to undefined behaviour!" when entering Play Mode with the PBR Sky Shader Graph created in Project
- Custom Property and Function Labels at the top of the Graph Inspector go out of bounds and are not truncated when String is long
- Warning "Full dialog message:" is logged when the project is upgraded to a newer version
- A 404 page is opened when selecting "Open Documentation" for any of the HDRP specific Input Nodes in Shader Graph
- A 404 page is opened when selecting "Open Documentation" on the URP Sample Buffer Node in Shader Graph
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.)