After loading a tileset that is over 10GB, I’m having trouble with the map reloading when I move, change my view, or go back to the original view
For example, if a map for area A is loaded and you go to another area and come back, the map for area A is loaded again, or a map for a large area is loaded, and there is a problem with the FPS and speed slowing down as it is reloaded.
Is there any way to prevent the map from reloading after all regions have been loaded?
The short answer is: No, it is not possible to prevent this reloading.
The reason for that should be convincing: There is no upper limit for the size of a tileset. It could have 10MB, or 10GB, or 10TB. At some point, it inevietably will not fit into memory. Some of the previously loaded tiles will have to be unloaded. And they will have to be loaded again when they become visible again.
By the way: The limit for that might be far lower than one might think: For example, the tileset might contain textures as JPG files. The textures will be stored in the GPU memory (i.e. in the VRAM). And even a small JPG with 50 KB (!) can easily occupy 5 MB (!) of GPU memory.
There are parameters that can be used for “tweaking” the behavior - for example, things like the cacheBytes. On the other hand, one can also try to optimize the tileset itself in some way. If there are large textures, then reducing their size and compressing and storing them as KTX might help. But the best approach also depends on the structure and contents of the tileset, the user interaction, the available memory, the network connection, and many other things.
Thank you for your kind reply.
I will try modifying the settings and test it. Thank you.