Slick Forums

_________________
: bytecode-weaving antiboilerplate lib for artemis. | : bugfixing and performance optimized fork.

Sorry for hijacking this thread, but it deals more or less with the problems I'm having with my game. I also read the sticky post about not asking questions regarding game design, but I see a few posts here about that, so I'll try

I'm using a tilemap in my game like the OP, although I only have one layer. My problem is updating only the section of screen you're currently seeing. How do you go about this with atemis-odb? To be clear, I have a tilemap of, say, 500x100 tiles, but my camera only covers 32x24 at any given time. How do I make the systems update only those? Preferably, I'd like not to fill a collection first and then pass that collection to every system, as I see this as not performant, but maybe that's is my only option with an ES approach?

Thank you in advance!

_________________
: bytecode-weaving antiboilerplate lib for artemis. | : bugfixing and performance optimized fork.

Why don't you want to create a collection though? If you reuse the same instance, it doesn't incur a higher cost to pass a collection than any other object. But it sounds somewhat headachey since you'd need to make sure that all entities that are cull-aware have matching aspects - or you'd need to allocate a Bag/collection for each unique aspect.

Without being familiar with your code, I'd consider having a culling system that populates entity ids into a BitSet; interested systems would then check if the entity.getId() is present in the bitset before processing (extend EntitySystem and do the check inside EntitySystem#processEntities). If it turns out to be a bottleneck (though I doubt it), consider tracking whenever an entity goes from being culled/not culled - and manually manage the Entities held by affected systems (by calling EntitySystem#enabled and EntitySytem#disabled, from your culling system).

_________________
: bytecode-weaving antiboilerplate lib for artemis. | : bugfixing and performance optimized fork.

There is no code yet (well, there IS some code, but nothing ES yet, that's why I'm asking all this questions before implementing anything )

I'll try your suggestions, thank you very much for your time