iPad 3 + Storyboard = really slow performance

hi there,

i discovered that with the new iPad the performance of the storyboard API decreased dramatically. i have a eBook like app (swipe left / right to change scenes) and on the iPad 2 everything went smooth.

for example:

i have a button that opens another storyboard screen. simple as that.

reactiontime to change screens on iPad 2: almost immediately
reactiontime to change screens on iPad 3: 2 - 3 seconds

has anyone of you experienced the same issue?

cheers [import]uid: 42936 topic_id: 23529 reply_id: 323529[/import]

I think this may be related to an apparent problem with display.captureScreen on the new iPad (which is used for the animated transitions).

Have you tried changing scenes without a transition effect? The temporary solution to this may be to disable the effects for high resolution devices until Ansca can get to this. Since I don’t have a new iPad and I’m trying to submit my game this week I’d love to hear if you get this sorted out.

They have a lot on their plate at the moment but Danny said within the last few days that he was working on fixing some related things with storyboard. [import]uid: 87138 topic_id: 23529 reply_id: 94414[/import]

Thanks for posting this. I noticed the same slow speed across the board on the iPad 3. It’s not just storyboard, it is occurring with all scene transitions as well as animated sprites. Overall, the speed is incredibly slow, which is ironic because the new iPad should be 4 times the speed of the first one:) What’s going on? [import]uid: 8780 topic_id: 23529 reply_id: 94449[/import]

@Revaerie - Bingo!

I also have a storyboard app, and screen transitions are very slow on the new iPad. I removed the transition effects, and screen transitions are now lightning.

Thank you very much for the tip! [import]uid: 27976 topic_id: 23529 reply_id: 94450[/import]

yep, transition caused it and removing it makes it fast again.
i really cant afford to remove the “slideLeft” and “slideRight” storyboard-transitions right now, instant screen switching seems odd in an ebook… is there a ETA for this bug to be solved? i know you are propably stuffed right now with the release of the new iPad, but storyboard is a really important feature so i hope this will get fixed soon… :slight_smile: [import]uid: 42936 topic_id: 23529 reply_id: 94453[/import]

I am looking into these issues. [import]uid: 84637 topic_id: 23529 reply_id: 94464[/import]

I have similar results in my testing of the same app on an iPhone 4 and on the new iPad.

There’s a definite difference in storyboard loading times where the new iPad takes between 1 and 2 second longer to load a scene than the iPhone 4 does. (In a scene that loads a background image, about 5Mb of textures and about 4Mb of audio)

My best guess so far is that even though you might not implement dynamic image scaling for the new iPad, it makes sense that the new iPad/Corona will still be up-scaling all of your images anyway to work in that resolution, and this might be taking more time. Just a guess though.

Something which will help in my case is a feature request which I’ve submitted this morning where I can call a “storyboard.loadScene” to do pretty much everything EXCEPT goto the scene. I can then have control over when I load the scene, and then when I do the actual “storyboard.gotoScene” at least all the loading is done already.

I hope the speed issue is found and fixed. [import]uid: 126708 topic_id: 23529 reply_id: 94475[/import]

Just adding my +1 to try and get this issue solved quickly, as I have also noticed laggy storyboard transition effects on the iPad 3. Thanks, Ansca! :slight_smile: [import]uid: 27636 topic_id: 23529 reply_id: 94517[/import]

Storyboard delay issue has been addressed :slight_smile:

Look for the fix in the *next* daily build (after 2012.768 — most likely 2012.769).

[import]uid: 52430 topic_id: 23529 reply_id: 94615[/import]

thank you! :slight_smile: [import]uid: 42936 topic_id: 23529 reply_id: 94723[/import]

Excellent, thank you very much! [import]uid: 126708 topic_id: 23529 reply_id: 94725[/import]

New Daily Build just released adressing the problem with storyboard…

http://developer.anscamobile.com/corona-daily-builds/summary

nice responsetime, team corona! :slight_smile: cant wait to try it out [import]uid: 42936 topic_id: 23529 reply_id: 94755[/import]

mh close… responsetime when changing scenes is much better but it still takes up to a second to responds which feels odd…

and there is a new problem: while the old scene moves off the stage, it gets scaled in a weird way… like it gets zoomed in and moves to the bottom. this happens on the device aswell as in the simulator. ill post a quick screencapture video when i’m back in the office

[import]uid: 42936 topic_id: 23529 reply_id: 94758[/import]

Hi,

One more bug with build 2012.769.
Transitions for iPhone is wrong. When I use slideLeft sometimes new scene is moved left by about 50px off the screen (In my case a new scene contains scrollView).
Also slideUp and slideDown have some zoom effect.

Everything is OK with build 2012.768

Tested on iPhone4.

P.S. Sorry for my english :frowning: [import]uid: 123747 topic_id: 23529 reply_id: 94768[/import]

Yes, new problem with Storyboard, “previous scene” gets scaled and zoomed before leaves the screen …

Hej, Marijo, odakle si ? [import]uid: 13367 topic_id: 23529 reply_id: 94774[/import]

Can you guys put together a extremely simple example with any assets needed to reproduce the problem and email me it to : danny [at] anscamobile.com

Thanks! [import]uid: 84637 topic_id: 23529 reply_id: 94778[/import]

it seems the error only occurs when the direction of the scene leaving is either to the LEFT or TOP… can anyone confirm?

UPDATE:
nope… it seems that particular scenes have problems when moving offscreen regardless of the direction they are going [import]uid: 42936 topic_id: 23529 reply_id: 94788[/import]

Issues I’ve noticed with Storyboard in build 769:

  • When using “crossfade,” the scene that is being transitioned away from gets zoomed and stretched in a strange way so that the crossfade effect doesn’t look right. You can see the distortion happening to the scene during the transition, and you can also see the black Runtime background when the stretching begins.

  • When I use the “slideUp” effect, not only does the new scene get stretched while it is sliding into place, but the whole new scene is offset so that only the bottom 40 or so pixels are visible once the transition is finished. This is on an iPad app in landscape orientation. Essentially the transition is overshooting it by 90% of the screen’s height.

Thanks, Ansca, for the quick work on this so far…hopefully we’ll get these remaining bugs ironed out just as quickly! As it stands, I think I’m going to push an update on my latest app using build 767, even with the slow transition effects, and then push out a second update once we get these Storyboard issues settled. Slow transitions are bad, but not as bad as only seeing 1/4 of the app! :slight_smile:

-Jason [import]uid: 27636 topic_id: 23529 reply_id: 94803[/import]

problem occurs on my iPad 3 and iPad 2, no matter wich transition effect is used… [import]uid: 42936 topic_id: 23529 reply_id: 94807[/import]

Update (regarding transition bugs):

The storyboard transition issues that were introduced after the “delay bug” was resolved are now fixed. The changes should be in one of the next few daily builds (keep an eye out for “Storyboard” in the daily build changelogs).

EDIT March 21, 2012:

We just checked-in an important storyboard update that should fix the transitioning bugs, and also introduces a couple new features. Here’s a description of the changes that will be in the next build (after 2012.772):

  • Fixed bug where certain transitions would behave incorrectly if there were off-screen objects.

  • Added new function: storyboard.loadScene( sceneName [, doNotLoadView] ), which is similar to storyboard.gotoScene(), but no transition is initiated (useful for pre-loading scenes).

  • Added two scene events: “enterBegan” (dispatched before scene transition occurs) and “exitEnded” (dispatched after scene has exited).

And for those interested, these updates address ticket casenums: 12827 and 12954

Once again, these changes will appear in the build that posts after 2012.772. [import]uid: 52430 topic_id: 23529 reply_id: 95010[/import]