Landscape/Terrain obsolete?

I was wondering - and since the demo scene is only composed of megascans assets - if traditional landscapes will become obsolete in UE5.

This is basically a question of how people will create their games in the future.

What do you guys think?
Will you use the UE Terrain tools, or stick to meshes?

1 Like

Landscapes will not be removed from UE5, mainly because you still want to import heat/height maps from software like World Creator.

Basically you could generate a Static Mesh from the maps as well and use that (maybe blending materials using vertex colors or UVs?).

I guess that depends what’s faster - Nanite or the terrain system.

Yeah! I also wanna know about this. These terrain softwares allow exporting tiled static meshes as well. So, technically we could use Nanite.

But in the docs, it says Nanite is best for assets we can instantiate more. For terrain tiles, it’s not the case.

What I been thinking with landscape is to use it for rivers and coastlines. And I am loading in a heightmap to use as a guide for placing and mapping out with nanite assets.

Landscapes are faster and easier, I also would like to know how we are supposed to make our terrains now.
I put several landscapes next to each other in a scene with no problem at all, but it’s not possible to sculpt those landscapes seamlessly like we were able to with world composition where all landscapes belonged to the persistent level. Or, at least, I didn’t manage to do it.
I guess we will soon see landscape components artist flood the marketplace with modular landscape elements for all kinds of terrains anyway.

Is this a good hope for your question?


No, you will always need a landscape system unless you’re working on small scenes with restricted area of movement/view.
How will you fill an 8km² map with only meshes, without holes, with rivers/roads splines, with the possibily to quickly flatten an area to place some building, etc.
Actual landscape system is planned to be replaced with Virtual HeightField Mesh but the work is done on the engine side, you will use it like actual landscapes.


You can add to your landscape in the manage tab of landscapes and simply add more components.

1 Like

The current landscape system is (unfortunately) not deprecated. It’s still (unfortunately) central to the water system but it’s by far the most oudated tool in the engine by this point, constantly crashing, with no proper undo support. I sincerely hope it’ll be addressed in the near future.

It’s noted that landscapes are currently NOT (yet!) supported w/lumen, likely why one was not included…

Can you recall where you heard that, as I’ve been hoping both that and virtualising LayerInfos (for more precise edit time landscape painting and physics boundaries) were on Epic’s radar. Started going down that track with the code myself but quickly saw it was going to be a nightmare to keep compatible with future updates.

I disagree. Even though better support for water without landscape would be nice, landscape is very quick and easy, and most importantly runs pretty well on all platforms, as its just displacements, and I have never ever had it crash, and undo support does exist. However yes, it definitely needs an update, or a suitable replacement. Voxel system perhaps?

I converted my 4.25 project to UE5 and activated Lumen and it is so much better than the old baked lighting. No patchy shadows, which I was strugglying to overcome despite having the maximum detail on the landscape - all the lighting just worked. And having done all the work I built the project and tested it on an i3-2100 with a GTX1050 and it ran perfectly.

Somehow I completely missed that bullet point. That explains why I’m getting a ton of crashes on every project using Landscapes.

I don’t think landscapes will be obsolete, because it’s always better to have tools in engine to build something other than relying on third party software.