A fast, easy to use, free, and community supported 2D game engine
Can somebody tell me what significantly changed from revision 1434 to latest revision? Because when I updated, everything suddenly stopped deallocing (scenes, layers, ...). Everything worked nice with r1434 and I updated bc of few changes with FontLabel, but now my game can't run anymore?
Suppose it's something new with actions or schedulers but I can't figure it out...
Thanks
bradparks
Member
I can't tell you exactly what changed.... but you can look in SVN and see for yourself what the differences appear to be here:
http://code.google.com/p/cocos2d-iphone/source/list
You can browse it by revision #, so you should be able to figure out what's changed from there...
Already did that but it's pretty confusing to track every single change and figure out what could cause the problem. I already told that, by looking through source changes, I think it's something about actions, but couldn't figure it out what exactly...
from r1434 to "head" there were lot of fixes, but basically internal action fixes.
try to be more specific about the code that doesn't work anymore.
basically if you have coded you own action, you should do this now:
// Old interface
@implementation MyAction
-(void) start
{
}to:
// New iterface
@implementation MyAction
-(void) startWithTarget:(id)target
{
[super startWithTarget:target];
}If something doesn't work with that change, please open a bug attaching the code that reproduces the bug. thanks.
Uh, that would be pretty tough. I am in the latest development stage, and I would need to strip the code pretty much to locate the actual problem. I didn't subclassed nor made any actions. Just used regular stuff. All actions are done through Action Manager. I'll try to reproduce the problem in some simpler code.
shadaz
Member
Reading your symptom "everything suddenly stopped deallocing".. Im not sure if this helps but I had an issue where everything stopped deallocing and it was because I was using an NSTimer or another method that implemented NSTimer, I switched all those calls to the cocos scheduler and my deallocs started working again.
@crmagic: there might be a memory leak in the new code, but according to my tests everything is being dealloced OK.
@shadaz I don't use NSTimer anywhere in my code
@riq
Wow, did anybody of you actually see the performance drop from version 0.8.1 to 0.8.2? I never use fast director, but in v.0.8.1 I used animation interval of 1/240.0f so I suppose that somehow dispatched my events pretty faster.
Ok my latest game stats:
v0.8.1, no fast director, anim interval 1/240: I am getting 59-60 FPS, never below because I optimized my code pretty much
b0.8.2, no fast director so I suppose it's NSTimer type used. Only changes I made in code is convertCoordinates to convertToGL in 2 places: I am getting 30-60 FPS. It's so obvious that it hurts.
I suppose with introduction of new Director types you limited basic director type to 1/60 right? I even tried with DisplayLink but it's way slower than old v0.8.1 standard director with 1/240 anim interval...
I'll revert everything to v0.8.1 until I understand what's happening.
Riq, can I please send you 2 same projects on email so you can see it for yourself? Maybe it's something important that should be addressed. Only difference in projects is v0.8.1 and v.0.8.2 used. Also if you're interested I can send you even the 3rd project, with only difference that latest revision is used and scenes/layers don't get dealloced...
I am using parallax in the game, and touch dispatcher to move the main character. But differences in FPS are more than obvious.
Thanks
@crmagicxxx: sure, send it to my email. Please detail what should be the expected behavior.
Thanks Riq
Sent you email
@Riq
Thanks for fast response. I am glad if it helped to find a bug in actions. But I am not glad I lost whole day trying to figure out what's wrong in my code :)
Also, for everybody else... If you see FPS drop when you updated to cocos v0.8.2 it's because of new default pixel buffer format. So revert it to 565 from 8888 and it should help. Thanks Riq for pointing out this...
Regards
yes, probably I will rollback the RGBA8888 change for v0.8.2
You must log in to post.