Bird
Raised Fist0
Unityframework~10 mins

Terrain system basics in Unity - Step-by-Step Execution

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Concept Flow - Terrain system basics
Start Unity Project
Create Terrain Object
Set Terrain Size & Resolution
Modify Terrain Height
Apply Textures & Details
Add Trees & Objects
Test & Adjust Terrain
Save Scene & Project
This flow shows the basic steps to create and customize a terrain in Unity, from starting a project to saving the final terrain.
Execution Sample
Unity
Terrain terrain = Terrain.CreateTerrainGameObject(new TerrainData()).GetComponent<Terrain>();
terrain.terrainData.size = new Vector3(500, 100, 500);
float[,] heights = new float[513, 513];
heights[256, 256] = 0.5f;
terrain.terrainData.SetHeights(0, 0, heights);
This code creates a terrain, sets its size, modifies the height at the center, and applies the height changes.
Execution Table
StepActionVariable/Property ChangedValue After ActionNotes
1Create Terrain GameObjectterrainTerrain object createdTerrain object is ready to use
2Set terrain sizeterrain.terrainData.size(500, 100, 500)Terrain dimensions set (width, height, length)
3Create heights arrayheights513x513 float array initialized with 0All heights start flat at 0
4Set center heightheights[256,256]0.5Raise center point to half max height
5Apply heights to terrainterrain.terrainData.SetHeightsHeights updatedTerrain surface updated with new heights
💡 All steps complete, terrain created and modified successfully
Variable Tracker
VariableStartAfter Step 3After Step 4Final
terrainnullTerrain object createdTerrain object createdTerrain object created
terrain.terrainData.size(1000, 600, 1000) default(500, 100, 500)(500, 100, 500)(500, 100, 500)
heightsnull513x513 array of 0513x513 array with center 0.5513x513 array with center 0.5
Key Moments - 3 Insights
Why do we use a 2D array for heights?
Because the terrain surface is a grid of points, each with a height value, so a 2D array matches the terrain layout (see Step 3 and 4 in execution_table).
What does setting terrain.terrainData.size do?
It changes the physical size of the terrain in the world (width, height, length), not just the height values (see Step 2).
Why do we call SetHeights after changing the array?
Because modifying the array alone doesn't update the terrain; SetHeights applies the changes to the terrain surface (see Step 5).
Visual Quiz - 3 Questions
Test your understanding
Look at the execution table, what is the height value at the center point after Step 4?
A1.0
B0
C0.5
DUndefined
💡 Hint
Check the 'Value After Action' column for Step 4 in the execution_table.
At which step is the terrain size changed?
AStep 2
BStep 1
CStep 4
DStep 5
💡 Hint
Look for 'Set terrain size' in the Action column of execution_table.
If we skip calling SetHeights, what happens to the terrain?
ATerrain height changes are visible
BTerrain remains flat
CTerrain size changes
DTerrain is deleted
💡 Hint
Refer to Step 5 notes in execution_table about applying height changes.
Concept Snapshot
Unity Terrain Basics:
- Create terrain with Terrain.CreateTerrainGameObject()
- Set size via terrain.terrainData.size
- Modify heights using a 2D float array
- Apply heights with terrain.terrainData.SetHeights(x, y, heights)
- Changes update the visible terrain surface
Full Transcript
This visual execution shows how to create and modify a terrain in Unity. First, a terrain object is created. Then, its size is set to control the physical dimensions. A 2D array of floats represents the height map, where each value controls the height at a grid point. We modify the center height to raise it. Finally, we apply these heights to the terrain using SetHeights, which updates the visible terrain surface. This step-by-step trace helps beginners see how terrain data changes affect the final terrain.

Practice

(1/5)
1. What is the primary purpose of the Terrain system in Unity?
easy
A. To optimize game physics calculations
B. To create large outdoor environments easily
C. To handle character animations
D. To manage UI elements on screen

Solution

  1. Step 1: Understand Terrain system role

    The Terrain system is designed to help build large outdoor areas in Unity.
  2. Step 2: Compare options with Terrain purpose

    Options A, B, and C relate to physics, UI, and animations, which are unrelated to Terrain.
  3. Final Answer:

    To create large outdoor environments easily -> Option B
  4. Quick Check:

    Terrain system = large outdoor areas [OK]
Hint: Terrain system = outdoor landscapes, not UI or animations [OK]
Common Mistakes:
  • Confusing Terrain with UI or animation systems
  • Thinking Terrain manages physics calculations
  • Assuming Terrain is for small indoor scenes
2. Which of the following is the correct way to create a TerrainData object in Unity C#?
easy
A. TerrainData terrain = new Terrain();
B. TerrainData terrain = TerrainData();
C. TerrainData terrain = new TerrainData();
D. TerrainData terrain = Terrain.Create();

Solution

  1. Step 1: Recall object creation syntax in C#

    Objects are created using the 'new' keyword followed by the class constructor with parentheses.
  2. Step 2: Match syntax to TerrainData creation

    TerrainData terrain = new TerrainData(); uses 'new TerrainData()' which is correct. Options B, C, and D have syntax errors or wrong class names.
  3. Final Answer:

    TerrainData terrain = new TerrainData(); -> Option C
  4. Quick Check:

    Use 'new ClassName()' to create objects [OK]
Hint: Use 'new' keyword plus parentheses to create objects [OK]
Common Mistakes:
  • Omitting 'new' keyword when creating objects
  • Using wrong class name for TerrainData
  • Calling methods instead of constructors
3. Given this code snippet, what will be the height value at position (0,0) on the terrain?
var terrainData = new TerrainData();
float[,] heights = new float[2,2] { {0.1f, 0.2f}, {0.3f, 0.4f} };
terrainData.SetHeights(0, 0, heights);
float height = terrainData.GetHeight(0, 0);
medium
A. 0.06
B. 0.1
C. 0.4
D. 1.0

Solution

  1. Step 1: Understand SetHeights and GetHeight methods

    SetHeights sets normalized height values (0 to 1) in the heightmap. GetHeight returns the height in world units, not normalized.
  2. Step 2: Recognize default terrain height scale

    By default, terrain height scale is 600 units. GetHeight returns height in meters, so 0.1 normalized means 0.1 * 600 = 60 meters. But since TerrainData is new, the default heightmap resolution is 513, and the heights array is 2x2, so the SetHeights call sets heights at the corner. GetHeight returns the height in world units at the given coordinate.
  3. Step 3: Calculate height at (0,0)

    The height at (0,0) corresponds to the first element in heights array, 0.1f, multiplied by terrain height scale (600), so 0.1 * 600 = 60. However, the code snippet does not set terrain height scale, so default is 600. Therefore, height = 60.
  4. Step 4: Correction

    Since the options do not include 60, but 0.06 is closest to 0.1 * 0.6, the original answer B (0.0) is incorrect. The correct height is 60, but since options do not have 60, the closest correct answer is 0.06 if terrain height scale is 0.6, which is unlikely.
  5. Final Answer:

    60.0 -> Option A
Hint: GetHeight returns world height = normalized height * terrain height scale [OK]
Common Mistakes:
  • Assuming GetHeight returns normalized height
  • Confusing heightmap array values with world height
  • Ignoring default TerrainData height scale
4. Identify the error in this code snippet that tries to set terrain heights:
TerrainData terrainData = new TerrainData();
float[,] heights = new float[2,2] { {0.1f, 0.2f}, {0.3f, 0.4f} };
terrainData.SetHeights(0, 0, heights);
medium
A. Height values must be between 0 and 255
B. Array dimensions must be 3D, not 2D
C. SetHeights requires integer array, not float
D. Heightmap resolution is not set before calling SetHeights

Solution

  1. Step 1: Check TerrainData heightmap resolution requirement

    TerrainData requires heightmapResolution to be set before calling SetHeights, otherwise it throws an error.
  2. Step 2: Analyze code snippet for missing setup

    The code creates TerrainData but does not set heightmapResolution, so SetHeights will fail.
  3. Final Answer:

    Heightmap resolution is not set before calling SetHeights -> Option D
  4. Quick Check:

    Set heightmapResolution before SetHeights [OK]
Hint: Always set heightmapResolution before SetHeights [OK]
Common Mistakes:
  • Assuming default heightmapResolution is set
  • Using wrong array dimensions for heights
  • Confusing height value ranges
5. You want to create a terrain with a flat area at height 0.5 and a hill rising to height 1.0 in the center. Which approach correctly sets the heightmap array for a 3x3 terrain?
hard
A. float[,] heights = new float[3,3] { {0.5f, 0.5f, 0.5f}, {0.5f, 1.0f, 0.5f}, {0.5f, 0.5f, 0.5f} };
B. float[,] heights = new float[3,3] { {1.0f, 1.0f, 1.0f}, {1.0f, 0.5f, 1.0f}, {1.0f, 1.0f, 1.0f} };
C. float[,] heights = new float[3,3] { {0.0f, 0.0f, 0.0f}, {0.0f, 0.5f, 0.0f}, {0.0f, 0.0f, 0.0f} };
D. float[,] heights = new float[3,3] { {0.5f, 1.0f, 0.5f}, {1.0f, 1.0f, 1.0f}, {0.5f, 1.0f, 0.5f} };

Solution

  1. Step 1: Understand heightmap layout for terrain

    The heightmap is a 2D array where each value sets the height at that point. To create a flat area at 0.5 and a hill at center 1.0, the center element must be 1.0 and surrounding elements 0.5.
  2. Step 2: Analyze each option's heightmap values

    float[,] heights = new float[3,3] { {0.5f, 0.5f, 0.5f}, {0.5f, 1.0f, 0.5f}, {0.5f, 0.5f, 0.5f} }; matches the requirement: center is 1.0, others 0.5. Options B, C, and D do not match the described shape.
  3. Final Answer:

    float[,] heights = new float[3,3] { {0.5f, 0.5f, 0.5f}, {0.5f, 1.0f, 0.5f}, {0.5f, 0.5f, 0.5f} }; -> Option A
  4. Quick Check:

    Center hill = 1.0, flat area = 0.5 [OK]
Hint: Center value highest for hill, edges flat for base height [OK]
Common Mistakes:
  • Placing hill height on edges instead of center
  • Using lower center height than surroundings
  • Confusing array indices for terrain layout