Post by Merijn in New Feature Games Devlog

libGDX Jam - Powered by RoboVM & Robotality » Community

Viewing post in New Feature Games Devlog

T.minus something...

He - I seem to have found why the android version has such a low performance!

The number of objects in Overlap2d is apparently very important. In the current version I am tiling the back ground images - especially the border blocks. In the large space map this gives me aprox 2500 objects. Apparently the Overlap2DRenderer is not very happy with that. (Even though tiling should actually be really fast). I think they where thinking about a tiled extension to Overlap2D. Until that is fixed - or I write my own renderer - I will create new borders. Just creating new borders should reduce the number of objects from around 2500 to aprox 200. And this ups my FPS in Android from around 20 to a nice 60 fps. :)

In the next couple of days I will try to get this in.

In the meanwhile - have a look at the windows version and try this game out!

http://itch.io/jam/libgdxjam/rate/50929

conversion78 years ago

What about convertation overlap objects to scene objects https://github.com/DmitriyL/Feed-the-space/blob/ma... ?

It looks like you are reimplementing libgdx scene.

Merijn8 years ago

Hi them.

No - I am not doing anything that complicated. (Although that code does look interesting :) I just noticed that the performance of Overlap2D drops on Android when I have a lot of entities. This is even true if I switch off the back ground layer and these are not rendered at all.

Now in order to solve this I will remove the composite objects that make up the border shapes in my scene. I will then replace them with simple much larger textures. So I will end up with a lot less entities.

I was just thinking it would be nice to have a tiled option in Overlap2D. The idea behind Tiled is that the textures are send to the graphics buffer once, and then stencilled when needed. That is a faster technique, but obviously only works when you can simply copy the textures again and again. I don't think the current Overlap2dRenderer can handle that. So for now my idea is to stick with a limited set of textures.

In any way - this game just utilizes the standard functionality of Overlap2D, Ashley, Box2D and Spriter. I am not sure about my implementation of the ECS. (So let me know what you think :) As I said before I think it would be good to have more 'live' examples of how this can be best used in games.

conversion78 years ago

Hi, I see Overlap2dRenderer is doing the job, but it looks like it's doing too much for one system and at the same time like it could be difficult to split its logic on sub-systems. I could just recommend (1) convert everything possible to libgdx/bod2d domain objects (sprite/color/lighting/collisions...) and (2) assign component-system to these objects. I'm sure it's a big chance you will want add more functionality in scene renderer... into Overlap2dRenderer.