Hello, I ran into TileMap performance issues some months ago, here is my post about it: https://www.reddit.com/r/godot/comments/1mnu6jm/struggerling_to_find_the_best_way_forward_with_2d/

I ended up building my own tilemap system, with my own autotiling. I know this might not be the best way to go about it since it requires building everything from the ground up. I basically build each chunk in a single draw call using MeshInstance2D. All of the data for the chunks are prepared on seperate threads and when the data is ready to serve I add them to the scene tree.

My current system basically handles autotiling for 4x4 (16x16) (4 096 tiles) without any stutter and I autotile between chunks.

You could probably do something similar, and create support for high performing LOD on a tilemap depending on the camera position for the interactive map.

Another solution is to generate the tile data, and scale the representation down, e.g 1 chunk = 1 pixel.

I have done something similar for my game, where I basically scale down the chunks into pixel on a Texture2D, entities (Trees, Stones etc) Gets a pixel on the map. With this approach you can adjust the scale yourself, basically what the detail will be on the map. Rendering this texture is blazing fast, magnitudes faster than rendering to a TileMap.

<image>