cocos2d for iPhone

A fast, easy to use, free, and community supported 2D game engine

1. 

   alexgames
   Member

   Hi,

   I decided to use one texture atlas for all of my sprites.
   Should I use single AtlasManager for it?
   I guess it will take less memory. Or no?

   For example, I have layers:

   RootLayer (AtlasManager)

   Layer1
   --- layer2
   --- layer3

   Layer4
   ---Layer5

   Each layer contains sprites, I can create AtlasManager in RootLayer and share its pointer to all other layers,
   but all the sprites will be attached to RootLayer.

   Otherwise I should create AtlasManager in each Layer,
   five managers at all (or maybe much more).

   RootLayer (AtlasManager)

   Layer1 (AtlasManager)
   --- layer2 (AtlasManager)
   --- layer3 (AtlasManager)

   Layer4 (AtlasManager)
   ---Layer5 (AtlasManager)

   I worry about memory usage…

   Thanks.

   Posted 2 years ago #
2. 

   Clain
   Member

   One AtlasSpriteManager (ASMgr) in each Layer is the way to go. The ASM's texture is handled by the TextureMgr : it will only be loaded once and be shared with all your ASMgr.

   Posted 2 years ago #
3. 

   dalplatinum
   Member

   I'm very new to both Obj-C and cocos2D, and I have a similar query.

   I have converted all the sprites on my menu to atlassprites with their own manager. This works very nicely.

   But when it comes to the game, it is laid out in a rather tricky pattern.

   GameBoard Layer (AtlasManager)
   -- Row1 CocosNode (AtlasManager)
   -----Item1 CocosNode (1 sprite)
   -----Item2 CocosNode (1 sprite)
   -----Item3 CocosNode (1 sprite)
   -----Item4 ... etc.
   -- Row2
   -----Item1 etc.
   ...

   There are 12 rows and 13 items per row, for a total of 150+ sprites. Possibly doubling, depending on how I put the FX in.

   So in this case, I would like to send the sprites to the AtlasManager for its parent row.

   But I don't know how.

   I've tried: (from going through the classes and samples)

   AtlasSpriteManager *mgr = (AtlasSpriteManager*) [parent getChildByTag:kTagSpriteManager];

   But I get nothing. This might be just my lack of C knowledge (I'm used to ActionScript), of course.

   Also, would it be better (performance-wise) to send them all even further up the tree to the GameBoard object? I see from your comment that I can have as many managers as I want, and they will all share the same atlas, so that's not a problem, but is there a speed penalty for using twelve managers over just one?

   Posted 2 years ago #
4. 

   Clain
   Member

   First, you can't have an ASMgr as a child of another ASMgr. So this :

   GameBoard Layer (AtlasManager)
   -- Row1 CocosNode (AtlasManager)

   is not good.

   To move an AtlasSprite from one ASMgr to another, you should read this thread : http://www.cocos2d-iphone.org/forum/topic/1221
   (especially riq's answer)

   Performance-wise, yes, it's better to have one ASMgr instead of 12. But I don't think you'd see any difference. Maybe if you had 50 or more... Never tried though so it's just guessing.

   Posted 2 years ago #
5. 

   dalplatinum
   Member

   Having spent a couple of hours with my nose in Google, I found a way to do it. I think part of the problem is the terminology I picked up with ActionScript.

   Obj-C: Parent = superclass
   AS: Parent = container

   My way of getting around it was to change the inits on the items.
   Now I am initialising objects using

   Container:
   CoreNode *comp = [[CoreNode alloc] initWithPapa:self];

   CoreNode:
   - (id) initWithPapa: (Rail *) papa;

   Now I can use (in CoreNode):
   [papa stuff] = things

   I'm guessing this is common knowledge for anyone with obj-C experience. But if I had to hunt the answer down, so will someone else.

   I've been through my obj-C books, and none of them mentioned this. Most likely because there's a better way of doing it ;)

   While I'm here, I'd like to express how impressed I am with this framework. It's made creating my game a far less daunting task. I'm not sure I have the mental capacity to learn obj-C and OpenGL at the same time.

   Posted 2 years ago #
6. 

   dalplatinum
   Member

   I was typing while you were replying, Clain.

   I think I probably worded the original query badly. I'm not actually moving between managers. I'm creating them directly on a single manager.

   The way I have it set up now is that the Gameboard layer has it's own AtlasManager for drawing the board. The Row objects have an AtlasManager for drawing their children.

   When the children are created, they create sprites directly into the AtlasManager in the containing Row.

   Again, this is probably less than ideal (it may not even make sense). Hopefully, by the time I get closer to finishing, I will have learnt enough to do it properly. But I've only been at this for 10 days.

   I had a look at that link, and it is good to know, but because barely anything I have will need to move between managers, it's not entirely applicable. Although there is another game on my idea list that could use it.

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.