GIANTS Editor

Slow Saving Time In GIANTS Editor

Estimated reading: 1 minute 592 views

Why does the GIANTS Editor save a map’s i3D so slowly when the terrain is modified?

The answer to that is how changes to terrain data are written to the map’s DEM file (or just .dem). What the GIANTS Editor does is rewrite/generate all the terrain data again, instead of just writing the portion of the data that was modified.
Now you may think your system/hardware is slow, but even on a high-end system, this process is still very slow today, especially for maps made for Farming Simulator that are larger than the vanilla size.

How does the terrain system in GIANTS Engine work in comparison to other game engines?

Comparison of Terrain Systems in different Game Engines

Engine / ToolTerrain TypeChange FlowStorageLimitations
GIANTS Editor (FS)HeightmapCPU-based, entire heightmap regeneratesFull file writing, synchronousNo tunnels/overhangs, slow brush
Farming Simulator GameplayOnly a small radius, limited deformationLocal real-time updatesDelta storage, asynchronousOnly small radius, limited deformation
Transport Fever 2Mesh + dynamic deformationGPU-accelerated, large brushes flowData streamingLimited by game balance, not full geology
Unreal Engine (Out of Ore)Mesh/voxelReal-time, deeply diggable terrainLocal updates, GPU + multithreadHeightmap (optimised)