Skip to main content
Known Participant
October 14, 2011
Question

Air 3.0 poor performance vs 2.7 on ios (user error?)

  • October 14, 2011
  • 3 replies
  • 2168 views

I'm not sure what is goin on here, but when I published my app on 3.0 its just bogging down on the iPhone. Everything is going slower. It was running great in 2.7.  I've compiled builds via cmd line, and in flash 5.5 (with 3.0 overlay).  No difference.  Is anyone else running into this problem?  I'm rendering in gpu mode, and the app was running considerably faster in 2.7. 

Any insight on what I could be doing wrong is appreciated.

-dis

This topic has been closed for replies.

3 replies

Known Participant
October 17, 2011

After a weekend of investigation, I've determined that this issue was on my end, and not Adobe's. Your off the hook!   It was a weird combination of a lot of little things as well as a device that was running badly.

I really appreciate all the feed back, and will log bugs as I see them.  Did get some usefull info from the stage and color changes to boost speed out of this particular thread. Thanks

-dis

Participating Frequently
October 14, 2011

I'm also getting similar results. Upgraded from 2.6 to 3.0. The performance is exactly the same on my iPad 2 and iPod 4th gen, but when I tested on an iPad 1 I was noticing a weird framerate skipping issue. Basically I have animations with 5 looping frames and in AIR 3.0 it seems to skip one of the frames every now and then, meaning that the animation never quite finishes before it loops. I have many incidences of these objects, often some will play fine but the others will skip frames.

Didn't run into any issues like this on AIR 2.6, everything runs nice and smooth.

Participating Frequently
October 14, 2011

Hi,

I am sorry you are running into this problem. What is the value of stage quality for your app? Could you set it to MEDIUM or HIGH and see if the performance improves? Since you have a reproducible case, I would appreciate if you can file a bug at http://bugbase.adobe.com with the source project, steps and other details. Once you have logged the bug, please post the number here so that others who are affected can vote/comment.

Thanks,

Sanika

Participating Frequently
October 14, 2011

You can also try adding <colorDepth>16bit</colorDepth> as a direct child of the <android> element in your app descriptor. AIR 3 switched to (24+8)-bit color mode on Android.

Inspiring
October 17, 2011

Thanks Joe Ward!!!

I just got a slight performace boost by switching back to 16bit color, in my situation you cant tell the difference anyway.

Great tip!