Addressable system and sprite atlas

Hi, I was wondering if sprite atlases are supported by the new addressable system.
For what I see from the profiler all the atlases are loaded into memory cause referenced from “CachedSpriteAtlasRuntimeData”.
So even if all the texture in the atlas are not referenced from game objects the atlas seem to be loaded anyway, along with a the non-packed version of each image (making in fact the memory footprint bigger).
I have then two questions:

  1. Is there a way to lazy load an atlas in memory?
  2. why do I see in the profilers entries for both the atlas page and the separate version of the same image (actually adding up to a bigger memory footprint?)
4 Likes

still no answers?

EDIT: I also see all my Addressable atlases referenced in memory when I was playing in Editor. But when I build for Android and check on my device profiler, none of the atlases was unnecessary referenced by that CachedSpriteAtlasRuntimeData. It only loads when I want to and unload and remove reference correctly

1 Like