I found that when I increased the size of PathFinder, 1x1 cells on a certain line no longer generated pathfinding, as shown in the figure below. This is very abnormal. I can alleviate this issue by adjusting parameters such as tileSize or MaxEdge Error. However, I am not clear about the underlying principle, and this will bring a lot of uncertainty to the game.
Is it specifically everything in that red square stop working with pathfinding?
Yes, the z-coordinates of all the tiles that are not working are the same, and I found that they are precisely at the boundary of the TileSize. My tileSize is set to 128, which corresponds to 12.8 meters, and I suspect it has something to do with the 0.8 in the decimal.
Try turning on the gizmos to check the connections between the nodes? That may shed some more light on this.
That said, if you are able to at least test it, I’d reccomend seeing if this behaviour still exists in the latest version, just to see if it’s already addressed? I’m reading through the patchnotes and even on the 5.0 update, the next update after your version, it says:
- Reduced likelyhood of gaps being generated between tiles in recast graphs. This will reduce the precision of the navmesh a bit on the y-axis along tile edges, but agents should be able to navigate better (and it will look better).
Whether this is your specific issue not sure though. Maybe we’ll find out more from viewing the connections.
