This is AWEFUL!! If they didn't prepared and say "hey you guys have to wait:/" than at least they should let us use ordinary way to use it I have to download manually one by one and some of asset can not be access!

I won't be changing the way I teach. Sorry

should work now. Sorry about that

Hey! Thank you for the support. I might be able to get around to that. i was thinking of doing a general open world map tutorial with a handful of different assets.

@@mootzartdev thanks. Do as soon as possible brother. Im waiting

I can make one. If people want me to make different sized videos I can. I have already made 30x30 also just so you're aware

@@mootzartdev yes i just watched one with the scaling tips so it helped me create 20*20. Thank you ^-^

Im trying to fit in at least one a week now. But i will likely get two out this weekend. They will be shorter then this one covering specific more advanced tools in the create menu :)

it is the total height from lowest to highest point :) But you of course have to do the calculations to work that out in terms of the value in UE.

Sorry to hear that. Its quite a difficult thing to get your head around at first. But you can get there with some practice

This is using World Partition. Currently it prefers a single heightmap file and its not really designed for tiled ideally. But this is probably going to change soon.

@@mootzartdev I got 2 100km x 100km On top of each other done. 3090 48gb ram. Runs great so far. Thank you.

Have you triple checked the total component amount in your settings? It should not exceed what i have in my setup.

So i found out that this is related to the resolution that youre using(Youre using 16k resolution ?), i have 2 questions: 1: what happens when we use low resolution in landscape. 2: how can i know the resolution for 2 or 4k landscape.

@@StaticPlayer Ok that's fair enough. 16321x16321 is going to require a lot of VRam. It can get a little confusing with the terminology. 1: The resolution of the heightmap file will determine the resolution of the height map. When we say 'K' we generally are talking about the heightmap/image size so in this videos example we are using a 16321x16321 heightmap which we call 16k image. Which if we leave at base settings of 1:1 will end up with 16kmx16km due to how UE converts the image to scale. But this does not mean we have to stick with that. We can scale the landscape to whatever sizes we want.. So in this example Im using a 16k image and scaling it to a 30kmx30km map. If you use a 2k heightmap and scale it to 25km x 25km it is likely going to look bad or stretched out due to the heightmap being a low resolution image. 2: You should already know this as its determined by the heightmap size you are using on input.

@@mootzartdev Thank you for the reply <3

Hey, thanks for the message. Sadly this does not work. My landscape is made up of 32 components in this example you are correct. However the World Partition Region Size setting is how many components go into each of the individual regions. Setting it to 32 creates no regions at all as that is the entire landscapes 'makeup'. I'm almost certain that it is a bug and I am setting it up perfectly correct.. as lower scale examples work perfectly with the formula I use. And in fact these versions also work technically. However the bug is where it positions them on maps above 2k. I have tested nearly all setups.

Hey, thanks for the message. Sadly this is not quite right. I have written back to you explaining why in your other comment. World Partition Region Size setting states 'number of components per Landscape World Partition Region per axis'. Which essentially means how many components go into each individual region. I have tested many different examples. I only tend to get the issue with 4k and 8k maps. Perfectly fine with 1, 2 and 16k maps. So im nearly certain its a bug.

Hey im copying my answer for others to read as you have commented on three videos with the similar comment. And its not worth me rewriting haha. Appreciate the engagement though . "Hey, thanks for the message. Sadly this is not quite right. I have written back to you explaining why in your other comment. World Partition Region Size setting states 'number of components per Landscape World Partition Region per axis'. Which essentially means how many components go into each individual region. I have tested many different examples. I only tend to get the issue with 4k and 8k maps. Perfectly fine with 1, 2 and 16k maps. So im nearly certain its a bug."

Thanks.. Deep down im a lazy person

Excellent! Thank you for the comment. i will try this out for the market asset update. Ill be adding new landscapes to it soon

@@mootzartdev Im not sure if its accurate, but worth a shot I guess.

Purple line are thr landscape regions. Found within thr landscape actor.

this is usually related to GPU issues. Drivers or similar. Also depend if your hardware is capable of doing the task you are trying to do in the first place. Sorry for the time to get back to you

I honestly wouldn't even bother thinking about it at this point. It really isn't worth wasting your time with at this scale. It takes to much resource to be viable for any type of project beyond 2-4k maps.

@@mootzartdevthank you for the advice

No, world partition is designed to deal with single file heightmaps predominantly. Tiled actually takes more resources with world partition.

Hey, You are able to use typical tools like sculpting, stamps etc in the landscape edit mode. The heightmaps are just a 'better' way of getting initial details etc. Or i can be your final product of course. Hope this helps.

At the moment not really.. but they may become more important as time goes on.

I would suggest a landscape auto material to get yourself started

Sadly not this one as its part of my personal project. I am slowly creating a free heightmap playlist for this though. I have only released the 1k versions for free though. The product in the description has 1-8k maps though.

Sorry it took so long to reply. I am working through various subjects. But i will of course get to this. I would suggest looking into PCG for trees etc firstly.

@@mootzartdev No worries at all. You have some of the most impressive tutorials ive seen in unreal, take all the time you need ! As for PCG I am familiar with it. But HLODs really are tough to grasp due to lack of digestible info in specific cases. Especially considering nanite trees. I saw a great video presentation from unreal using this technique but they gently glossed over it. The presenter had LOD billboards baked into the HLOD, and at a certain distance the HLOD would pop in to replace the nanite mesh.

In this example im using UDS which has this option pre-set. Though i dont think its to much to work out :)

Have you triple checked your settings to see about the total component values ?

who?

No thank you.

Gaea if you want to buy software.