Importing data
For the purpose of this guide we will use the previously downloaded source files, however when making your own terrain this step usually follows after getting some starting real world data or crafting them yourself in L3DT or similar tool. It’s far easier to explain the creating your own data, when you already understand what the files are used for, so we highly encourage to stick to using the supplied source data for now.
This part assumes you already set up your mapframe properly and the source files you have match the settings you used for your mapframe. The order in which you import files is not too important, with the exception being that object imports are dependant on the heightmap.
First you should make sure you can actually see the files that you import, so check the marked icons in the View toolbar. To see what each one does, mouseover the button and it’ll show which type of files it’ll show when enabled.
Terrain Builder isn’t the most stable software and has a habit of crashing often. Between each import it’s a good idea to save your project (Ctrl+S).
Heightmap
The heightmaps is what controls the elevation of your terrain, import it by going to File > Import > Terrains. Each button of the import menu also has a toolbar button that you could use instead.
Navigate to the source files and import the gtt_heightmap.asc file. You could also use a black and white image file for this, but we don’t recommend using this at all, check Heightmap editing for more info.
Rebuilding terrain
One important to thing to note is that within a Terrain Builder there are two heightmaps. One is the heightmap file you import (.asc) and the other is your currently build terrain in your heightmap we call Heightfield. Whenever you import a new heightmap you need to right click the mapframe in Mapframes panel, go to Properties > Processing and click Rebuild Terrain. This will rebuild the heightfield out of your currently loaded heightmap file.
Something EXTREMELY important to note is that any heightmap edits you make in Terrain Builder or Buldozer are made on your heightfield. This means that whenever you press the Rebuild terrain button all changes you have made to the terrain will be overwritten using data from the loaded heightmap file. (Because the loaded heightmap file does not change, just the heightfield)
In effect this means that whenever you make changes to the heightmap in TB or Buldozer, you should export the heightfield, so you can replace the loaded heightmap file with this. Use File > Export > Terrain and export it under a new filename (It’s a good idea to keep multiple versions of your heightmap) gtt_heightmap_01.asc
Next right click the gtt_heightmap.asc layer and do Remove this Terrain. After that right click the DefaultMapFrame_01_heightfield and do Refresh Content from Source and select gtt_heightmap_01.asc. You want to do this process whenever you make changes to the heightfield using buldozer.
Satmap
The satmap, short for Satellite map is what you see at further distances ingame. It’s what you see when you’re in a helicopter or looking around in open areas.
To import the satellite imagery in TB go to File > Import > Satellite Images, navigate to the folder files and import the gtt_satmap.bmp.
The next window will show the coordinates and resolution, with the exception of split mapframes this should be [200000, 0] and [1.0, 1.0] similar to what you use for mapframe settings.
Normal Map
This is an optional file as discussed in Mapframe, but we will be using it in this guide. Import it by using File > Import > Satellite normal map. Generally this will be a blue/purple image file, ours is called normal_map.bmp. Double check the resolution and localisation options in the popup and click Ok.
Mask
Next is up the mask file, the actual colors this file will have vary wildy, but it’s always going to be an image with very limited colors. Import it by using File > Import > Surface Mask images. Confirm coordinates like the other image files and click Ok.
After importing these 4 files you should have something resembling the screenshot. We recommend turning of the icons in the View toolbar from right to left to see if each file is where it should be and loaded properly. Make sure you save your project.
