You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Removing these extra tiles should be a low-hanging fruit for improving performance, though it may require a more involved collision detection algorithm than the axis-aligned-bounding-box approach introduced in #11508.
On the other hand, it's possible that including these extra tiles in the cache could improve performance on subsequent panning. (Though even if this was included as a feature, they should not cause additional draw calls).
As pointed out by @ansis in #11917 (comment)
Steps to Trigger Behavior
Logging the tiles, we can see that tiles columns 2 and 5 are included, which are to the right and left of the visible screen:
This issue also occurs with raster tiles and can be tested with:
Removing these extra tiles should be a low-hanging fruit for improving performance, though it may require a more involved collision detection algorithm than the axis-aligned-bounding-box approach introduced in #11508.
On the other hand, it's possible that including these extra tiles in the cache could improve performance on subsequent panning. (Though even if this was included as a feature, they should not cause additional draw calls).
cc @ansis @akoylasar
The text was updated successfully, but these errors were encountered: