cocos2d v0.8-beta released « cocos2d for iPhone

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

cocos2d v0.8-beta released

(40 posts) (17 voices)

Started 2 years ago by riq
Latest reply from Clain

Tags:

12 Next »

riq
Key Master
cocos2d v0.8-beta is available for download.
http://cocos2d-iphone.googlecode.com/files/cocos2d-iphone-0.8-beta.tar.gz

release notes (MUST READ):
http://www.cocos2d-iphone.org/wiki/doku.php/release_8_0

v0.8-beta, is BETA. It means
It means:
- it's not the final v0.8 version
- it's not feature freeze
- it's API is not frozen
- documentation might be incomplete or inaccurate
- it might contain lots of bugs
Begin said that, beta testers are welcomed.

Also, like in previous versions, this release was made with the effort of lots of persons. Please take a look at the authors file:
http://code.google.com/p/cocos2d-iphone/source/browse/trunk/AUTHORS
Posted 2 years ago #
edisonslabs
Member

Very very good, a lot of features and good details in the release notes! I'll test it out a little bit later when I'm done working on my current thing.

Posted 2 years ago #
Joao Caxaria
Member

Hi Riq,

I've been using 0.8, updating from the trunk as I remember. The only thing I had a hard time with was the menus and the new touch notifier. I had a scene with a few of them and it just broke...
Other than that, it's looking good. :) Congratulations.

Posted 2 years ago #
tjweir
Member

Great stuff Riq!

Posted 2 years ago #
arian487
Member

Thanks riq, seriously awesome work!

Posted 2 years ago #
sunsu
Member

0.8 has been working great for me! I especially like the BitFontAtlas...that made my life a whollleeee lot easier.

Posted 2 years ago #
OldJames
Member

Getting a compile error. Not something I recognize.

No architectures to compile for (ONLY_ACTIVE_ARCH=YES, active arch=armv6, VALID_ARCHS=i386).

Not really sure where to go from here.

Posted 2 years ago #
OldJames
Member

I take it back, forgot to set my builds.
Anyone else with same dumb mistake, be sure to set build with (simulator, target, matching exec).

Posted 2 years ago #
UloPe
Member

Thanks for the 0.8!

Is it only me or does the sound in the "SoundEngineTest (experimental)" not change at all for you too when dragging around the sound source?

Posted 2 years ago #
PhilM
Member

Just quickly tried updating to the beta from 991 revision of trunk & having issues with the TouchDispatcher.

After replacing the old TouchDispatcher 'addEventHandler' call with the new 'addTargetedDelegate' (& also the removeEventHandler with removeDelegate) I'm getting the following error:

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Delegate already added to touch dispatcher.'

But thats the first call to the touch dispatcher, so that doesn't make sense to me, although I do have other layers that will add to it later in the loading process, that shouldn't be effecting this.

I don't have time to properly debug it right now, will have a look later tonight.
Anyone encountered anything similar?

Thanks,
Phil

Posted 2 years ago #
Codemattic
Moderator

"Is it only me or does the sound in the "SoundEngineTest (experimental)" not change at all for you too when dragging around the sound source? "

There are four sounds. A clank, a chicken, waterfall, and a trance-loop. The trace-loop plays as background music and does respond to position change. The problem is that the trace-loop is so much louder than the other sounds so that its easy to miss them. Clicking on the green button at the center bottom plays the clank and the chicken. The two red dots are the chicken and waterfall and they respond to listener position but are harder to hear.

However, I still think its not working quite right. Im experimenting with it now, if I can figure out whats happening Ill post back.

Posted 2 years ago #
UloPe
Member

@Codemattic:
You're right. However it seems the [bgTrack setGain:0.3f]; has no effect. I tried multiple other values without the volume of the background track ever changing.

Posted 2 years ago #
Codemattic
Moderator

"Is it only me or does the sound in the "SoundEngineTest (experimental)" not change at all for you too when dragging around the sound source? "

change the background track volume to very low:

[bgTrack setGain:0.005f];

and you should be able to hear the other positional sounds.

"However, I still think its not working quite right. Im experimenting with it now, if I can figure out whats happening Ill post back. "

I was wrong - it seems to work fine.

Posted 2 years ago #
UloPe
Member

"change the background track volume to very low:

[bgTrack setGain:0.005f];"

Then it seems the scale is skewed at least. I tried values between 0.9 and 0.03 and didn't hear a difference in volume.

Posted 2 years ago #
PhilM
Member

Fixed my touch issue.

It looks like layers no longer need the manual calls to addTargetedDelegate/removeDelegate in the onEnter/onExit methods. Instead I had to add a -(void) registerWithTouchDispatcher method as used in Menu.m

Touch enabled nodes still need the calls. Everything else seems to be functioning nicely.

Thanks for all the hard work as usual Riq & everyone who's contributed...

Posted 2 years ago #
OldJames
Member

Riq, what was the motivation on killing the "setTransformAnchor" functionality, to be replaced by a relative system? Also, why not support both?

Most of the time it would be much easier to use a relative system, but on occasion (say to set an odd point for a rotation) it's going to be a real head-scratcher to calculate.

Posted 2 years ago #
riq
Key Master
@oldJames: a normalized anchorPoint simplifies the code, and fixes several bugs.
its very easy to obtain the same result using anchorPoint.

let's say you want your anchor point in pixel (283,117), then:
```
CGSize s = [sprite contentSize];
sprite.anchorPoint = ccp( 283 / s.witdh, 117/ s.height );
```
Posted 2 years ago #
tjweir
Member

I've branched my cocos2d-application template at GitHub for 0.8.0 here:
http://github.com/tjweir/cocos2d-application/tree/0.8.0

It's broken in about a million ways currently, I plan on fixing it up today.

Posted 2 years ago #
riq
Key Master

@tjwier: nice. I've added a "templates" page to the wiki:
http://www.cocos2d-iphone.org/wiki/doku.php/templates

Feel free to add any kind of info there.

Posted 2 years ago #
tjweir
Member

@rqi - will do.

Posted 2 years ago #

Obiwahn
Member

Sorry, no time.

In CocosNode method removeAllChildrenWithCleanup better first onExit and then cleanup? Else Timers won't get unscheduled.

Greets,
Obi

Better version: (?)

-(void) removeAllChildrenWithCleanup:(BOOL)cleanup
{
	// not using detachChild improves speed here
	for( CocosNode * c in children) {
		if( isRunning )
			[c onExit];
		if( cleanup) {
			[c cleanup];
		}
		[c setParent: nil];

	}

	[children removeAllObjects];
}

[edited by admin: added backticks]

Posted 2 years ago #

Obiwahn
Member

Another suggestion for Menu with overlapping menu items. Not sure with this.

Menu items should react to touches in the z order of the items. I.e. if an item covers another item it will be touched first (and not the covered item). So just reverse the search order:

-(MenuItem *) itemForTouch: (UITouch *) touch;
{
	CGPoint touchLocation = [touch locationInView: [touch view]];
	touchLocation = [[Director sharedDirector] convertCoordinate: touchLocation];

	// just search in the reverse order !!!!
	for( MenuItem* item in [children reverseObjectEnumerator]) {
		CGPoint local = [item convertToNodeSpace:touchLocation];

		CGRect r = [item rect];
		r.origin = CGPointZero;

		if( CGRectContainsPoint( r, local ) )
			return item;
	}
	return nil;
}

[edited by admin: added backticks]

Posted 2 years ago #

mho
Member

Thanks for releasing 0.8beta.

The TouchesTest demo doesn't work well, the touches are not detected 99% of the time on my iPhone 3G version 3.0 (it works smoothly on the simulator, though multitouches cannot be tested). Environment : xcode3.2+snowleopard+3.0targetOS.

Anyone else got this problem?

Posted 2 years ago #
tvalleau
Member

Sanity check from new user, please, if anyone has thoughts...

I'm just now starting my first project with Cocos2D. Given that there's a blank slate, and several months of work ahead, would you recommend starting with b8, (figuring that it will come along as I come along) or stay with 7.n (for all the obvious reasons?)

TIA

Posted 2 years ago #
tjweir
Member

@tvalleau - I'd pick 0.8-beta. Riq and crew move pretty quickly, and 0.8-beta is pretty stable for me.

Posted 2 years ago #
jd
Member

I've had no problems at all with 0.8 and since the graphics orientation works differently than prior versions (as well as other updates - including box2d and cocosdension additions), I would start there.

Posted 2 years ago #
riq
Key Master

@obiwahn: could you add your suggestion in the issue tracker ?
thanks.

Posted 2 years ago #
tvalleau
Member

Thanks folks.... I'm off to the races with b8.

Posted 2 years ago #
shw
Member

I have problem with landscape mode after 0.8 update.
This line crashes the app:
[[Director sharedDirector] setDeviceOrientation:CCDeviceOrientationLandscapeRight];
What is more interesting - if I replace it with:
[[Director sharedDirector] setLandscape: YES];
It's working fine. Strange thing is that setLandscape does the same thing that causes the problem.

Posted 2 years ago #
riq
Key Master

@shw: could you post the backtrace ? could you confirm that you are using v0.8-beta ? (open the file cocos2d.h)

Posted 2 years ago #

RSS feed for this topic

12 Next »

Reply »

You must log in to post.