Help needed: v0.99.0rc coming really soon

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

Help needed: v0.99.0rc coming really soon

(26 posts) (9 voices)

Started 2 years ago by riq
Latest reply from shadaz

Tags:

riq
Key Master

Hi,

v0.99.0rc will be released really soon.
Since it contains many changes I would appreciate if you can test SVN r1751 (or newer).

Features:
- It is faster than v0.9.0beta2 and v0.8.2. In some scenarios it should be MUCH faster
- It works on iPhone/iPod Touch and iPad (you need SDK 3.2) (cocos2d and all the tests are resolution independent)

So, how can you help ?
- v0.99rc should be faster, at least it should not be slower. If you perceive that it is slower, please post it here. It would be great if you could also describe what nodes are you using
- it should compile (and work) on SDK 2.2, 3.0, 3.1 and 3.2
- templates should work

Incompatibility changes from v0.9-beta2:
- CCNode uses the "_" suffix for ivars. Eg: if you were using children, now you should use children_. But if you were using self.children, then you are OK.
- Scheduler was rolled back to v0.9-beta1. schedule:repeat and other scheduler changes were postponed to v0.99.1
- Camera: please read this thread http://www.cocos2d-iphone.org/forum/topic/3959
- OpenGL default states: please read this thread http://www.cocos2d-iphone.org/forum/topic/3976
- TMXMap: "objects support" were simplified.

So far, this is the list of changes:
http://cocos2d-iphone.googlecode.com/svn/trunk/CHANGELOG

Posted 2 years ago #
MikeSz
Member

just included it in our new project. gonna tell you when I find any issues with it

I'd like to know 2 things though:

1) Why this _ thing ? (or using self.) ? What is the benefit of this ?

2) What is the benefit of using BOOL CC_BOOL_IS_BIT(visible_); ? I know it's one bit instead of byte, but is it faster in any way ? is it worth using instead of pure BOOL for gameobjects etc ?

Posted 2 years ago #
riq
Key Master

1) Why this _ thing ? (or using self.) ? What is the benefit of this ?

2) What is the benefit of using BOOL CC_BOOL_IS_BIT(visible_); ? I know it's one bit instead of byte, but is it faster in any way ? is it worth using instead of pure BOOL for gameobjects etc ?

1)
the suffix is to:
- prevent collision with ivars from subclasses
- prevent confusion between ivar an properties

2)
It's not faster but it consumes less memory. It is a little optimization:
Instead of consuming 1 byte per BOOL, it consumes 1 bit per BOOL.
the CC_BOOL_IS_BIT macro exists because in SDK 2.2 you can't "propertyize" a bit, so it is disabled on SDK 2.2

Posted 2 years ago #
georgeburns
Member

I'm using 1751... working great.

I went from the original beta to 1742 and noticed massive speed improvements. So much though I had to decrease my gravity (chipmunk) so that it felt right.

Only two problems with the upgrade...
removeChild in TMXLayer wasn't using child_
and some other file was doing the same but I don't remember which... It may have been CCLayer.
and ... that could have been my fault.

Posted 2 years ago #
MikeSz
Member
thanks for explanations Riq !

had no problem compiling it whatsoever, only had to add the self. to visible and children

but I was on .99 RC before

other than that, there is a change for box 2d debug drawing, this is the new version (to put in draw)
```
glDisable(GL_TEXTURE_2D);
	glDisableClientState(GL_COLOR_ARRAY);
	glDisableClientState(GL_TEXTURE_COORD_ARRAY);

	world->DrawDebugData();

	// restore default GL states
	glEnable(GL_TEXTURE_2D);
	glEnableClientState(GL_COLOR_ARRAY);
	glEnableClientState(GL_TEXTURE_COORD_ARRAY);
```
also - - (void)ccTouchesMoved:(NSSet *)touches withEvent:(UIEvent *)event; is the new way, notice no BOOL in the return type

but the transition is super smooth
Posted 2 years ago #
MrMojo
Member

@Riq: So can the camera zoom in now? Seemed like the camera changes were possibly causing an issue with zooming in?

http://www.cocos2d-iphone.org/forum/topic/3959#post-24020

Thanks again for your great work!

Posted 2 years ago #
riq
Key Master

@georgeburns: Try to make your game CPU independent. Try to use the "delta time" when possible. The devices have different speeds, so you should not hardcode any value for a particular device.

UPDATE: I'm glad to hear that r1751 is faster :-)

@mikesz: yes, you need to add the new glEnableXXX before drawing in box2d (the template already has it)

Posted 2 years ago #
MikeSz
Member

I know Riq, the code IS straight from the template ;) just posting it here for the lazy ones so they don't have to look for it too much ;)

Posted 2 years ago #
riq
Key Master

@MrMojo:
Good question... the short answer is: No, you can zoom in, but you can zoom out.

The long answer is: I really don't like the old Camera implementation:
- it had lots of bugs: wrong offset in landscape mode, it was resetting the parent transformation, it was impossible to modify the center while orbiting

The new implementation is very simple: it just provide a gluLookAt interface to each node, honoring previous transformations.
So, it works OK in landscape mode, portrait, when your parent was rotated, its possible to chain cameras, etc..., etc...
But what you cant' do (remember it is an interface to gluLookAt) is to zoom in, because it is already using the maximum zoom in. But it is possible to zoom out.
So, my suggestions is:
- If you want 3d effects, but you don't need zoom in: use the camera
- If you don't want 3d effects, but you want zoom it, use: "position and scale"
- if you want 3d effects + zoom in then use: camera for panning and 3d effects, and use scale for zooming in/out.

Of course I would like to support zoom_in in the camera, but I just don't know how. Ideas ?

UPDATE: If you have ideas,suggestions,etc about the camera, please post it here: http://www.cocos2d-iphone.org/forum/topic/3959 Thanks.

Posted 2 years ago #
napierzaza
Member

Looking forward to the new version. Everything has been working fine so far with 0.9 and I hope that a few tricky parts are resolved. I've definitely suffered through some speed issues in the earlier betas.

Posted 2 years ago #
sergen1976
Member

Riq,

Thanks for your hard work! It is great that you are making cocos2d work with SDK 3.2.2 beta.

I got the latest code using svn checkout http://cocos2d-iphone.googlecode.com/svn/trunk/ cocos2d-iphone-read-only. Before I was waiting for the releases but now I can't wait to start developing for iPad using cocos2d framework.
When I am trying to build target "box2d" for example I am getting the error "There is no SDK with the name 'iPhoneOS 2.2.1'. The reason for that probably is that I installed SDK 3.2.2 beta on clean Snow Leopard and this beta doesn't come with iPhoneOS 2.2.1 SDK.
Please take a look at this issue because I think it might be somewhat important in the future.

Thanks!

Posted 2 years ago #
riq
Key Master

@sergen: You need to select an Active SDK 3.0 (or later) when you use XCode 3.2.2 since SDK 2.2.1.

Posted 2 years ago #
crmagicxxx
Member

Hey, I tested it and can't tell if it's faster but for sure it's not slower. Latest project I am working on is fairly optimized already, but I am sure latest revision isn't slower...

Anyway, posted an issue about old code snippet for preventing flicker at startup that doesn't work anymore with new GL states http://www.cocos2d-iphone.org/forum/topic/4156

Posted 2 years ago #
shadaz
Member
Hello, I am having problem with:

- (BOOL) ccTouchesBegan:(NSSet *)touches withEvent:(UIEvent *) event

which is now..

- (void)ccTouchesBegan:(NSSet *)touches withEvent:(UIEvent *)event;

I was using the kEventHandled and kEventIgnored constants as well.

I see this was changed with issue:

TouchDispatcher: StandardTouchHandler returns void (not BOOL). They are executed after the TargetedHandlers (issue #710)

what is the proper way to implement this now?

my old code:
```
- (BOOL) ccTouchesBegan:(NSSet *)touches withEvent:(UIEvent *) event
{
	UITouch *touch = [touches anyObject];
	CGPoint point = [touch locationInView: [touch view]];

	point =  [[CCDirector sharedDirector] convertToGL: point];
	if (CGRectContainsPoint([playerA rect], point))
	{
		[self openPicker:playerA];

		return kEventHandled;
	}
	else if (CGRectContainsPoint([playerB rect], point))
	{
		[self openPicker:playerB];

		return kEventHandled;
	}

	return kEventIgnored;
}
```
thanks!
Posted 2 years ago #

MikeSz
Member

depends if the return values are of importance to you. if yes - you can always store them in some extra boolean value

- (void) ccTouchesBegan:(NSSet *)touches withEvent:(UIEvent *) event
{
	UITouch *touch = [touches anyObject];
	CGPoint point = [touch locationInView: [touch view]];

	point =  [[CCDirector sharedDirector] convertToGL: point];
	if (CGRectContainsPoint([playerA rect], point))
	{
		[self openPicker:playerA];
		// store true in some extra value if needed
	}
	else if (CGRectContainsPoint([playerB rect], point))
	{
		[self openPicker:playerB];
		// store true in some extra value if needed
	}
}

EDIT: or just use the touch dispatcher. I don't use it though, have to learn it one day but didn't have a need yet

Posted 2 years ago #

jakempapa
Member

Updated to 1755, and compiled. got some _ errors and ccTouches... conflicts, after modifying those, it works very well.
In addition, I had an issue with new flipX and just found out I need to use scale instead.

Posted 2 years ago #
shadaz
Member

I got code to compile having issue with an issue that was corrected before with issue #690. I am using zwoptex offsets and when animating sprites that are flipX, the offsets seem to be ignored again. This was fixed in in #690, now I am having the problem again.

EDIT: scaleX = -1.0 fixed my flipX issue.

Posted 2 years ago #
riq
Key Master

@shadaz @jakempapa:

Yes, flipX and flipY flip the texture. But in order to flip the texture correctly I need to know the trimmed pixels from left,right,tip,bottom. Right now I only have information from left,top.

And as you figured out, you could use scaelX = -1 instead and it will work correctly. Please, take into account that scaleX = -1 will flip the anchorPoint too!.

there is more information about this here:
http://www.cocos2d-iphone.org/forum/topic/3447

Posted 2 years ago #
shadaz
Member

Makes sense riq, thank you.

I have 1 last issue, something changed with anchorpoints on my children:

[myParentSprite addChild:myChildSprite];
[myChildSprite setAnchorPoint:ccp( .5f, 0.0f)];

Pre v.99 I used that to center horizontally the child sprite on the parent sprite. It now is on the left.

I will look through the forum/change logs to see what changed.. but if anyone have idea how to accomplish the same result in .99, i would appreciate it!

Posted 2 years ago #
riq
Key Master

@shadaz: please, see the tests/SpriteTest.m. It has many tests that uses different anchor points both in standar sprite and in sprite sheets.

Posted 2 years ago #
shadaz
Member

Hi riq,

I think i see what is happening, in v.9 when I added a child, it put it in the center. in v.99 it places it bottom left.
Another problem I just noticed is huge lag on child sprites. for example, if I have a sprite with a child sprite on top of it moving across the screen, the child sprite does not move until its parent is 1/2 way across the screen, then it jumps and appears above the parent. I will see if I can get you example of this, but I am having alot of problems with spritesheet children in v.99, it was working perfectly in v.9.

Posted 2 years ago #
riq
Key Master

@shadaz: could you post the code to reproduce it ? thanks.

Posted 2 years ago #
shadaz
Member

After debugging for a while I think it may be an issue unique to my code. I will run some more tests and if I find an issue in v.99 I will let you know. thanks again.

Most of my problems are really due to the positioning of child sprites. Im not sure what changed, but in .9 it placed children in center and I have some offset indexes to position children. Now that v.99 places children at 0,0 instead of center - its causing havoc on me.

Can you please just let me know if this behavior was an intentional change for v.99 (center vs 0,0). Then at least I can switch my offsets and everything will be fine.

Posted 2 years ago #

shadaz
Member

ok, I replicated my problem with the sprite test sample code. Add this test, and run it in v.9 and then in v.99. I use a few schedulers in there but its pretty straight forward. In v.9 the child sprite relative positions are different than v.99 and in v.9 the offsets dont jump around like they do in v.99.

In this example the child sprite is above the parent sprite and its supposed to remain stationary (it does in v.9) in v.99 it jumps around and its relative position is different. Anyway the expected result is it to remain in 1 spot like v.9.

so there are 2 issues that I am having that changed moving from v.9 to v.99

1) the relative position of child sprites
2) the offsets changing during animation

#pragma mark -
#pragma mark SpriteSheetChildrenAnchorPoint

@implementation SpriteSheetChildrenAnchorPoint

CCSprite *spriteA,*spriteB;
-(id) init
{
	if( (self=[super init]) ) {

		CGSize s = [[CCDirector sharedDirector] winSize];

		[[CCSpriteFrameCache sharedSpriteFrameCache] addSpriteFramesWithFile:@"animations/grossini.plist"];

		CCNode *aParent;
		CCSprite *point;
		//
		// SpriteSheet
		//
		// parents

		aParent = [CCSpriteSheet spriteSheetWithFile:@"animations/grossini.png" capacity:50];
		[self addChild:aParent z:0];

		NSMutableArray *animFrames = [NSMutableArray array];
		for(int i = 0; i < 14; i++) {

			CCSpriteFrame *frame = [[CCSpriteFrameCache sharedSpriteFrameCache] spriteFrameByName:[NSString stringWithFormat:@"grossini_dance_%02d.png",(i+1)]];
			[animFrames addObject:frame];
		}
		CCAnimation *animation = [CCAnimation animationWithName:@"dance" delay:0.2f frames:animFrames];

		// anchor (0.5, 0.5)
		spriteA = [CCSprite spriteWithSpriteFrameName:@"grossini_dance_08.png"];
		[spriteA setPosition:ccp(s.width/2,s.height/2)];
		[spriteA runAction:[CCRepeatForever actionWithAction: [CCAnimate actionWithAnimation:animation restoreOriginalFrame:NO] ]];		

		spriteB = [CCSprite spriteWithSpriteFrameName:@"grossini_dance_05.png"];
		[spriteB setPosition:ccp([spriteA contentSize].width/2  ,[spriteA contentSize].height)];
		spriteB.anchorPoint = ccp(0.5f,0.0f);

		[aParent addChild:spriteA];
		[spriteA addChild:spriteB];

		point = [CCSprite spriteWithFile:@"r1.png"];
		point.scale = 0.25f;
		point.position = spriteA.position;
		[self addChild:point z:10];		

		[self schedule: @selector(test) interval: 2.0f];

	}
	return self;
}

-(void)test
{

	[self unschedule:@selector(test)];
	[self schedule:@selector(manual_animate) interval:.25f];
	[spriteA stopAllActions];
}

int xx = 0;
-(void)manual_animate
{
	if (xx==14)
		xx=0;
	CCSpriteFrame *frame = [[CCSpriteFrameCache sharedSpriteFrameCache] spriteFrameByName:[NSString stringWithFormat:@"grossini_dance_%02d.png",(xx+1)]];

	CGRect rect = [frame rect];
	CGPoint offset = [frame offset];
	[spriteA setOffsetPosition:offset];
	[spriteA setTextureRect:rect];

	//[spriteB setPosition:ccp([spriteA contentSize].width/2  ,[spriteA contentSize].height)];
	[spriteB setPosition:ccp(26  ,109)];
	xx++;
}

- (void) dealloc
{
	[[CCSpriteFrameCache sharedSpriteFrameCache] removeUnusedSpriteFrames];
	[super dealloc];
}

-(NSString *) title
{
	return @"SpriteSheet: children + anchor";
}
@end

Posted 2 years ago #

riq
Key Master

@shadaz: The relative children position was discussed here:
http://www.cocos2d-iphone.org/forum/topic/3541

probably you were using an SVN version that included childrenAnchorPoint.

v0.99 like in v0.8, the children are added relative its parent (0,0) coordinate.
The childrenAnchorPoint was added a few weeks ago, but was removed only a few days after it was added.

Posted 2 years ago #
shadaz
Member
Riq,

Thank you so much. I started building my compound sprites at the start of this month, and did not know there was debate going on how to deal with children offsets. I searched around when everything fell apart in .99 and I could not find that thread. Now that I see It, it explained everything and the solution you gave was elegant and clean.

ccpAdd is a nice way that solved my compound sprite offset problems. thank you.
```
CGSize parentSize  = [octopus contentSize];
CGPoint center = ccp( parentSize.width/2, parentSize.height/2);

shoe1.position = ccpAdd( center, ccp(-50,-30) );
```
Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.