Android performance with Haxeflixel 4.4.0
I was so excited with the release of the 4.4.0 version that updated to it without thinking twice. The upgrade went smoothly.
The main target of the game is Android, and the performance of new builds using 4.4.0 is pretty bad. The framerate drops from 60 (with v4.2.0) to 25-30ish fps in v4.4.0. The slowdown is pretty noticeable while playing. Other targets, as html5 or windows/mac native are not affected by this slowdown.
I'm not using any special graphical features, shaders, blend modes, or even tilemaps. It's just FlxSprites with scaling and some minor alpha and FlxBackdrops. FlxTweens, also.
What should I look for in order to restore the 60fps mark? Are there any specific things that should be done differently in 4.4.0 than 4.2.0?
What OpenFL / Lime versions are you using? If not latest, could you try updating?
I did the upgrade using $ haxelib update, and now I'm working from a clean installation.
$ haxelib list
Same result in both cases.
I'd be curious to know what results you're getting with the Tilemap branch: https://github.com/HaxeFlixel/flixel/commits/Tilemap
It's rather experimental / unstable, but it uses a different renderer (Tilemap instead of drawQuads), so there's a chance you'd see an improvement.
I just tried it. I had to disable FlxBackdrop rendering from flixel-addons, though.
On desktop it's mostly the same although there are some graphical glitches with bitmap text characters.
On mobile there's a slight speed bump (35-40fps instead of 25-30), but the scaling makes everything blurry (this does not happen on desktop).
Is there something I should look for in my code (like, I don't know, avoid using FlxBackdrops or scaling or something?) that may be causing problems?
@rafadelahoz You could try disabling particular "features" (text rendering, large sprites, etc) to try and isolate what exactly is making it slow. Not aware of anything in particular that would be slower with new OpenFL 8 right now.
I'll try and do that. I will report if I find something interesting.
Thanks for your answers!
Hi rafadelahoz on what version of Android and android device do you test the game?
I have the same problems basically.
the game lags very badly basically unplayable.
When it freezes there are no traces from the update function.
Tested on Android 4.2.2, device with 2GB ram.
The same game build with
on the same device works flawlessly.
I tested on a wide range of devices, from android 4 to 8 and low to mid-high hardware specs.
I got the same results, specially very low framerate when compared to builds with the older tools. I got no actual crash or frozen status.
Trying to find problematic elements by disabling things and features isolatedly yielded no results.
I have returned to the flixel 4.3 environment, but it seems Google Play will not accept android-19 builds from August. Nice situation!
I'll keep investigating (after the game is published!)
I'm not sure if this is a possible reason, but I noticed with cpp builds when running full screen I get lag, too. This is with latest libs.
Just a hunch here, but maybe it's something to do with the full screen implementation??
For simple games with simple collision, I was able to set fps to 30 for reasonable game play. For my bigger game with lots of collision action, it's not able to handle the collisions without missing sometimes.
I hope someone can figure this out. I wish I knew more so I could.