Android export optimization

[Matt]

Hi, im making an android game using nape physics (FlxNapeSprite) and i have about 110 of NapeSprite objects on the game and it seems to lag. Is there any known optimizations for android build ?  I'm already using texture atlas for all the sprites , is there anything else i can do to make it go faster and any function/features i shouldnt be using on android build . Also is it possible to display fps on the android devices ?

 These stats are from Windows export

[Thom Sip]

Not sure about the optimizing, however you can get the FPS like this:

In Create:
FlxG.fixedTimestep = false;

in Update:
YourTextField.text = "Fps " + (Std.int(1 / FlxG.elapsed));

Op donderdag 19 maart 2015 12:04:34 UTC+1 schreef Matt:

[Gama11]

That's quite a roundabout way to display FPS, you could just make the debugger visible:

FlxG.debugger.visible = false;

// hide the other debugger windows manually if they take up too much space

FlxG.game.debugger.console.setVisible(false);

FlxG.game.debugger.log.setVisible(false);

FlxG.game.debugger.watch.setVisible(false);

or access the fps value directly:

var fps:Float = FlxG.game.debugger.stats.currentFps();

[Matt]

Thanks for the replies Thom and Gama about FPS display. Only Thoms fps display works , when i try Gama's code it just says that debugger doesnt exist.

And about optimization i managed to cut update time by 50% using my own simple hitbox colision detection ,  FlxG.overlaps was very costly it seems on android.

[Gama11]

You need to compile without FLX_NO_DEBUG / in debug mode to access the debugger.

I thought you were using Nape? You shouldn't need FlxG.overlaps() in the first place then.