Copy link to clipboard
Copied
I'm sorry that I haven't debugged further. I hope you are aware of performance issues regarding AIR 15 beta on iOS. I'm using the 20th of August version. The app works fine on simulator (except visual artifacts on bitmaps) and on Android. On iOS it's reported to be very slow and crashes in a situation, which I can't think of being special.
Using GPU renderMode, timeline animations with plenty of bitmaps.
Copy link to clipboard
Copied
You cannot get away with GPU mode and a timeline animation where every frame is different. If you are animating symbols, where the symbol is the same one from frame to frame, then it should work. But if the scene is constantly changing, the GPU memory gets filled up quickly, and AIR is having to replace those textures with new ones.
If the area of the screen that is animating is small enough, and if you're just doing 24 fps, Direct mode can give good enough performance, without the GPU memory issues. Even then, iPad Retina may not perform well enough, but there's a way to exclude iPad 3 from the High quality mode, and then the performance is better.
Copy link to clipboard
Copied
The animations are quite optimized, so it's not that. Everything runs fine with AIR 14 or AIR 15 on Android, with old hardware. I try to dig deeper into this when I have more time.
Copy link to clipboard
Copied
I know this is no longer beta, but just to let you know that official AIR 15 version fixed some issues, not all. The rest were got fixed with "-useLegacyAOT yes". So it has something to do with the packaging the app in a wrong way. The places where the app crashed the most used MovieClips on timeline.
Copy link to clipboard
Copied
Hi,
Thanks for reporting the issue. Could you please send a sample app to govindag@adobe.com ?
Thanks
Govinda Gupta
Copy link to clipboard
Copied
Thanks for replying. Unfortunately our app is a monolith and the bug affects parts of it, which are difficult to separate. I can give you the undocumented project files or I can try to reproduce the bug in a test project. I believe the bug is somehow related to having multiple MovieClip subclass definitions on different SWC files, and instantiating them on timeline.
Copy link to clipboard
Copied
Hi,
It would be helpful to have project file with action script code. Please send the data to my email id govindag@adobe.com<mailto:govindag@adobe.com>.
Thanks
Govinda Gupta
Copy link to clipboard
Copied
Hi Govinda,
I'm getting back to this thread, because I noticed that there's a new AIR 16 beta, which doesn't any longer support the old compiler. I had critical issues with the new compiler during AIR 15 beta, which you were able to reproduce. Can you tell if these issues have now been fixed? I can't test the new AIR 16 beta, since I don't have a Mac, which I understood was a requirement.
Copy link to clipboard
Copied
Hi kaveri2,
You can compile iOS on PC with the latest Air beta.
You just can't compile 64 bit.
Hope it helps.
Copy link to clipboard
Copied
Thanks, downloaded and confirmed the export release building is quick, even with "-useLegacyAOT yes". Initial tests seem to work fine, so maybe the issue has been fixed. Unfortunately I'm not testing with exactly same code anymore.
Copy link to clipboard
Copied
Hi,
We fixed lots of performance issues in new compiler recently and as of now we don’t have outstanding performance issues.
If you find one, please share.
Thanks
Govind