Set Landscape Component Size

Development World Creation
,
1

Hi all,

i have a height map in 4k resolution and i want to create a landscape with 2017m per side, in order to double the resolution of the landscape.

I also want to follow the “Recommended Landscape Sizes” to get only 256 components in order to not get performance issues with LODs and streaming.

But i dont get it done under Landscape → Manage → New → Import from file.

Input height map:
4033pxx4033px

Settings:
Quads: 63x63
Sections per Component: 2x2
Number of Components: 32x32
Overall Resolution: 4033x4033
Total Components: 1024
ScaleXY: 100

Resulting terrain:
4033mx4033m

If i reduce the Number of Components to the recommended 256 i only get 1/4th of the terrain with 1px / m².

If i scale it down i get the higher terrain resolution with 4px/m², but i still have the 1024 total components which is too much.

I guess i have to change the “Landscape Component Size”, but i don´t know how.

Anyone who can help?
It should be possible, since the linked technical guide lists it as a parameter in the table “Recommended Landscape size”

2

I think i figured it out. Changing the quads and then scaling down has the desired effect.

3

Not sure if the old landscape guide is all that relevant anymore if using world partition in 5.x. If you want a roughly 2kmx2km landscape, probably best to just make a level using the new open world template, and import new heightmaps into it?

4

It seems broken at 5.3, the resolution max is 1021x1021 (2x2 255x255 per component), and one cannot increase component size to get better resolution for the height maps hmhm

5

The old landscape guide was barerely relevant 10 years ago when published.

Number of components = number of drawcalls.
Higher number of drawcalls = lower performance.

One can split a 4k heightmap in 4 pieces, and create 4 landacape tiles at 256 components each covering the same surface area.
However the performance will then be 256x4 drawcalls - almost always since the system will likely require all 4 landscapes to be streamed in.

Of note:
Going up to the 8K landscape size even with 256 compoents will perform worse in spite of the number of drawcalls.
This is due to the fact that each component is far bigger than it ought to be in order to render/occlude correctly.
(Mostly depends on hardware at this point, but more surface per component = more vertex. More vertex = less performance).

Anyone at all using the landacape system should know at least enough to set up benchmarks for their desired minimum requirements system, and make any decision on size / number of components / tris count etc. Strictly off the benched performance.