Total Posts: 261
Joined: September 08, 2011
|
Desktop performance is always going to be considerably better than on the device. Simulator performance is a bit random - sometimes slower, sometimes faster. In both cases they won't represent the final performance.
If it's faster on the simulator I guess there is a CPU bottleneck involved:
Avoid software-bound features (filters, blendmodes, masks) which will force things to be composited in software and obviously kill the performance on mobile.
Then performance will depend on the size of the elements and if you are using batching to draw them (Tilesheet). Batching greatly improves performance.
Also definitely use ENTER_FRAME and make sure the elements movement is independent of the framerate - ie. move elements according the the elapsed time. Tween engines (like Actuate) do it well and keep everything smooth even if the framerate would fall dramatically.
Related (shameless but useful plug):
http://speakerdeck.com/u/elsassph/p/haxe-nme-vs-the-world... (check slides 23+)
Posted on April 16, 2012 at 2:31 PM
|
