A fast, easy to use, free, and community supported 2D game engine
how would impact having different atlas sprite managers for the same texture? I'm thinking of having one texture for the tiles (using TMX support), that would mean that every layer is one AtlasSpriteManager and one shared manager for every object in the level that has an atlasSprite.
So, for instance if I have 5 layers, two tilesheets and 50 objects (all of which share a common atlas sprite manager), would that be too expensive in terms of memory?
thanks!
From what I understand of the code base, the memory impact from the texture should be nil. When you create an AtlasSpriteManager from a texture, it checks to see if the texture has already been loaded so you won't get multiple copies of the texture. So your primary additional overhead from this approach should just be the extra layer of the manager.
At least that's how I read the code browsing over it. =)
bradparks
Member
From my understanding, it'd still have an effect on performance though.... Though how big an effect it would be, I can't say...
Each AtlasSpriteManager batches openGL calls, so drawing 100 sprites results in 1 big batched OpenGL call, as opposed to 100 separate openGL calls.
So having 3 AtlasSpriteManager's that used the same texture would still result in 3 batched open GL calls. If you did it all with one, then you'd only have one big batched openGL call, which I think would be faster...
This post from last week kind of discusses this...
http://www.cocos2d-iphone.org/forum/topic/2861#post-17954
So memory wise, I think it's nil effect, as @exorcyze said... but I think there's still a performance hit to some extent...
Brad
You must log in to post.
