Arm7 performance issue

After Apple only accept games build with arm7, I compiled my new app with this requirement. After I’ve done this, my app has huge performance problems (tested at Iphone 4). With arm7 my game has a extrem slow framerate, but with arm6 only, it run smooth(as it should :wink: )
At the moment I only use many planes with textures on it (2D like)+ 1 particle system (max 5 emission) + 1 lightsource with a flare effect and no 3d modles.

I already deactivated the lightsource + the particle system, this helped a bit, but the performance is far away from the arm6 build. I dont have a clue what I can do to optimise the performance. Maybe its a Arm7 bug?

Draw Calls: 43
Tris: 5.4k Verts:3.6k
Used Textures: 16 - 6.4MB
Render Textures: 0 - 0 B switches: 0
VRAM usage: 3.1MB to 9.9 MB (of 256.0 MB)
VBO Total: 139 - 356.3 KB
Visible Skinned Meshes: 0 Animations: 0

Anyone has a hint for me?

UPDATE: Now I’ve tested the Arm7 build at my Iphone 3GS and the performance is the same as the Arm6 build (runs smooth). Could it be that the high resolution of the Iphone 4 is the matter for this huge framedrop?

Hmm, didn’t know that apple accepts only arm7 builds. are you sure? does it mean we can’t do games for 3G anymore? or it means we need to compile arm6+arm7?

if you want to target pre 3GS you must compile ARMV6 or ARMV6 + ARMV7
But nothing prevents you fromt targeting ARMV7 only if you wanted to.

What you take the hit from is not ARMV7 targeting here but OpenGL ES 2.0
To just get ARMV7 without OpenGL ES 2.0, go into the AppController.mm and disable the define thats right after the initial comment block which controls if it is meant to use OPENGLES 20 or not and set the define to 0 instead of 1

This, and probably targeting native resolution (just in case)

@dreamora
OKAY! Thats it! Thank you! I simply deactivated OpenGL ES 2.0 like you wrote, and know everthing works fine :slight_smile: BORAY!

HD resolutions definitely hit as well :slight_smile:
But the resolution should be independent of ARMV7 targeting, shouldn’t it?

yes, missed

part. 8)