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
- UI Toolkit Slider value defaults to min value when the initial value is set in the UXML file
- The Player hangs when unloading a scene using the UnloadUnusedAssets() method
- [iOS] Too many texture parameters error is thrown when running on devices that support the number of parameters
- [MacOS] Trying to pick a Colour from full-screen window breaks Colour Picker Tool functionality
- WebGL Player hangs on first frame when "Autoconnect Profiler" is enabled and large amount of Profiler data is buffered before the first frame
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.)