cocos2d for iPhone

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

1. 

   riq
   Key Master

   Hi,

   v0.9.0-alpha is available for download:
   http://cocos2d-iphone.googlecode.com/files/cocos2d-iphone-0.9.0-alpha.tar.gz

   Highlights:
   - CC namespace
   - Sprite/Atlas sprite merge
   - Zwoptex support

   Changelog:
   http://cocos2d-iphone.googlecode.com/svn/tags/release-0.9.0-alpha/CHANGELOG

   Release Notes:
   http://www.cocos2d-iphone.org/wiki/doku.php/release_notes:0_9_0_alpha

   How to migrate to v0.9:
   http://www.cocos2d-iphone.org/wiki/doku.php/prog_guide:migrating_to_0_9

   What does "alpha" mean ?
   - it means that it is more volatile than "beta"
   - API might change, in fact, it will change a little bit
   - It wasn't tested as much as a final version

   I would appreciate your feedback, specially feedback regarding:
   - CC namespace
   - Sprite / AtlasSprite merge
   - Animation

   Don't be shy regarding the feedback. If you don't like something about the API, let us know. The v0.9.x series will be our last opportunity to introduce important API modifications. The v1.x series will be backward compatible.

   Thanks,

   Posted 4 months ago #
2. 

   rolando
   Moderator

   awesome! as usual, excellent work riq!

   Posted 4 months ago #
3. 

   QcMat
   Member

   I'll convert my newest project to 0.9. Thanks for the great and fast work!

   Posted 4 months ago #
4. 

   mmilo
   Member

   Thank riq! Good stuff. :)

   Posted 4 months ago #
5. 

   MikeSz
   Member

   great to see it :) doesn't even require that much effort to move from 0.8.2 to 0.9 :)

   however, it seems there is something missing in the CCSprite, CCSpriteSheet, CCSpriteFrameCache affair, or Im just unable to find it ?

   creating a CCSprite that uses CCSpriteSheet simply requires a bit too much of work (yes, I'm lazy :P but as I often say, laziness is the mother of invention)

   1) create CCSprite using CCSpriteFrameCache
   2) add CCSprite to CCSpriteSheet

   so code looks like this:
   

   CCSprite * spr = [[CCSpriteFrameCache sharedSpriteFrameCache] createSpriteWithFrameName:@"some_name.png"];
   [mySpriteSheet addChild:spr];

   I feel that it can be very simply organized into one helper function that takes a CCSpriteSheet and NSString as arguments and returns a CCSprite. like this:

   -(CCSprite*) addSpriteWithName:(NSString *) spriteName toSpriteSheet:(CCSpriteSheet*) spriteSheet
   {
   	return [self addSpriteWithName:spriteName toSpriteSheet:spriteSheet withZ:0];
   }
   
   -(CCSprite*) addSpriteWithName:(NSString *) spriteName toSpriteSheet:(CCSpriteSheet*) spriteSheet withZ:(int) zVal;
   {
   	CCSprite * tempSprite = [[CCSpriteFrameCache sharedSpriteFrameCache] createSpriteWithFrameName:spriteName];
   	[spriteSheet addChild:tempSprite z:zVal];
   	return tempSprite;
   }

   with an example function call:
   

   CCSprite * spr = [self addSpriteWithName:@"some_name.png" toSpriteSheet:mySpriteSheet];
   // or
   CCSprite * spr = [self addSpriteWithName:@"some_name.png" toSpriteSheet:mySpriteSheet withZ:10];

   what do you think ?

   Posted 4 months ago #
6. 

   MikeSz
   Member

   ok, another thing:

   in cocos 0.8.2 there was something called MenuItemAtlasSprite, which could accept AtlasSprites

   however, 0.9.0 alpha only has CCMenuItemSprite which seemingly does not want to accept CCSprites that are children of the CCSpriteSheet

   I receive "'CCSprite can't be dirty when it's parent is not an CCSpriteSheet'" error when trying to do it

   obviously it's caused by drawing it twice, once by spritesheet and once by the menu

   ---

   I have made a temporary fix - CCMenuItemSpriteWithSpriteSheet that works quite ok, but is not influenced by calling setPosition on its CCMenu parent. can provide it if needed, but it is just a straight copy of the MenuItemAtlasSprite

   Posted 4 months ago #
7. 

   riq
   Key Master

   @mikesz:
   to create an sprite that uses an sprite sheet you can use:

   CCSpriteSheet *sheet = [CCSpriteSheet spriteSheetWithTexture:texture];
   CCSprite *sprite = [sheet createSpriteWithRect:CGRectMake(0,0,20,20)];

   or are talking about another use case ?

   Regarding MenuItemAtlasSprite, yes, it was removed from v0.9 because:
   - In v0.9 CCSprites supports rects
   - MenuItemAtlasSprite was a hack. You needed to add the items in 2 different places and it wasn't obvious at all
   - Usually you don't need a lot of performance to display a menu. If you have 20 items, the performance between MenuItemAtlasSprite and MenuItemSprite should be more or less equal

   I've just updated the release notes explaining this.

   Posted 4 months ago #
8. 

   MikeSz
   Member

   @ riq

   regarding CCSprite creation for CCSpriteSheet - I was talking about a situation when you use coords provided by the CCSpriteFrameCache. I have not been able to find a single method that allows for it. you always have to create a CCSprite using the CCSpriteFrameCache and then add it to the CCSpriteSheet. I think it would be a bit faster if there was a method like I proposed, which accepts the texture name and spritesheet to which it should be added and does it all for you. but as I said - it's just being a bit lazy and anyone can write such helper function in a matter of seconds

   actually my current function call is just [TL add:"filename.png" to:"sprite_sheet"]; // optionally - withZ:0];

   just makes it a bit faster and shorter. but that's just me being lazy as I said

   ---

   regarding MenuItems - I know that the MenuItemAtlasSprite was a hack, but it was a useful hack anyway ;)

   and it was not about performance at all, but about amount of images that you need to add to the project (and load at runtime). with AtlasSprite support you were able to have all of it in one .png file, now it has to (or at least I assume there is no other direct way) be held in a multitude of texture files. so while performance doesn't suffer, loading time and "cleanliness" of the resources do suffer a bit

   Posted 4 months ago #
9. 

   riq
   Key Master

   @mikesz:
   in v0.9, AtlasSprite andSprite were merged, and now CCSprite supports sub-rects.
   With one texture you can have different sprites whether or not you use an CCSpriteSheet as a parent.

   See the MenuTest.m to see how to a texture atlas in the menus.

   Posted 4 months ago #
10. 

    MikeSz
    Member

    ok, I see now. so to achieve it I should:

    1) create a CCSpriteFrameCache for the .plist file

    2) get the CCSpriteFrame from the CCSpriteFrameCache with -(CCSpriteFrame*) spriteFrameByName:(NSString*)name;

    3) use rect of this CCSpriteFrame to create CCSprite

    4) add this to the CCMenuItemSprite

    seems to work for me, thanks :)

    [[CCSpriteFrameCache sharedSpriteFrameCache] addSpriteFramesWithFile:@"animations/grossini.plist"];
    
    NSString * spriteSheetFile = @"gui.png";
    CCSpriteSheet * imgMgr = [CCSpriteSheet spriteSheetWithFile:@"gui.png"];
    
    NSString * frameName = @"grossini_dance_%02d.png";
    CCSpriteFrame *frame = [[CCSpriteFrameCache sharedSpriteFrameCache] spriteFrameByName:frameName];
    
    CCSprite *spriteNormal = [CCSprite spriteWithFile:spriteSheetFile rect:frame.rect];
    CCSprite *spriteSelected = [CCSprite spriteWithFile:spriteSheetFile rect:frame.rect];
    CCSprite *spriteDisabled = [CCSprite spriteWithFile:spriteSheetFile rect:frame.rect];
    
    CCMenuItemSprite *item1 = [CCMenuItemSprite itemFromNormalSprite:spriteNormal selectedSprite:spriteSelected disabledSprite:spriteDisabled target:self selector:@selector(menuCallback:)];

    Posted 4 months ago #
11. 

    riq
    Key Master

    Yes. The use of CCSpriteFrameCache is optional, but it facilitates the creation.

    Take a look at the CCSprite API:
    http://www.cocos2d-iphone.org/api-ref/0.9.0-alpha/interface_c_c_sprite.html

    You will see the different ways to create an sprite.

    Posted 4 months ago #
12. 

    paulhart
    Member

    I just posted my experience with the 0.8.2 to 0.9.0-alpha upgrade on my blog. Was pretty simple.

    Posted 4 months ago #
13. 

    riq
    Key Master

    @paulhart: cool. Feel free to add a link to your post in the wiki page, in the section that says: "add your experience here"

    Posted 4 months ago #
14. 

    MikeSz
    Member

    I actually managed to port it in a matter of hour without even using CC_COMPATABILITY_WITH_0_8 flag ;)

    my biggest problem was actually not with Cocos2d but with new Box2D and the b2_dynamicBody flag that needs to be added to the body definition if it is to move...

    other than that - smooth as butter really

    actually this is one of the best things about cocos2d - switching to newer versions requires really little work

    Posted 4 months ago #
15. 

    greyhoundgames
    Member

    I don't know if this is because I am doing something wrong, but when creating a CCSprite from a file directly, I am able to visit it to cause it to render on a RendereSurface. However that same sprite created from a sprite sheet(though not added to it) does not appear to render (all other things being the same with the previous scenario). In both cases there was no parent object.
    Any ideas?

    Posted 3 months ago #
16. 

    DonomaGames
    Member

    Hi Riq,

    I upgraded to the trunk from 8.2 and noticed that this line in CCSprite.m in the setDisplayFrame method is giving me a problem.

    anchorPoint_ = ccp( (- frame.offset.x / frame.rect.size.width) + 0.5f,
    					   ( - frame.offset.y / frame.rect.size.height) + 0.5f );

    It's basically updating the anchor point for every frame and overriding the anchor point that I've set for the sprite. So when not animated, my sprite is positioned correctly. But as soon as it starts animating, the sprite is now off centered. I know the anchor point has to be set b/c each frame could have a different offset, but is this a bug or is there another way to make the animation respect the original anchor point?

    thanks

    [edit]
    I am using a spritesheet where the offset is none 0.

    Posted 3 months ago #
17. 

    riq
    Key Master

    @donomaGames: So, it worked OK with v0.8.2 ? but after upgrading it's not working as expected, right ?

    Could you open an issue, and if possible, with the code and the images to reproduce it ? thanks

    Posted 3 months ago #
18. 

    DonomaGames
    Member

    Thanks for the quick reply. Actually I think this might be a new issue. 8.2 didn't support zwoptex natively and I didn't use zwoptex in 8.2. I didn't specify that clearly in my original post.

    I'll see if I can put together some sample code to demonstrate.

    Posted 3 months ago #
19. 

    riq
    Key Master

    @DonomaGames: yes, a sample code will help a lot. thanks.

    Posted 3 months ago #
20. 

    slipster216
    Moderator

    @DonomaGames:

    This might be because the new format supports the zwopple offsets automatically. You don't need to update the anchor point for each frame of the animation anymore; the offsets stored in the new sprite system do that for you automatically.

    Posted 3 months ago #
21. 

    DonomaGames
    Member

    @slipster216

    Yes I know. But it's overriding my anchor point. I set all my sprites to ccp(1.0, 1.0) and it's resetting it every frame to ccp(0.5+offsetX, 0.5+offsetY).

    Posted 3 months ago #
22. 

    greyhoundgames
    Member

    Trying out the new atlas sprites can be children of other atlas sprites from the trunk(downloaded dec 1st) I encountered the following. Perhaps I am just not doing this right but anyhow.

    I alloc an instance of my custom subclass of CCSprite but I do not init it. I then call [spriteSheet initSprite:mySprite rect:CGRectMake(0,0,0,0)]; I used a size 0 rect because I wanted this guy to only represent position for the child\parent hierachy but not render. But I wanted him to be an sprite on the spritesheet so I could get the batch rendering still

    It then gets added to the sprite sheet as a child(the sprite sheet is added to the scene).
    Then shortly after that I add a child doing the same thing as before but using a actual rect to some image on my sheet. I then add that child to my first node.

    When I do this I get an issue because the imageIndex it computes for my sprite is like 412123213123 and this blows up on an assert.

    Did I miss something on how this works?

    Posted 3 months ago #
23. 

    riq
    Key Master

    @greyhoundgames: Could you post the code to reproduce it ?

    @DonomaGames: Yes, it's bug. I'm working on it. SVN r1585 contains an improvement but it is not 100% fixed yet. I've been working on this bug all the day, but today it wasn't a very productive day for me :-(

    Posted 3 months ago #
24. 

    greyhoundgames
    Member

    I believe this is all the relevant code. I did some debugging and I determined that its because I am adding children before the parent is added to the sprite sheet. Is this expected? Should we be able to prebuild our entire node(with children) before adding it? Anyhow adding first then doing this made it come back with a 0 for the index

    //Scene Node init relevant parts
    CCSpriteSheet* thingsSpriteSheet=[CCSpriteSheet spriteSheetWithFile:@"unit_sheet_real.png" capacity:1];
    [self addChild:thingsSpriteSheet z:THINGS_Z tag:ThingsSpriteSheet];

    //Then later when I actually want to add the units to the screen
    CCSpriteSheet *thingsSpriteSheet = (CCSpriteSheet*) [self getChildByTag:ThingsSpriteSheet];
    UnitNode *newUnit=[[UnitNode alloc] autorelease];//no init, init happens on next line
    [thingsSpriteSheet initSprite:newUnit rect:CGRectMake(0,0,0,0)];
    [newUnit setEnemy:enemy];
    enemy->unitRenderer=newUnit;
    [thingsSpriteSheet addChild:newUnit z:BASE_ENEMY_Z+[newUnit calculateZ]];

    //And then shortly after that, the following happens. This is where it has the assert error, trying to add the children nodes

    -(void)addBodyParts
    {
    AnimatedSequenceChildNode* temp=[self setupAnimatedSequenceChildNodeWithRect:CGRectMake(0,0,10,10)];
    [self addChild:temp z:1 tag:NodeType_Leg];
    [temp addChild:[self setupAnimatedSequenceChildNodeWithRect:CGRectMake(0,0,15,15)] z:2 tag:NodeType_Foot];
    }

    //helper function
    -(AnimatedSequenceChildNode*)setupAnimatedSequenceChildNodeWithRect:(CGRect)rect
    {
    AnimatedSequenceChildNode *child=[[AnimatedSequenceChildNode alloc] autorelease];//no init, init happens on next line
    [self.spriteSheet initSprite:child rect:rect];
    return child;
    }

    Posted 3 months ago #
25. 

    greyhoundgames
    Member

    Now that I got around that problem I noticed that the z Order of children that is set is not respected. Pos or neg the child appears to always be drawn behind the parent. Looking at the code, the first child of a ccsprite is given its parent's atlas index with the z passed in value ignored. But I also see that you are reording them when the actuall addCHild happens so that may be ok. Based on how I think this is working, the atlas is containing basically a big sorted list of sprites based on render order.

    Posted 3 months ago #
26. 

    riq
    Key Master

    @greyhoundgames: Could you reproduce it with the latest SVN revision ?
    If so, could you open an issue ? Thanks.

    Posted 3 months ago #
27. 

    badawe
    Member

    @riq seens the anchorpoint for ccsprite now works diferent? Right? i try make one test with box2d and new 0.9alpha cocos2d, and i can change the anchorpoint of one CCSprite! =/

    Posted 3 months ago #
28. 

    riq
    Key Master

    @badawe: Sorry, I don't understand the problem. Could you explain it further ? Thanks.

    Posted 3 months ago #
29. 

    badawe
    Member

    @riq sorry! Its my bad! i using zwoptex and when i try change the anchor point, i get the problem because offset zwoptex applies, but just untrinn the images, and everything work again.

    Maybe the anchor point in someway count the xoffset and yoffset to the calculations? This will be very nice!

    Posted 3 months ago #
30. 

    riq
    Key Master

    @badawe:
    Yes, anchorPoint with Zwoptex is still not working OK when the anchorPoint is not 0.5:
    http://code.google.com/p/cocos2d-iphone/issues/detail?id=653

    Posted 3 months ago #

RSS feed for this topic

Reply »

You must log in to post.