• Runtimes

  • Question about performance on low end mobile hardware

    inglés

Hi, question about performance of these runtimes. How intense these runtimes are ? I am planning a project where I would have hundreds of animated graphics assets and now I am trying to figure out how big chunk I am going to do with spine. There would be probably maximum on 30 or so animations running on screen simultaneously. (mostly simple skeletons with little deformation. maximum of 10 characters with complex skeletons). I have almost zero experience with spine. I just finished a test project and I was able to make it all function and I like it very much how spine works. I am just wondering how much I can drop this stuff on screen before low end hardware starts choking.

I haven't yet decided if I go with unity or godot. This is very much in planning stage. and I will probably do pilot versions with both engines.

Thnx

Related Discussions
...

I do understand that this is very setup / hardware specific, but if someone has some experience / indication on of how many relatively simple animated characters I could have running on the screen simultaneously on 5 year old ordinary tablet/phone.

I will make my own testing offcourse.

@ProgeGames While the following text will probably not add much information, we can only say that it unfortunately really depends on your use-case and needs to be measured on your target device. You need to take into account how many vertices, bones, constraints, draw-calls per skeleton (due to multiple atlas pages), and so on you will need for each skeleton. Regarding draw calls it's also important how many different skeletons there are, whether it's 30 different skeletons or 5 skeletons of 6 skeleton types (all sharing a single atlas texture and material), with the latter leading to fewer draw calls.

You can have a look at the Performance section of the spine-unity FAQ to get an idea of what might be more costly, so that you can test with skeletons that yield measurements as close to your final assets as possible.

Of course, we're always happy to hear from real-world cases, if anyone wants to share their experience regarding their game. The Showcase section of the website shows what existing games have achieved using Spine.

Each engine has its own advantages and disadvantages, so the choice depends on the specific requirements and needs of your project. Unity has a broader toolbox for 3D graphics, including a more advanced animation and character management toolbox. Unity also supports a large number of platforms, including mobile devices and web browsers, and has a large developer community. Godot, on the other hand, is more flexible in use, easily scalable, and adapts easily to different platforms. Godot has an intuitive interface, making it easy to create scripts and quickly prototype ideas.