Yes, I know this is old. But while you can import tiled landscapes to be stitched together during the import process, it’s a MASSIVE resource hog. anything over 16k total would crash when attempting to do so. it is possible to import a 16k landscape as a single file (if using world machine, tell it to recombine the tiled build into a single file) but anything larger and you’ll run into system resource limitations. I can’t even import a 16k landscape as a tileset of 4x4 4k tiles. I run into vram limitations during the import process. only if I import it as a single heightmap can I get it in, and even then it fills my RAM and pages a bunch in the process (usage drops to reasonable levels afterwards).
For a file that’s 231MB on disk, I’m blown away by how much the engine uses importing it.
At this point, as clunky as it was, I think world composition was a better solution for really large worlds. At minimum, you could actually import all the tiles and not crash… World partition seems promising, but for actually large terrains, it is not robust enough.