10-29-2012 03:21 PM
Yes it definitely seems like the displacement map is causing a performance hit. A few other things that I would consider is toning down the number of asteroids orbiting the planet. Alpha and blur effects are also very expensive. I would try disabling those in your tweens and see if your performance goes up.
10-29-2012 03:24 PM
Thanks for taking a look Dustin. I know there's some stuff in there that can have a high impact on performance, but on the Playbook I'm only testing out the main menu. So with the displacement as well as the buffer 'motion blur' turned off, there's only the logo, the background, the planet and the menu buttons being drawn. This is what's confusing me so much...
10-29-2012 03:41 PM
Ok well the only thing that comes to mind then is to keep stripping down the code until you find the culprit. If you do find out what is causing the performance hit please let us know
10-29-2012 03:49 PM
10-29-2012 04:07 PM
Was looking into it a bit more. You may have already read this post but it has some good information - http://www.andymoore.ca/2012/01/how-to-improve-you
10-29-2012 08:38 PM
So I created a very simple app with just a buffer texture, a text field for the elapsed time and a loop drawing out a 1x1 texture in randomized points across the screen.
The app runs ok with a handful of sprites on screen, but by the time you have ~200 or so the framerate is at 20fps. I then tried the same app with GPU rendering enabled and the performance actually decreased! It was hovering around 24fps with nothing being drawn.
I suppose 200 sprites is quite a few, and maybe I was just expecting more from the Playbook. But this is a very simple app with no logic involved even, just simple rendering. It just seems like a device with such highly touted Flash performance would fare better than this.
10-30-2012 09:58 AM
Last bit of help I can provide is a link to a performance tuning presentation by Andy Hall of Adobe- http://www.slideshare.net/fenomas1/flash-performan
If you have seen this I'm not really sure what else to recommend other than to ask you to wait patiently while we update our runtime. We're working with Adobe on this right now and will post information to our roadmap as soon as we have more details - https://developer.blackberry.com/air/download/road