A fast, easy to use, free, and community supported 2D game engine
Nicke
Member
Hey everyone.
I've run into an issue where I want to move around a bunch of my atlassprites independent of some of the other sprites belonging to that particular atlasspritemanager. Now, my question is as follows:
If I have two or more atlasspritemanagers created from the SAME sprite sheet, will memory usage double/triple or will the sprite sheet only be loaded once into memory and all the atlasspritemanagers will just reference the same piece of memory?
Thanks,
Nicke
As far as I know, all textures are cached by default and reused if you reference the same file again. This applies to Sprites and Atlas Sprites (& should work the same for anything else using the texture manager).
Obviously the more AtlasSpriteManagers you have, the more OpenGL calls are made, but I had to do the same to get parallax working on a large background sprite sheet. 5 different managers for the same 1024x1024 png, it ran much better than separate smaller sprites still.
Nicke
Member
Ugh, ran into an issue. I've been "repeating" my grass background.png, and when I had it as a Sprite it worked very well. Now with AtlasSprites I get a "border" effect between the two AtlasSprites:
bg.png in this example is 1024 pixels wide.
Before (no "border effect"):
Sprite *blabla1 = [Sprite SpriteWithFile:@"bg.png]
Sprite *blabla2 = [Sprite SpriteWithFile:@"bg.png]
blabla1.position = ccp(0, 0);
blabla2.position = ccp(1023, 0)
Now (You see a vertical line between the two AtlasSprites):
AtlasSprite * blabla1 = [AtlasSprite spriteWithRect:CGRectMake(x, y, w, h) spriteManager:backgroundNode];
blabla1.position = ccp(0, 0)];
AtlasSprite * blabla2 = [AtlasSprite spriteWithRect:CGRectMake(x, y, w, h) spriteManager:backgroundNode];
blabla2.position = ccp(1023, 0)];
I tried setting blabla2's position to a lower value, like 1020 or 1000 but the problem still persisted. I also tried changing the z-order, but to no avail. I'm hoping I'm not the first to encounter this issue. Grateful for any advice,
Nicke.
You must log in to post.
