Stuttering while building new cells about flame_spatial_grid HOT 3 CLOSED

Hey @ASGAlex, I ended up writting my own very basic spatial grid system (just grid mapping and some basic grid state management). But anyway, I'm just making some tests for a possible personal game code base.
I'll try to tweak those parameters as suggested as soon as I have an opportunity to do so.
Thanks for the tips!

from flame_spatial_grid.

This is expected behavior because you player leaves preloaded game field and triggers creating new cells with (probably) new components inside. Than more components you will have inside than longer the game will freeze.

I try eventually optimize the process but anyway it is blocking by-design, especially with single-threaded language like Dart =(

To avoid stutter in your game you should play with grid parameters:

• cellSize: should not be too big but maybe it is better to make it 10 times bigger than your average component size;
• activeRadius, unloadRadius, preloadRadius - to find balanced combination of active vs pre-build cells
• processCellsLimitToPauseEngine - if you need sometimes to build very large field of cells
• buildCellsPerUpdate / cleanupCellsPerUpdate

You can read details in initializeSpatialGrid dartdoc, and play with parameters to find which fits with your game conditions.

Also, keep in mind that debug overlay is completelly unoptimized, so keeping it constantly enabled will cause a heavy FPS drop. But you can toggle it in runtime.

from flame_spatial_grid.

@daniel-mf did you found a solution for your case?
For your example it is only necessary to change processCellsLimitToPauseEngine to larger value (default is 5) to prevent engine pausing while building new cells. But in games with complex logic it may become a reason of bugs. In this cause it become better to pause whole game during loading.

from flame_spatial_grid.