[SUPPORT] Advanced Turn Based Tile Toolkit

[Monokkel]

@Darthlatte

Ahh, I’m using UE4 4.20, that’s probably why the uasset file doesn’t work

The problem was that I had the new terrain above the grid manager threshold, so it didn’t work.

On another note, I’m trying to create a rather large grid for my rather large game world, and am running into issues with the “infinite loop detetcted” when generating the grid tiles. I’ve read that this can be solved by increasing the iteration count, but that doesn’t seem like the best way to handle large worlds (at least for me), and I’m pretty sure that it doesn’t work with level streaming (I may be wrong here). So my question is this, wouldn’t it be better and more flexible to generate the grid around each player per turn? Say, maybe just generate a 20x20 grid around the player pawn on each turn, or am I missing something obvious?

Thanks

Ok, that explains the missing ability. Whenever I release a new update of UE4 it is always for the newest version. That is the version I use when developing and it is not possible to convert projects to older versions of UE4, so updating multiple versions would be too time consuming. Hope the free roam ability gives you a good starting point to achieve your intended goal.

As for large maps, I would generally recommend calculating at startup. The map generation stuff are some of the heaviest operations in the toolkit, so if you want to run a limited version of them every time you run pathfinding etc. it could quickly slow the game down. You could increase the iteration count, and if it is possible to reset this to the normal value after the first tick of the game, there aren’t many drawbacks to doing it this way. Another possibility is to run the startup function over multiple ticks using my ForLoopPerTick and ForEachLoopPerTick macros. It will take some reordering of things, but should not be terribly difficult to do.

How large a map are we talking here, by the way, and what options are you using (multi-level, trace for walls etc.)?

I’ve been slowly but steadily putting more hours into this real-time-to-turn-based project…There’s something I’m wondering now about the camera: if I wanted the same camera controls (Zoom, Pan, Rotate) for both gameplay situations, what would be an elegant way of solving it?

I see that they way its set up now, the PlayerController detects the input events, and triggers in the GridCamera BP other events which execute these actions.

For my real-time moments, right now I have a camera parented to a SpringArm in my character blueprint (, in the future I will follow your advice and turn this character BP to an Actor BP that spawn a character and attaches itself to it, like you mentioned in post #2374](https://forums.unrealengine.com/unreal-engine/marketplace/31005-support-advanced-turn-based-tile-toolkit?p=1553520#post1553520)). I was trying to copy the events and setup, but I was wondering if there was a more intelligent way of doing this rather than copying the same code, and creating the same variables, twice.

Anyone who’s willing to share their thoughts on this would be super appreciated! Cheers.

Any reason you can’t just use the grid camera in both modes of play?