I was looking for this exact thing and found a great answer at unreal forums. I'm going to paste that instead of the link to it, because youtube keeps doing weird things with comments with links in them: the more components you have, the more draw calls there are. think of it as each component being a seperate object. larger components have fewer draw calls, but it also means there is going to be a lot less LOD-ing as each component is bigger and needs to spread its LOD over a larger area. If you have a very flat landscape, use larger components as you can then start out with fewer detail in each component and the LOD-ing becomes less of an issue, and because the landscape would be so flat, you wouldnt want lots of smaller components as you would be seeing lots of them at a time, which would increase the draw call cost. for a very hilly or obstructed landscape, you want lots of smaller components. this is because you can cull out the components you cant see, which increases performance, and because they are being culled you dont suffer from draw call issues. because the components are being culled so well this way, you can increase the detail in the landscape without much performance cost. source: "Understanding landscape size and performance" thread, answered by "Construc")

great thanks for the comment, I downloaded the material from unreal sensi's website directly, i've provided the link here, he has avideo also explains how to make the material if you are interested, this file is a great starter file with great settings. link to material: www.unrealsensei.com/asset/autolandscape

Its good for a start...

Depends on what you are doing but for the most part it’s workable…if you start to use a lot of megascan objects it can start to eat up your ram

hI, i have the same problem. Select the mountain object at top level (landscape ...(self)) and move it a bit, then it will render the mountain. It seems some kind of a refresh problem.