Introduction:
What would happen if what people share on Twitter turns real? And best of all, if you could play with that? Welcome to the first game that turns tweets into reality. Get ready to jump into your race-car, drive on Route 140 and live the most innovative adventure of the moment, escape from tsunamis, zombies, meteorites, motorcycle gangs, and many more events that are really happening on this precise moment.

But, you are not alone!
You will also be able to defend yourself with powerful weapons and cool events that will get you out of trouble and let you arrive safely to your destination. All of the events will be generated by people around the world that will create a new experience every time you play!

Why developers will find my game interesting:
Very interesting way to create events based on real tweets.

Why gamers will find my game interesting:
It uses real life tweets to schedule content, so it's pretty cool when you can see social networking being used as an input to a game.

Screenshots:

Tweet Land Trailer:
http://www.youtube.com/watch?v=6PXibEMngTM

You can read more about Tweet Land here:
http://www.tweetlandgame.com

Development: Tree Interactive

Publishing: Why Ideas

You can download Tweet Land from iTunes here:
http://itunes.apple.com/app/tweet-land/id491102570?mt=8

Please write an honest review on the app store and report directly back here about any bugs.

I've been implementing a File > Save/Open menu into my Cocos2d-MAC iPhone game level editor.

I created a class called 'SaveController' of which I created an instance variable in my 'HelloWorldScene'

SaveController* saveController;

.m init method -

blocks = [NSMutableArray arrayWithCapacity:60];
[blocks retain];

saveController = [[[SaveController alloc] initWithBlocks:blocks] autorelease];
[saveController retain];

'blocks' is supposedly a pointer to the NSMutableArray that stores the level editor 'block' (tile) data.

NSMutableArray* blocks;

So I instantiate 'saveController' with a pointer to the array, and make sure it is retained. (and released is dealloc).

Inside the SaveController .m :

-(id)initWithBlocks:(NSMutableArray *)b{
if ( (self = [super init]) ) {
blocks = b;
[blocks retain];
}
return self;}

In another method of the save controller, the one that responds to the NSSavePanel, there is a method I wrote to parse the data into JSON:

for (int i = 0;i < [blocks count];i++) {
MovableBlock* block = [blocks objectAtIndex:i];
... }

Despite the array of objects 'blocks' in HelloWorldLayer being full (e.g. 27 objects), when I access them through this loop the array is always blank.

Any clues as to what is going on?

In my game now I have plenty of CCLabelTTF's. Names of labels point to it in my header file, and that design makes sense to me. I'm at a point now where I sometimes have a menu display over the paused game, and it will have x amount of labels. There may up to 40-50 of them, who knows. I'm not really sure how to proceed with this in the most organized way, but I'm confused whether or not CCLabelTTF's could ever be temporary and then all be released when that menu goes away. The way I handle getting rid of the labels now is just setting the string to a space " " which I know is probably really ghetto and not the proper procedure. Furthermore, those labels still exist. I know they don't take up a lot of resources, but if I'm going to have an upward of 200 of them or more (not all displaying all at once of course), I don't just want them hanging around.

Hi there, I have made a hud layer.
In my action layer I make reference to the hud layer...

HudLayer *hud;
}
@property (nonatomic, retain) HudLayer *hud;

Everything seems to work perfectly.

The problem is that when I look in dealloc of my actonLayer.mm it says "on "dealloc" you need to release all your retained objects" I then notice that I have retained hud.

I have tried adding self.hud = nil; and [hud release]; into the actionLayer dealloc.... but the app crashes with both of these.

I have added a checker of CCLOG(@"dealloc:%@", self); in my dealloc which does get called when I exit actionLayer.

Just wondered... do I need to release hud, or is there a way to not retain it??

sorry if the solution is obvious, I'm not too experienced with this.
thanks
moomy

hey guys
so we made this awesome game during the global game jam this weekend with kobold2d for mac which is sort of a wrapper for cocos2d.

video of our game here: http://vimeo.com/35831115

it works great on our computers.
2x - works from ide and release - lion
1x - works from release, has only Xcode 3 installed so never tried the release - snow leopard

the problem is that some of the people we send it respond with crash reports.
1x snow leopard (no dev tools) - crash
1x lion (dev tools installed) - crash
1x lion (unknown) - works

its always a black screen when the game starts and does not work.
one tried to start it directly from the console

$ ./TeaArena-Mac
2012-01-30 12:23:07.793 TeaArena-Mac[586:507] *** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[0]

i tried to search for initWithObjects in our project but we never use it nor do the kobold/cocos libs attached (well they use it but the breakpoints don't activate)

there is another crash report here: http://pastie.org/3281685

We are trying to find more people to test, but it does not look good. How can we find the problem? Did we forget some things that need to be packaged as well? I just did product/archive in Xcode.

You can dl the game incl. source (without kobold2d etc) here:
direct: http://globalgamejam.org/sites/default/files/uploads/2012/2551/Tea%20Arena_0.zip
overview: http://globalgamejam.org/2012/tea-arena

We appreciate any help very much :)
thanks for reading and have a nice day :D

I think im a bit confused about how it works.
What is a "reference count"? What is release and retain?
Do i have to release the object everytime i "use" it?

Where can i read more about properties? (@property (nonatomic, retain), etc.)

Hi all,

I released my first game (Rainbow Waterfalls) a few months ago and to be honest the number of downloads is rather poor. I created a full and lite version of the game but even the free version isn't receiving many downloads. Ok, my game isn't the best out there, but there seems to be some very basic games that still 1000's of free downloads.

I'm curious if any of you guys have had the same thing happen and if you have any success fixing this?

I should add I sent my game away to several web sites prior to release and most asked for a fee to review the game (which I have declined thus far). I'm not sure i trust these sites.... it seems more like an ad rather than a review but has anyone tried this route?

Thanks!

Hi, I am happy to announce that cocos2d v2.0-beta is available for download:

* cocos2d-iphone-2.0-beta.tar.gz

Highlights from v2.0-alpha:
- Forward-ported changes from v1.1 (batched particles, faster reorder, ARC compatible, and more)
- Improved draw internal API
- Added alignment + multiline in LabelBMFont
- Added "Milliseconds per frame" in Director
- Improved internal GL cache
- and more

Full Changelog: https://github.com/cocos2d/cocos2d-iphone/blob/release-2.0-beta/CHANGELOG

v2.0 Mini FAQ:

Q: Should I use v2.0 or v1.0
A: It depends on your requirements, and varies from case to case.
A: If you need to support older devices (1st & 2nd generation iPhones) you should use cocos2d v1.x
A: v2.0 is about supporting new technologies (blocks, OpenGL ES 2.0, etc) and improving the current API, while cocos2d v1.x is about backward compatibility.

Q: How stable is v2.0-beta
A: From a code point of view, it is pretty stable. At Zynga, we have just released a game using cocos2d v2.0 (DreamZoo)
A: But from an API point of view, you should know that the API is still not stable. It might change a bit until v2.0-final is released.

Q: When v2.0-final will be released
A:Most probably during Q1 2012, perhaps in February.

My game sprites take up memory when they are created, and seem to keep hold of that memory. They do not take up additional memory if I allocate them again.
My problem is that I get memory warnings in the first level itself, and from my understanding, the game needs at least that much memory to work.

I wanted to know if my sprite sheets have to be a particular size, or whether i don't release the sprites properly(they can be simple images in sprites also).

Right now I do this :
[<parent> removeChild:<child> cleanup:YES];

I also do this:
[<child> release];
<child> = nil;

The deallocate methods are called for sure (even checked by tracing it in dealloc of CCSprite).
Any comments are appreciated. Anything can be useful. Thanks! :/

I wanted to share some code I've written to allow using UIGestureRecognizer classes with cocos2d. This code has saved me a tremendous amount of time handling touch events, so hopefully it will help some others out I can get some feedback on them in the process. The main goal was to be able to get the gesture recognizers to act as close to original design as possible without a lot of setup work to use them.

This major design change I did to accomplish this was to move touches from CCLayer based to CCNode based, this way can be seen as each node being a view. Handling touches this way gives you a lot of flexibility and control to test for touches on individual objects of a scene or a layer like a sprite instead of just knowing the layer was touched somewhere. This change was only for gesture recognizers, I left the way cocos handles individual touch events intact. My other goal was the gesture recognizers should handle touches across nodes, but a touch on a particular node can only be handled by itself and it's children, this mimics the way gesture recognizers normally work with subviews.

Note:
Not all code changes are in this post, I made some changes to CCNode such as moving the isTouchEnabled from CCLayer and the code to retain its gesture recognizers and handle the actual attachment to the view. If this post generates enough interest I will post a full patch.

Example initialization:

CCGestureRecognizer* recognizer = [CCGestureRecognizer CCRecognizerWithRecognizerTargetAction:[[[UIRotationGestureRecognizer alloc]init] autorelease] target:self action:@selector(rotate:node:)];

Example usage:
Usage is very straightforward, the callback function that occurs once a gesture is recognized just needs to take a UIGestureRecognizer and a CCNode as a parameter. Normally you can tell what view was touched from the gesture recognizer, but since we only have one view the CCNode that was touched gets passed to the callback function as well.

- (void) rotate:(UIGestureRecognizer*)recognizer node:(CCNode*)node
{
  UIRotationGestureRecognizer* rotate = (UIRotationGestureRecognizer*)recognizer;
  float r = node.rotation;
  node.rotation += CC_RADIANS_TO_DEGREES(rotate.rotation) -r;
}

Here is the source:
CCGestureRecognizer.h

#ifndef __CCGestureRecognizer_H__
#define __CCGestureRecognizer_H__

#import "ccTypes.h"
#import "CCNode.h"
#import <UIKit/UIKit.h>

@class CCNode;

@interface CCGestureRecognizer : NSObject <UIGestureRecognizerDelegate>
{
  UIGestureRecognizer* m_gestureRecognizer;
  CCNode* m_node;

  id<UIGestureRecognizerDelegate> m_delegate;

  id m_target;
  SEL m_callback;
}

@property(nonatomic,readonly) UIGestureRecognizer* gestureRecognizer;
@property(nonatomic,assign) CCNode* node;
@property(nonatomic,assign) id<UIGestureRecognizerDelegate> delegate;
@property(nonatomic,assign) id target;
@property(nonatomic,assign) SEL callback;

- (id) initWithRecognizerTargetAction:(UIGestureRecognizer*)gestureRecognizer target:(id)target action:(SEL)action;
+ (id) CCRecognizerWithRecognizerTargetAction:(UIGestureRecognizer*)gestureRecognizer target:(id)target action:(SEL)action;

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldReceiveTouch:(UITouch *)touch;
- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldRecognizeSimultaneouslyWithGestureRecognizer:(UIGestureRecognizer *)otherGestureRecognizer;
- (BOOL)gestureRecognizerShouldBegin:(UIGestureRecognizer *)gestureRecognizer;

// this is the function the gesture recognizer will callback and we will add our CCNode onto it
- (void) callback:(UIGestureRecognizer*)recognizer;
@end

#endif  // end of __CCGestureRecognizer_H__

CCGestureRecognizer.m
It looks m_node isn't retained or released, but when you attach a gesture recognizer to a CCNode the node sets this value and also unsets this value when it is released. Since CCNode keeps track of gesture recognizers attached to it doing a retain would mean both objects would never get released.

#import "CCGestureRecognizer.h"
#import "CCDirector.h"
#import "ccMacros.h"
#import "CGPointExtension.h"

@implementation CCGestureRecognizer

-(void)dealloc
{
  [m_delegate release];
  [super dealloc];
}

- (UIGestureRecognizer*)gestureRecognizer
{
  return m_gestureRecognizer;
}

- (CCNode*)node
{
  return m_node;
}

- (void)setNode:(CCNode*)node
{
  // we can't retain the node, otherwise a node will never get destroyed since it contains a
  // ref to this.  if node gets unrefed it will destroy this so all should be good
  m_node = node;
}

- (id<UIGestureRecognizerDelegate>)delegate
{
  return m_delegate;
}

- (void) setDelegate:(id<UIGestureRecognizerDelegate>)delegate
{
  [m_delegate release];
  m_delegate = delegate;
  [m_delegate retain];
}

- (id)target
{
  return m_target;
}

- (void)setTarget:(id)target
{
  [m_target release];
  m_target = target;
  [m_target retain];
}

- (SEL)callback
{
  return m_callback;
}

- (void)setCallback:(SEL)callback
{
  m_callback = callback;
}

- (id)initWithRecognizerTargetAction:(UIGestureRecognizer*)gestureRecognizer target:(id)target action:(SEL)action
{
  if( (self=[super init]) )
  {
    m_gestureRecognizer = gestureRecognizer;
    [m_gestureRecognizer retain];
    [m_gestureRecognizer addTarget:self action:@selector(callback:)];

    // setup our new delegate
    m_delegate = m_gestureRecognizer.delegate;
    m_gestureRecognizer.delegate = self;

    m_target = target;
    [m_target retain];
    m_callback = action;
  }
  return self;
}

+ (id)CCRecognizerWithRecognizerTargetAction:(UIGestureRecognizer*)gestureRecognizer target:(id)target action:(SEL)action
{
  [[[self alloc] initWithRecognizerTargetAction:gestureRecognizer target:target action:action] autorelease];
}

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldReceiveTouch:(UITouch *)touch
{
  CGPoint pt = [[CCDirector sharedDirector] convertToGL:[touch locationInView: [touch view]]];

  BOOL rslt = [m_node isPointInArea:pt];

  if( rslt )
  {
    // still ok, now check children of parents after this node
    CCNode* node = m_node;
    CCNode* parent = m_node.parent;
    while( node != nil && rslt)
    {
      CCNode* child;
      BOOL nodeFound = NO;
      CCARRAY_FOREACH(parent.children, child)
      {
        if( !nodeFound )
        {
          if( !nodeFound && node == child )
            nodeFound = YES;  // we need to keep track of until we hit our node, any past it have a higher z value
          continue;
        }

        if( [child isNodeInTreeTouched:pt] )
        {
          rslt = NO;
          break;
        }
      }

      node = parent;
      parent = node.parent;
    }
  }

  if( rslt && m_delegate )
    rslt = [m_delegate gestureRecognizer:gestureRecognizer shouldReceiveTouch:touch];

  return rslt;
}

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldRecognizeSimultaneouslyWithGestureRecognizer:(UIGestureRecognizer *)otherGestureRecognizer
{
  if( !m_delegate )
    return YES;
  return [m_delegate gestureRecognizer:gestureRecognizer shouldRecognizeSimultaneouslyWithGestureRecognizer:otherGestureRecognizer];
}

- (BOOL)gestureRecognizerShouldBegin:(UIGestureRecognizer *)gestureRecognizer
{
  if( !m_delegate )
    return YES;
  return [m_delegate gestureRecognizerShouldBegin:gestureRecognizer];
}

- (void)callback:(UIGestureRecognizer*)recognizer
{
  if( m_target )
    [m_target performSelector:m_callback withObject:recognizer withObject:m_node];
}
@end

Here are some of the changes to CCNode

-(BOOL) isPointInArea:(CGPoint)pt
{
  if( !visible_ )
    return NO;

  /*  convert the point to the nodes local coordinate system to make it
   easier to compare against the area the node occupies*/
  pt = [self convertToNodeSpace:pt];

  // we have to take the anchor point into account for checking
  CGRect rect;
  /*  we should be able to use touchableArea here, even if a node doesn't set
   this, it will return the contentArea.  */
  rect.size = self.touchableArea;
  CGPoint anchor = anchorPoint_;

  // we pretty much need to undo the anchor to get our rect to start at the lower left
  anchor.x = 0.5f - anchor.x;
  anchor.y = 0.5f - anchor.y;

  rect.origin = CGPointMake( -(rect.size.width*anchor.x), -(rect.size.height*anchor.y) );

  if( CGRectContainsPoint(rect,pt) )
    return YES;
  return NO;
}

-(BOOL) isNodeInTreeTouched:(CGPoint)pt
{
  if( [self isPointInArea:pt] )
    return YES;

  BOOL rslt = NO;
  CCNode* child;
  CCARRAY_FOREACH(children_, child )
  {
    if( [child isNodeInTreeTouched:pt] )
    {
      rslt = YES;
      break;
    }
  }
  return rslt;
}

-(CGSize) touchableArea
{
  // we use content size if touchable area is 0
  if( touchableArea_.width != 0.0f &&
      touchableArea_.height != 0.0f )
    return touchableArea_;
  else
    return contentSize_;
}

-(void) setTouchableArea:(CGSize)area
{
	touchableArea_ = area;
}

Hi,

I am happy to announce that cocos2d v1.1 beta is available for download:
cocos2d-iphone-v1.1-beta.tar.gz

Highlights

* Particles: CCParticleBatchNode, batches multiple particle systems in one OpenGL draw call
* Node/Sprite: much faster reordering, adding and removing of nodes and sprites in batchnodes
* Scheduler: support for delay and repeat of selectors
* Textures: support for RGB888 textures
* TileMap: TMX map supports flipped tiles

Full Changelog: https://github.com/cocos2d/cocos2d-iphone/blob/release-1.1-beta/CHANGELOG

Release Notes: http://www.cocos2d-iphone.org/wiki/doku.php/release_notes:1_1_0 (includes example usage of new functionality)

I would appreciate if you can test this beta release in your games and report any possible bug that you might find. Thank you.

I have an NSObject call GatherQuest which is allocated like this:
[[self alloc]initQuestWithRoom:houseRoom andName:(NSString*)name andTarget:(CCLayer*)target andTime:(int)seconds specialLoot:(BOOL)special];

When [GatherQuest newQuestWithRoom: andName: andTargert: andTime: specialLoot:] is called. However I do not know when to release this and unscheldule its update (which I use CCScheduler for). I pretty much want it to act like a CCNode, so it can be autoreleased whenever the scene is changed. However, I also want to be able to release it whenever the quest is completed. Now I was thinking of doing that in the update but I cannot do [self release] without getting an error.

All in all, my question really asks on how to release and dealloc an NSObject which has an update. I have tried releasing it manually but this does not get rid of the update (Im not even sure it will release it) even though I have [[CCScheduler sharedScheduler]unscheduleUpdateForTarget:self] in the dealloc...

I was wondering, should I add it to the App Store now or wait?
I want to wait BUT I've read that some people had a release date that was a few days after the approval date. And their app didn't appear on the "new" apps list because the date assigned to them was the approval date by the App Store...

Please help me with this, give me your recommendations or knowledge if you have beeb through this !

Thanks a lot, this community has been great!

Hey guys, soon I'll be releasing my first game (finalizing some details in design and code optimization ;) )

So I wanted to ask for some advice from those of you who have already published their games, free or paid!

Here are some questions:

1 - I will not be paying one dime for advertising, since I don't have any money. So what did you do to advertise your game? ideas that were free!

2 - This one is related to #1, what strategies did you use to increase downloads once the game was published? (example, lite version, changing price, etc)

3 - How are you doing on sales (if it's not a secret) and how do you think you got there? Numbers will be greatly appreciated

4 - How many games have you released, what did you do differently in terms of advertising and what difference did it make on sales (I know I'm being kind of repetitive, but I want to learn as much as possible)

5 - When did you release the game, why did you choose that date?
6 - ... still thinking some other questions....

Im asking this questions because they are of real interest and value to me. I also think that they can help a lot of people with their projects, so please don't hold back and share your experiences, good and bad will work!

I'll do the same for you once the game is released! sharing is caring hehe

THANKS in advance!

My game runs fine when I run the first scene. I use something called 'getAvailableMegaBytes' to trace the memory available on the device.
So when I play the second level which uses the same scene all over again, the available memory reduces and the game is ultimately going to give memory warnings or crash when it runs out of memory.

Any pointers on what I should do to deallocate properly? Could there be any other reason for this to happen?

Thanks

Hi, i've a problem with a retained action. In the loading phase i do this:

obj = [layer.factory objectFromClassName:[[BookActor class]description]];
			obj.onClickAction = [BookActor shake:cocosLayer.position];

where onClickAction is
@property(nonatomic,retain)id onClickAction;

Now, i start an action like that:

+(id)backFlip:(CGPoint)anchorPoint
{
	id jump = [CCJumpBy actionWithDuration:0.6 position:anchorPoint height:150 jumps:1];
	id flip = [CCRotateBy actionWithDuration:0.4 angle:360];
	id action = [CCSpawn actions:jump,flip,nil];
	return action;
}

called by this method:

-(void)onClickAt:(CGPoint)p
{
	float rnd = CCRANDOM_0_1();

	if([sprite numberOfRunningActions] == 0)
	{
		if(rnd<0.4)
			onClickAction = [BookActor jump:self.position];
		else if(rnd<0.7)
			onClickAction = [BookActor backFlip:self.position];
		else
			onClickAction = [BookActor frontFlip:self.position];
	}
	[super onClickAt:p];
}

If i call a replaceScene the app crash because of
-[CCSpawn release]: message sent to deallocated instance 0x3d3620

My cleanup code is:

-(void)onExit
{
	[self stopAllActions];
	[super onExit];
}

-(void)dealloc
{
	self.onClickAction = nil;
	[super dealloc];
}

When the debugger reach self.onClickAction = nil; i can see a NSZombie on onClickAction.
Enabling cocos2d log i get this message

cocos2d: deallocing <CCSpawn = 003D3620 | Tag = -1>

BEFORE reaching the dealloc method.
It's like cocos deallocing onClickAction no matter what i set on property but it should have retained the action.
If i don't release onClickAction everything is fine but i don't understand why.
Any ideas?

Hi guys, the last app i made was simply released the second it got approved by apple, i was just wondering if theres a way to stop this happening so that i can time the release with my marketing.

I'm wondering what you would do as a new developer who wants to make the best impact as he/she can.

Currently the programming/gfx is at 60%, I think i could finish it within the week if I work full bolt on it. However even if I do finish the programming I still have a lot of questions to write (i'm making a trivia game).

Would you release early with 3 levels thats about 900 unique questions which we already have ready to go with a quickplay mode also 1000 unique questions seperate from singleplayer?

Or delay it a little longer and release 6 levels with 1800 unique questions with quickplay and multiplayer each with their own unique questions (1000 each)? Though multiplayer just playing on the same device. Similar to a board game

color + shape is a matching game that requires quick thinking and fast reflexes. Move the puzzle blocks around the grid with your finger, and try to line up four or more blocks that have the same color or same shape. Chain multiple matches to increase your score multiplier and recharge your "move" meter! Compare high scores with your friends using Game Center.

How To Play
Touch anywhere on the puzzle grid and drag your finger to move blocks. If you move a block off one side of the grid, it will reappear on the other side, so use this to your advantage. Match four or more blocks of the same color or same shape to make them disappear. Sequential matches will boost your "chain" counter, giving you more points per match. Each time you move a block, your "move" meter will decrease. When it is empty, that means game over! Keep it charged by making quick matches.

Screenshots

Check it out on iTunes!

Here are some promo codes for those who are interested, but don't have a dollar:

FYMRYEMK4XH3
3LJRMARWPFPT
3PTWE77WEXH3
J9WWXMAM76WM
MHL3MLFWEEAA
HP9YFKMRME9J
LMRPNKTTN7AH
TT34LRNY9M4W
9JW9X3T6NFXH
JYWTYXA7EMMR

Hi all guys, I have all day trying to figure out an strange issue using particles.

In my game every amount of time, let's say 10 sec a particle emitter will appear, if I run on device in DEBUG configuration the game works fine and around 60fps, but if I run the game on RELEASE everything go fine until the particle appears and the frames drop to 40 and the gameplay is affected by lag. I'm really frustrated :-S

This happen only on my iPhone 4, I tested on an iPod touch 3rg and the problem do not appear.

The particle is generated on a plist file using Particle Designer. I'm using cocos2d rc2.

The particle has maxparticle value set to 30 .

Any hint would be appreciated :)

Hi,

I'm happy to announce that v1.0.0-rc3 is available for download:
cocos2d-iphone-1.0.0-rc3.tar.gz

Highlights:
* Skew transformations
* Debug info in TextureCache
* Bug fixes

Release Notes (MUST READ)
* Release Notes 1.0.0 (Includes detailed description of the new features)

Full Changelog
* CHANGELOG

API Reference
* API Reference v1.0.0

If your game reorders more than object per frame, it is recommended to use the reorderSprite version:
* cocos2d-iphone-1.0.0-rc3-reorderSprite.zip

What's next:
* Unless we find some critical bugs, the next release will be 1.0.0 and will only include minor bug fixes
* Expect a cocos2d 2.0-alpha in the short term. It is like v1.0.0 but with OpenGL ES 2.0 support.

If you find a bug in 1.0.0-rc3, please, let us know! Thank you.

I found circular reference under some condiction.
When add schedule in layer/scene , the schedule retain its target ,
this could cause the layer/scene not release after replaceScene

why and how to solve?

I'm trying to make a callback layer that will execute a function when it is about to be removed. The problem is that the retainCount on the CCCallFunc never reaches zero.

The pause menu is using this in the code below (very bottom). Every time the pause menu is created, the retainCount for the parent layer's CCCallFunc increases by one extra. Because of this, the parent layer never can be dealloc'ed.

The extra increase comes from [CCCallFunc actionWithTarget:self selector:@selector(pauseDone)].

Digging deeper, the _callback retainCount never reaches zero. When the extra release is added in, everything seems to work with no problems but this shouldn't be needed.

@interface CCCallbackLayer : CCLayer {
	CCCallFunc* _callback;
}
-(void) enableCallback:(CCCallFunc*) func;
@end

@implementation CCCallbackLayer
-(id) init
{
	if( (self=[super init]))
	{
		_callback = nil;
	}
	return self;
}

-(void) enableCallback:(CCCallFunc*) func
{
	_callback = func;
	[_callback retain];
}

-(void) dealloc
{
	// Trigger the callback before we get deleted
	if (_callback) {  // _callback retainCount=1
		[self runAction: _callback];  //_callback retainCount=2
		[_callback release];     // _callback retainCount=1
	}
	[super dealloc];
}
@end

------------------

// Open up the new pause menu which is derived from CCCallbackLayer
// 

-(void) pauseTapped:(id)sender {
	PauseLayer* pause = [PauseLayer node];
	[pause enableCallback:[CCCallFunc actionWithTarget:self selector:@selector(pauseDone)]];  // CCCallFunc retainCount increases
	[[self parent] addChild: pause];
}

Hi,

cocos2d for iphone v1.0.1 is available for download.

Download: cocos2d-iphone-v1.0.1.tar.gz

This is a bug-fix release. Not new features were added since v1.0.0.

Changelog:

. [FIX] All: Implicit atomic properties converted to nonatomic
. [FIX] All: Removed deprected code
. [FIX] CCArray: copyWithZone fixed
. [FIX] Director: renamed frames -> totalFrames. It works as expected, value is not being reset.
. [FIX] Menu: If any ancestor is invisible, then touches won’t be accepted
. [FIX] Node: vertexZ returns points, not “pixels”
. [FIX] LabelTTF: don’t crash when calling description after dealloc
. [FIX] Tests: [window release] instead of [window dealloc]
. [FIX] Texture: TextureCache#dump reports the right info (issue #1205)
. [FIX-MAC] CocosDenshion: Cleanup buffers to prevent noise

Hi , I have around one week trying to figure out why the memory of my help scene is not released. I can't see anything, I was searching in the whole forum to check other informations about this kind of problems with no luck.

This is the complete code of my Help Scene:

#import "Help.h"
#import "SoundMenuItem.h"
#import "cocos2d.h"
#import "CCScrollLayer.h"
#import "MainMenuNode.h"

@implementation Help

+(CCScene*) scene
{
	CCScene *s = [CCScene node];

	id help = [Help node];
	[s addChild:help];

	return s;
}

#pragma mark Help - Init & Creation

//
// Return the list of needed images
// These images are going to be async-loaded
//
+(NSArray*) textureNames
{
	return [NSArray arrayWithObjects:
			@"helpscreens.png",
			nil];
}

-(id) init
{
	if( (self=[super init] ) ) {

		[[CCSpriteFrameCache sharedSpriteFrameCache] addSpriteFramesWithFile:@"helpscreens.plist"];

		CGSize s = [[CCDirector sharedDirector] winSize];

		CCMenu *menu;

		CCMenuItem* item1 = [SoundMenuItem itemFromNormalSpriteFrameName:@"btn_back_normal.png" selectedSpriteFrameName:@"btn_back_press.png" target:self selector:@selector(backCallback:)];	

		menu = [CCMenu menuWithItems:item1, nil];
		menu.position = ccp(0,0);
		[self addChild:menu z:5];
		[item1 setPosition:ccp(s.width - 25,s.height-22)];

	}

	return self;
}

-(void) backCallback:(id) sender {
	[[CCDirector sharedDirector] replaceScene: [CCTransitionFade transitionWithDuration:0.5f scene:[MainMenuNode scene] ]];
}

-(void) dealloc
{
	[self unscheduleUpdate];
	[self unscheduleAllSelectors];
	[self stopAllActions];

	[self removeAllChildrenWithCleanup:YES];

	[[CCSpriteFrameCache sharedSpriteFrameCache] removeSpriteFramesFromFile:@"helpscreens.plist"];
	[[CCTextureCache sharedTextureCache] removeTextureForKey:@"helpscreens.png"];
	[[CCTextureCache sharedTextureCache] removeUnusedTextures];
	[super dealloc];
}

@end

As you can see is very simple, the dealloc method is already called, but the memory is not release, helpscreens.png is preloaded in Async way from the main menu.

Activity monitor show around 20.56 MB before call the help scene.

After the Help Scene is called memory show 22.80 MB.

The problem comes when I back to the main menu, the memory stay in 22.80 MB

In fact I quit all sprites that use the helpscreens.plist, just load and try to release and it didn't help.

Any Hint would be very appreciated, I'm getting crazy with this.

My name is Paul Engstler and I'm one of the youth developers (14) and I just released my first App in the App Store which is powered by Cocos2D and Chipmunk. First of all thanks to everybody who helped me. Thanks riq and slembcke for creating this to great frameworks! It would be great if you could provide some feedback so that I can improve me. Thank you! :)

Game idea:

Basically your job is to "kick out" the red blocks by tapping. When you tap a blue block appears. Your goal is to do this not by killing your device but rather by creating a blue block at the right place. The time is running so hurry up! This is a really challenging in different stages in the Chipmunk world. Can you master it?

The whole App Store Description:

Get ready for Blocarde, one of the most challenging arcade games. It‘s fast and relaxing at the same time. Tap to create blue blocks and stop the red blocks from taking over! Extremely addicting without being too hard.

What players say about it:

- "I truly love Blocarde!"

- "Blocarde is the most addicting game I‘ve ever played."

- "It‘s really challenging and funny."

This is inside Blocarde:

• Two single player modes: the stacking and the physics challenge mode.

• A unique mode to create your own challenge.

• Five different stages with different soundtracks.

• Bluetooth mode to play it with a friend.

• A challenge sharing service to send your challenges via Twitter.

• Record system to determine who is best in the challenge you created.

• Beautiful graphics and animated backgrounds.

• Eight achievements and two leaderboards in Game Center.

Ready for the challenge?

Some Screenshots:

Promotion Codes (PM me if all are gone but you still want one):

FYP64NRA7AXX
W7FN9TAL4T34
AAETMTYNMMM3
TFKK3XXL6693
TFK69AJ4WK99

Please leave a review!

iTunes Link: http://bit.ly/g19GDH

A huge "Thank you!" to my beta testers. You helped me making this game good.

Thank you for reading, writing feedback and leaving a review. I really appreciate it.

Paul Engstler :)

cocos2d-iphone-1.0.0.tar.gz

I’m happy to announce that:
* after 3 years, 2 months and 4 days (1st commit)
* with more than 140 contributors
* after more than 2600 commits
* after 63 releases (~41 commits per release)
* with more than 2500 games in the AppStore (many games in the Top #10, and some Top #1)

cocos2d for iPhone v1.0.0 is available for download!

Many thanks to all the developers, contributors, testers, bug reporters, and the cocos2d community. Thank you for making this happen!

Release Notes: cocos2d v1.0.0 release notes

API Reference: v1.0.0 API Reference

Full Changelog: v1.0.0 Changelog

If your game reorders more than 1 sprite per frame, try the reorder branch: cocos2d-iphone-1.0.0-reorderSprite.zip

Hello,
Could someone please help me out with a strange problem:

Building a Release build config prevents accelerometer from responding on a device.
Building a Debug build config does not have this problem - accelerometer works OK.

I have gone through every option in project and target build settings but cannot figure this one out. I am working in Xcode 4 with iOS 4.3, targeting for 4.2.

Any hints on what have I messed up?

Thanks!

Hello everyone.

Our new game Zombie Toss Basketball is now available in the app store.

It's a Zombie Flingin' Funhouse!

iTunes Link: Zombie Toss Basketball (iTunes)
Website: PrestoArts.com

Here are some screenshots and not so great quality (sorry) in-game play video:

http://www.youtube.com/watch?v=gFTUBOPXRSY

After the smoke had cleared from the 'Near Zombie Apocalypse' of 2023 (or 'NZA' for short)
there was a great emptiness felt by those humans who had survived.

It was created with cocos2d (of course) and box2d.

Best regards,

Joseph

Hello, have not been here for a long time.
And now I am facing the old and popular problem. Despite that it is popular problem, I have not found any useful and working solution for this problem.
So, I want to release CCAnimation and free up the memory.
Player.m

playerWalkAnim = [CCAnimation animation];
    playerWalkAnim.name = @"PlayerWalkAnim";
    for( int q=1;q<12;q++){
        [playerWalkAnim addFrameWithFilename: [NSString stringWithFormat:@"walkforward_%.2d.png", q]];
    }
    walkAction = [CCRepeatForever actionWithAction:[CCAnimate actionWithDuration:1.5 animation:playerWalkAnim restoreOriginalFrame:NO]];
    [walkAction retain];

so, this is how I create the animation. And now, the methods I have tried to release it and to free up the memory.

-(void)destruct:(CCNode*)node{
    playerWalkAnim = nil;
    walkAction = nil;
    [playerWalkAnim release];
    [walkAction release];
//Nothing helped, and I try harder;
    [[CCDirector sharedDirector] purgeCachedData];
    [[CCTextureCache sharedTextureCache] removeAllTextures];
    [CCTextureCache purgeSharedTextureCache];
    [[CCSpriteFrameCache sharedSpriteFrameCache] removeSpriteFrames];
    [CCSpriteFrameCache purgeSharedSpriteFrameCache];

    [[CCAnimationCache sharedAnimationCache]removeAnimationByName:@"PlayerWalkAnim"];

I tried to name animation, to use removeAnimationByName:.
I tried to purge sharedTextureCache.

Solving this issue, I have found some interesting information: creating animation, CCAnimationCache is empty; CCSpriteFrameCache is also empty, but CCTextureCache - is not. Removing all textures from the CCTextureCache does not free memory.

Now I think about removing textures using

-(void) removeTexture: (CCTexture2D*) tex
-(void) removeTextureForKey:(NSString*)name

but I do not know how to get the name of the texture, or how to get the texture at all.

Am I doing everything correct? I showed you the class Player : CCSprite. In the app, there would be about 10 units of the "Player". Is it correct to create animation for a unit inside a class? And how to properly remove the CCAnimation.

If it is possible, the source code showing how the memory should be freed by releasing CCAnimation would be appreciable.
Thank you!