Terrain generation

Here you will understand how all the variables work and how to start the infinite generation of the terrain!

Last updated 8 months ago

Terrain generation

Here you will understand how all the variables work and how to start the infinite generation of the terrain!

What you have to put in the scenario is the BP_WorldEngine actor (available in the plugin folder). It is responsible for generating everything 100% working and ready for you, define the variables for testing (see what fits best for your objective):

All you need to know about the variables of infinite terrain generation are these:

X Vertex Count: defines the quality of the terrain generated on the X axis, in order to optimize the plugin already has a value of 50, but 100 is a good result with a satisfactory quality!
Y Vertex Count: defines the quality of the terrain generated on the Y axis, in order to optimize the plugin already has a value of 50, but 100 is a good result with a satisfactory quality!

PS.: The calculation made between these two values is very simple: X Vertex Count * Y Vertex Count. Using the value 50 as an example: it would be 50 times 50 = 2500.

Cell size: this is the size of the generated squares, they can also be called pieces, this variable increases the size of each piece of procedural generation.
Num Section X: is the number of chunks on the X axis in a section per generation, i.e. the generation will be created from the sections, this is completely synchronized with the player's location in the world.
Num Section Y: is the number of chunks on the Y axis in a section per generation, i.e. the generation will be created from the sections, this is completely synchronized with the player's location in the world.
Mesh Section Index: it is just a debug variable, it stores the value of the last generated section to be able to reuse chunks already left by the player.
Randomize Terrain Layout: you can literally randomize the terrain layout automatically when starting the game (beginplay).
Perlin Offset: this is the value that you can "slide the perlin noise" to have a more suitable format for the developer to customize.
Terrain Material: needless to say, right? This is where you define the texture of the generated terrain.

PS.: Don't use a Layer Blend material, use an automatic one (the procedural component doesn't support full landscape functionality).

Tile Replaceable Distance: This variable controls the distance needed to generate the next terrain chuck.
Mountain Height: is the value that controls the height of the highest mountains in the country on the Z-axis (the higher the value set, the smaller the size).
Boulder Height: is the value that controls the height of the terrain planes on the Z axis (the higher the value set, the smaller the size).
Mountain Scale: this is the float value that controls mountain scaling on the X and Y axes.
Boulder Scale: this is the float value that controls the scale of the planes on the X and Y axes.
Just test the values to get a result that pleases you.

This could be the result you have:

Last updated 8 months ago

All you need to know about the variables of infinite terrain generation are these:

X Vertex Count: defines the quality of the terrain generated on the X axis, in order to optimize the plugin already has a value of 50, but 100 is a good result with a satisfactory quality!
Y Vertex Count: defines the quality of the terrain generated on the Y axis, in order to optimize the plugin already has a value of 50, but 100 is a good result with a satisfactory quality!

PS.: The calculation made between these two values is very simple: X Vertex Count * Y Vertex Count. Using the value 50 as an example: it would be 50 times 50 = 2500.

Cell size: this is the size of the generated squares, they can also be called pieces, this variable increases the size of each piece of procedural generation.
Num Section X: is the number of chunks on the X axis in a section per generation, i.e. the generation will be created from the sections, this is completely synchronized with the player's location in the world.
Num Section Y: is the number of chunks on the Y axis in a section per generation, i.e. the generation will be created from the sections, this is completely synchronized with the player's location in the world.
Mesh Section Index: it is just a debug variable, it stores the value of the last generated section to be able to reuse chunks already left by the player.
Randomize Terrain Layout: you can literally randomize the terrain layout automatically when starting the game (beginplay).
Perlin Offset: this is the value that you can "slide the perlin noise" to have a more suitable format for the developer to customize.
Terrain Material: needless to say, right? This is where you define the texture of the generated terrain.

PS.: Don't use a Layer Blend material, use an automatic one (the procedural component doesn't support full landscape functionality).

Tile Replaceable Distance: This variable controls the distance needed to generate the next terrain chuck.
Mountain Height: is the value that controls the height of the highest mountains in the country on the Z-axis (the higher the value set, the smaller the size).
Boulder Height: is the value that controls the height of the terrain planes on the Z axis (the higher the value set, the smaller the size).
Mountain Scale: this is the float value that controls mountain scaling on the X and Y axes.
Boulder Scale: this is the float value that controls the scale of the planes on the X and Y axes.
Just test the values to get a result that pleases you.

This could be the result you have:

Tree Generation