Importing Terrain from Gaea 2

Set the terrain resolution. The resolution determines the number of pixels in the exported height and albedo maps and directly affects the detail level of your terrain.

For resolutions above 8192 x 8192, exporting in tiles is recommended as this helps to avoid RAM limitations, especially when using 32-bit textures. To do that, in the Build Settings, select Tiled Images and define the Tile Size. Gaea will produce multiple tiles to cover the full terrain.

For example, exporting a terrain at 8192 x 8192 resolution with 1024px tiles will produce an 8 x 8 grid of tiles (64 tiles total).

Specify your build destination folder. You can use predefined tokens in the folder path to dynamically generate names based on project data.

If you're using tiling, configure the tile suffix pattern correctly.

Here's how the default patterns compare:

• "_y%Y%_x%X%" (for Gaea 2)
• "_%X_%Y" (for UNIGINE)

You can change the pattern in either Gaea 2 or UNIGINE, just make sure they match exactly to ensure correct tile loading and alignment.

Select the suitable export format. UNIGINE allows importing 8, 16, and 32-bit maps.

For heightmaps better use 32-bit to preserve elevation accuracy. Lower bit depths (8 or 16-bit) can bring visible artifacts, especially on large-scale terrains.

Define your terrain's physical Height (vertical range) and Width (horizontal size) in meters.

Pay attention to:

• Real Scale: Meters per pixel, defines detail density by showing how many meters are represented by each pixel. Сalculated as output resolution divided by width. (e.g. 4096 / 8192 = 0.5m/px)
• Height-Scale Ratio: Defines the vertical exaggeration of the terrain. Calculated as height divided by width. (e.g. 2048 / 4096 = 0.5)

Once all settings are configured, click Execute Build to start the export process.