[SUPPORT] Advanced Turn Based Tile Toolkit

[Dan.Ott]

Thanks for your replies

Increasing loop iterations only affects how many computations that can be done… thus you can increase the size of grid and do more computations…
I dont think moving grid is a good idea because all the math for tile finding would be off…
Are you using alot of “foreach” nodes by any chance ? if you are try putting in a macro with “foreachwithbreak” setting break to 0.1 or 0.2 and make sure “oncomplete” has a return node, or use “foreach” with a delay of 0.1 - 0.2
try using “pregenerate gameplay grid” for sure…
Hope this helps some…

I have an old copy that has a multi level map and using that as template, My map is set up like a 3d chess game and only way to reach another level is through a teleporter/wormhole.

Would be perfect to figure out a way to move the grid and recalculate the reachable tiles and realign the tile decals.
Yap - we tried pregenerate gameplay grid, will definitely use that in the build version! No, currently there are not many foreach nodes in the blueprints.

: Ah, now I see what you’re getting at. I’ve indeed capped the grid size to 200 in the variable settings of BP_GridManager, though you can easily increase this cap. I’ve added the cap to signal that you’re going beyond what the toolkit is tested for. I’ve tested at roughly twice the size of the largest Civ and XCOM maps, but if you start going greatly beyond this it is mostly untested.

In principle you should be able to have very large grids without issue, as it mostly boils down to storing some large arrays, but modern computers have very high limits when it comes to that. Unlike in early versions of the toolkit, there are no functions run during the game that loop over the entire grid, so it should be pretty scalable. The exception is the startup code for generating the grid, which explains the loop limit stuff you’ve run into.

How big do you want to make this grid, though (in terms of number of tiles X*Y?). If you want to do something very big indeed you might not want to generate the entire grid at startup.

Edit: By the way, subgrids are not used for multi-level grids. For this select MultiLevel in heightmap settings for BP_GridManager. The subgrids are used for extending the size of the grid in the X and the Y axis beyond the base size of the grid, which can be useful for optimization in cases where you have a total play area that conforms very poorly to a rectangular shape.

The biggest map has a size of one squarekilometer - whilst our tiles are one squaremeter (half the size of ATBTT’s standard tiles). So we want the grid to be 1000x1000 tiles big. But of course it would also be nice to just relocate a way smaller grid as we actually only need a grid 128x128 sized grid for the combats, so in terms of performance simply relocating the grid to the player’s position when ever a combat starts would be great - but unfortunately we’re facing many problems when changing GridManager’s positon and it’s unclear which functions of e.g. SetupCoreBlueprints such as SetupCollisionPlane etc we need to call at what moment in order to get the grid align to the new location & it’s obstacles / heightmap.