A fast, easy to use, free, and community supported 2D game engine
Hey guys i just got feedback from apple that they rejected my ipad app.
It looks like it is really slow.
In the simulator it runs at 20 fps .It is not a game, it is a simple app. Even so, it does not take a lot of time for, say, fading an image and showing a couple labels. But according to apple that takes like 20 seconds on their tests...
they told me this:
For example, when the user taps "Information", it takes about 3-5 seconds to open the information page.
When the user taps "Continue" to exit, it takes 10-20 seconds to close the page. Same applies when the user taps "Preferences" and exiting "Preferences".
That information page is only a layer with an image that fades in and when touched fades out and gets removed.
In simulator it looks jerky (because of the 20 fps) but it surely does not take 20 secs to o away...
conor
Member
The 1024x768 images seem to really smoke the device. I removed the background image from my game and went from 15 fps to 45fps-50fps. Are you preloading the images before animating them? I'm just wondering if it's the actual animation taking that long or if there is a delay to read the images off disk.
gaminghorror
Member
@pablo: Ouch!
Is there any way you could share the offending code? Maybe we can get an idea what's causing this. I'm also on the 27th deadline and don't want to be rejected. But for the iPad app i had to add several CCLabel (not Atlas!) so i'm a little worried. I know from iPhone development that they can really suck the life out of your app.
Uh, I am also afraid of those big images loading times. I wonder how fast is simple transition between scenes with full 1024x768 backgrounds if they are not preloaded...
Btw, gaminghorror, CCLabel is only expensive at creation time. Once label is created, it's like any other sprite on the screen and it renders as fast as any other cocos node with the same texture size. And, if you decide to change the text of the CCLabel, you're going through the same process of re-creating the texture. That's why people are avoiding them. But if you just have text sitting there, it's perfect and much easier than making all those bitmap fonts...
@pablo: are you using "thumb" code? if so, disable it. How big are your images ? What pixel format are you using ? try to avoid 32-bit textures when possible.
@gamingHorror: Yes of course!
When i touch the corresponding menu i create an instance of the following class, according with what i undertood from the mail, this takes more than 5 sec to show and 10-20 to dissapear :S
here it is
#import "About.h"
@implementation About
-(id) initWithTheGame:(GameLayer *) game
{
if ((self = [super init]))
{
self->theGame = game;
[theGame.parent addChild:self];
theGame.isTouchEnabled=NO;
ccColor4B col={0,0,0,155};
back = [CCColorLayer layerWithColor:col width:720 height:980];
[back setPosition:ccp(24,22)];
[back setOpacity:0];
[self addChild:back];
CGSize size = [[CCDirector sharedDirector] winSize];
CGPoint pos = ccp(size.width/2,size.height/2);
about = [CCSprite spriteWithFile:@"about.png"];
[about setPosition:pos];
[about setOpacity:0];
[self addChild:about];
[self openMe];
}
return (self);
}
-(void)removeComp
{
//[theGame->menu setIsTouchEnabled:YES];
[self.parent removeChild:self cleanup:YES];
}
-(void)closeMe
{
[[BiometricsAppDelegate get].soundEngine playSound:3 channelGroupId:2 pitch:1 pan:0.0 gain:1 loop:NO];
[self->back runAction:[CCSequence actions:[CCFadeTo actionWithDuration:1 opacity:0],[CCCallFunc actionWithTarget:self selector:@selector(removeComp)],nil]];
[self->about runAction:[CCFadeOut actionWithDuration:1]];
theGame.isTouchEnabled= YES;
self.isTouchEnabled = NO;
[theGame->menu setIsTouchEnabled:YES];
}
-(void)openMe
{
[self->back runAction:[CCFadeTo actionWithDuration:1 opacity:130]];
[self->about runAction:[CCFadeIn actionWithDuration:1]];
theGame.isTouchEnabled= NO;
self.isTouchEnabled = YES;
[theGame->menu setIsTouchEnabled:NO];
}
- (void)ccTouchesBegan:(NSSet *)touches withEvent:(UIEvent *)event
{
UITouch *touch = [touches anyObject];
CGPoint location = [touch locationInView: [touch view]];
CGPoint convertedLocation = [[CCDirector sharedDirector] convertToGL:location];
CGPoint loc = [[CCDirector sharedDirector] convertToGL:location];
if(loc.y<260 && loc.y>220)
[self closeMe];
}
@end@riq: i have a 768 * 1024 background image, an many other big images... i wasn't unchecking compile for thumb, doing that does not chenge anything in the simulator. Maybe on device is a different thing. I will try resubmitting with that...
Hope it works for you.
I'm interested to see how many apps actually come out on launch day. And what percentage are of what type.
Thanks, i think small developers will release simple apps, since unless you somehow have a device it is imposible to get a somewhat complex game playing...
@pablozulz55
check out the other thread just started about the background images. I tried it out in my code. went from 15fps to 30fps...
http://www.cocos2d-iphone.org/forum/topic/5196
this other rejection issue is weirder
Issue 3: The scanning starts without the user putting his/her hand on the screen. If the user leaves the application without any user input for extended period of time, for example, 3-4 minutes, scanning starts automatically.
(it is a simple app, you touch a part of the screen and something starts happening)
There is no way that is happening (unless there is a serious bug somewhere not in my code that generates a touch without touching the screen.
Also no wonder they take some time reviewing apps... what are they doing with the app open and not touching anything for 4 minutes? :P
@pabloruiz55 probably waiting to see if it leaks itself to death within a specified time period :s
Hahaha yeah... i just submitted again. Could it be they test with a faulty device or something? :P
I little while ago, i submitted a pinball app, it worked ok in iphone 3g,3gs,ipod. But it was rejected because they said that in iphone3g when the game started, the ball was stuck in a part of the screen. I checked the code no errors, checked in a couple of 3gs phones again no errors.
Submitted again, same rejection. Changed nothing, the 3rd when through...
Just hoping i get lucky again, since there is no way for me to try anything else without a device.
@pabloruiz55 haha, hope you have sent at least a recompiled version with different cksum ;)
@pablo: Thumb MUST be disabled. It doesn't modify the performance on the simulator because it only affects the ARM code, and when you compile for the simulator, it compiles Intel code.
Did you start the project using the cocos2d templates ? The templates create "thumb-disabled" projects, if not, it is an important bug.
@riq: yes, i started them with the template (the one with no physics) and they do start with thumb checked.
According to Apple, you should only disable Thumb in the following case: Floating point intensive code on the ARMv6 architecture because the ARMv7 has floating point Thumb instructions.
I presume you are building for ARMv7 since it is for iPad. And in that case you should enable Thumb (which is actually Thumb-2).
Supporting information here:
http://developer.apple.com/iphone/news/archives/2010/march/#techtalks09
Mastering OpenGL ES for iPhone Part 1
It starts talking about this at approx 36minutes, and specifically talks about the Thumb-2 for ARMv7 at about 38:30
Blue Ether
Member
This is really only an issue if the apps is iPad specific, since it would otherwise be a simple 480x320 iPhone app running on iPad in its compatibility mode. So, there's no "I've got no device to test on" unknown factor.
Optimized will still run on arm6, but if you're building for iPad with 3.2 then, for the moment at least, it will always be running on an iPad with arm7. Remember, there's no support yet for having the SAME app run as a native iPad app and a native iPhone app.
well, as of right now i have another app rejected, but this one only mentions it is bacause of the icon, they don't like it.
That app also has huge backgrounds, fades in and out lots of stuff, creates many bitmaplabels at runtime...
So.. either that one runs fine, or they saw the icon and rejected it inmediately without trying it out, or... don't know...
@pablo: The project created by the template might have the "thumb" checked, but the targets should have them unchecked
@blueether: Yep, it was just the image "was not suited for ages 4+"
has anyone else submitted an ipad app and gotten any feedback?
You must log in to post.
