Performance issues on mobile (iOS) - Starling runtime

michael_p

Hello there,
We're having performance issues with our mobile game.
You may download Web demo (both debug and release builds included) from:

https://dl.dropboxusercontent.com/u/132 ... kFinal.zip

You will notice that the debug version is running in less FPS than the required 30 FPS.
The release build does not suffer the same issue.
The mobile release build has the same issues as the web-debug. (and even worse)

You may download the full Spine project from:

https://dl.dropboxusercontent.com/u/132 ... roject.zip

Can you suggest any changes that may improve the issues above?

Thank in advance,
Michael P

michael_p

Søren

The combination of 100+ bones multiplied by 63 (the amount of ghosts you have in the debug) is really heavy. That's more than 6000 bones.
Looking at the project I'm unsure what many of those bones are there for ?
At the same time you also use meshes which are heavier than regular quads, I haven't checked for how many of your attachments you use meshes though, but the body looks like it has a fair amount of edges.

Pancho

At first sight too many draw calls in SpineBenchmark. To check for you:

do you use a single texture atlas for all objects?
do you use a newest Spine runtime (it contains a fix for low performance meshes processing)?

michael_p

Shiu & Pancho,
Thanks a lot for your thoughts/suggestions.
We are working on optimising our Spine project by reducing the number of bones where possible, and even breaking the atlas into multiple for various elements.

Michael P

mfedorov

O my God. Do you really need all these bones? So easy character and thousand bones structure.