Overlay's textures size

[Krixtalx]

Is there a way to explicitly define the texture dimensions for tiles?

I understand that raster overlays provide an option for specifying the maximum texture size, but this appears to affect only level-of-detail selection. In my tests, the generated overlay textures have dimensions such as 64×Y and 128×Y pixels, with the value of Y varying considerably.

In light of issue #1263, I had assumed that provider textures would be standardized:

With a “Maximum Texture Size” of 2048, it will often happen that loading raster overlays for a single geometry can require 64 256×256-pixel Bing tiles.

Is it possible to configure or enforce consistent texture dimensions for raster overlay tiles?

[j9liu]

Hi @Krixtalx!

I'm afraid we don't have support this at the moment, but we can treat this issue as a feature request! Do you have any additional details or context for your use case we should know about?

[Krixtalx]

The main use case (for us) would be storing overlay textures in a texture array instead of allocating one texture per tile, which would otherwise require a resource set update for each draw.

A texture atlas can solve the same problem, but with more complexity: it needs allocation logic and border padding to preserve correct filtering. Another alternative would be an array of textures, but this is not a good fit because of coverage.

In Evergine’s Cesium integration, we're already using a texture atlas, so we no longer need this feature directly. Still, I think it would be a useful addition, even for integrations that already use an atlas.