jannem, 1 month ago

@SirLich
I kind of understand the reasoning that can lead to this issue.

As a workaround you could try add a polygon (disk) at your destination and path to that. I guess that might make it find the correct solution.

Edit: probably not. It'll still route through the large blue polygon first. If you split the polygon vertically into two it will likely work.

SirLich, 1 month ago

@jannem Yeah this "splitting" idea is nice. I didn't find any way to augment the navigation baking, or any settings related to max cell size.

I suppose I can manually change the data in the NavigationArea2D after baking? I don't actually know if those fields are even exposed to GDScript. Probably they are.

SirLich, 1 month ago

If you focus on the polygon where the path ends (top right), you can indeed see that to ENTER this polygon, the shortest path is on the left.

But to reach the actual terminus, it would be shorter to go straight, not make a curve around the obstacle.