Android phones from 2010 showing 2 FPS when using Box2D

totebo

Hi all,

When testing my game prototype on a range of phones all but two show good FPS at around 55-60. Two of them, however, run at around 2 FPS. They are HTC Desire Z and HTC Desire. The prototype is a pretty standard implementation of Box2D with 10 or so bodies of varying complexity, with no graphics attached yet.

Intrigued by this result I installed Angry Birds, which famously uses Box2D, on both phones. It runs fine on both of them with no noticeable slowdown.

How can this be explained? And, more importantly, is there something to look out for to get these moderately old phones up to speed?

Cheers,

Niclas

iforce2d

Are you displaying the debug draw shapes? I noticed this same problem with one of my phones from the same period, when drawing a lot of circles with the debug draw. When displaying texture sprites instead of primitives though, it was fine. I guess it is better optimized for textures than rasterized geometry. Quick way to check if this is the issue would be just to run the physics without displaying anything.

ar2rsawseen

What @iforce2d could be true.
The oldest device I have is a LG P500, but it usually runs the box2d physics apps normally. And debug draw really drains it.

You can try this game, also made with Gideros, to check if it runs ok or not:
https://play.google.com/store/apps/details?id=com.jenots.mashballs

totebo

I'm only using debug draw at the moment, which I assumed would be a lot less of a drain than bitmaps. I tried Mashballs on one of the devices (HTC Desire Z) and it runs very smoothly. Thanks for the heads up guys. I like solutions only involving commenting out one line of code.