SpriteSheets and sprite dimensions

cocos2d for iPhone » Programming » cocos2d support (graphics engine)

SpriteSheets and sprite dimensions

(6 posts) (3 voices)

Started 2 years ago by SonnyBurnette
Latest reply from jd

Tags:

SonnyBurnette
Member

I think I mostly get this but wanted to confirm before I start moving to this functionality.

If I have an animation consisting of 10 50X50 cells and another animation consisting of 10 30x30 cells both of those can be put on to the same spritesheet correct? All of the cells in the spritesheet do not have to be the same size right? Do the cells within the same animation have to be the same size? Can the second animation's cell be on the first row of the spritesheet behind the cells for the first animation and then carry over to the second horizontal row?

I keep reading about the benefits of spritesheets but was unsure of how I need to chunk out the cells on the spritesheet. Getting different sized cells all evenly spaced has been tricky for me.

Posted 2 years ago #
Joao Caxaria
Member

<quote>If I have an animation consisting of 10 50X50 cells and another animation consisting of 10 30x30 cells both of those can be put on to the same spritesheet correct?</quote>
Correct.
<quote>
All of the cells in the spritesheet do not have to be the same size right?
</quote>
Right.
<quote>
Do the cells within the same animation have to be the same size?
</quote>
I think so. I think there's a workaround for that limitation but I wouldn't bother..
<quote>
Can the second animation's cell be on the first row of the spritesheet behind the cells for the first animation and then carry over to the second horizontal row?
</quote>
Sure.

Posted 2 years ago #
Joao Caxaria
Member

Well, sorry for the badly formatted post.. :P can't edit it.. :) it was a nice try..

Posted 2 years ago #
SonnyBurnette
Member

Ok and now the follow up.

I see that I can load my png image like so (simplified):

AtlasSpriteManager spriteManagerWithFile:@"myimage.png"

or I have seen it loaded like so:

Texture2D *myTexture = [[TextureMgr sharedTextureMgr] addImage:@"myimage.png"];

then referenced like:

[[AtlasSpriteManager alloc] initWithTexture:myTexture capacity:25];

What is the difference or better yet what is the benefit of loading your image as a texture2d instead of directly into AtlasSpriteManager? Do this allow me to put all of my images in 1 texture somewhere then have separate AtlasSpriteManagers all reference that 1 image in memory? Is it indeed only in memory once? If I were to use the first method and load the png directly into AtlasSpriteManager that would cause me to load the image again if I needed another sprite cell for another class, correct?

Lastly, what does the capacity reference? Is it how many total cells are contained in the png image or how many are to be used in the animation(s) or how many are in the horizontal row?

Sorry if these are noobie questions but I kind of want to know how all of this fits together.

Thanks!

Posted 2 years ago #
Joao Caxaria
Member

What is the difference or better yet what is the benefit of loading your image as a texture2d instead of directly into AtlasSpriteManager?

I think it's the same.. but if you take a look at the code, it's all there..

It's only in memory once, no mather what. And it does not load the image again if you need another sprite cell.

The capacity should be the initial size for the children... but, again, check the source code, it should clear it all up for you.

Posted 2 years ago #
jd
Member

I read that it's sort of expensive if you set capacity too low and then use more than you specified. It will expand automatically but that's the expensive part. So...overestimate if you aren't sure.

Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.