I don't know if internally you guys have some normal approach for this kind of access? Danger here being that load needs to be called (I'm not a fan of non-RAII patterns, which this kind of would be).Alternatively, Load function on the Atlas class, Atlas.LoadAsync/Sync().Either it gets loaded by the first sprite instance that references/uses it, or at this point. GetSpritesFromAtlas() could internally load if it's not already loaded in the scene.An alternative is to manually list all sprites in an array on an object somewhere, but to be honest this will be painful to maintain as the number of swords grows/shrinks etc.Īs most texture atlas' come with a seperate descriptor to list all the items it holds, I would assume some similar internal representation exists for Unity SpritePacker Texture that maybe isn't exposed? This relies on being able enumerate the Sprites contained within the SpritePacker generated texture, which I can't find a way to do. Make a new UI rect for each sprite to display in the UI

For all sword sprites in Texture Atlas (normally represented by some UV array?) create all sprites by enumerating and iterating over them Get SpritePacker TextureAtlas of swords 'unity_spritepacker_generated_swords.png' I want to increase the number of swords in this atlas, potentially an infinite amount (of course not really infinite, but it might be 10, might be 100).Īt runtime when I show this sword selection menu, what I really want to happen is the following pseudo code:

I have a bunch of swords (sprite images) that I pack into an Atlas for both memory and runtime performance (batching a sword selection menu). By Atlas I mean, the Texture SpritePacker generates upon building. Click to expand.So perhaps 'atlas' isn't quite the right terminology.

Unity assets bundle extractor sprite