This series is really helpful for my open-world games, thank you.

@@steven3314 - No problem. I will be adding a few more videos to the World Partition Series over the next couple of weeks. I will be diving deep into statistics and information that is probably not on most other videos on KZfaq.

Is there any way to solve this resolution bug? Unfortunately I have a 4k monitor and the whole thing is a bit frustrating.

@@MeikoKusanagi - Do you mean that the World Partition Grid moves around the screen when you move in the viewport? You will have to wait for Epic to fix it.

@@demenzunmedia Yeah that bug. Ill have to wait then.

Thank you. Additional videos in this series are still being developed.

Thanks.

Thanks. I have tested the memory usage on packaging a game with eight 16321 x 16321 maps, and the amount of RAM memory used was about 50GB. However, if you have less physical RAM, the packaging process may be able to use Virtual Memory, so make sure that you have a large Page File specified on your fastest drive. This may entail creating a manually sized Page File, as the default size may be too small. I haven't tested VM usage with packaging, I could test it on my 16GB RAM system to find out.

@@demenzunmedia welp, today I tested a 7680x7680 map. I was able to import the first one, then extend the land to paste import the second. Pc does slow down when editing the 15360 world, but its not bad for a 1660 6gb, 16vram computer. Im curious whether this 15360 map will build when doing the package. Lods work as normal.

You can scale the entire world's actors down, and that has the immediate benefit of giving you a Landscape of an apparent twice the size if you keep the Landscape size the same. An 8km Landscape at one half player scale would become a 16km Landscape. You may have to change the Scale Z though for elevation range. The downside is that the Landscape Scale XY would still be one meter, so in the mini world the Landscape scale would be the equivalent of two meters. That would also effectively make the streaming distance twice as far in the mini world, which should improve performance.

@@demenzunmedia That sounds promising... now all I have to do is to not screw up the math lol. I will keep looking to get that nailed down. Thanks again.

That is for if you are creating a manual Landscape as opposed to importing a heightmap. 8161x8161 has always been the largest Landscape size using the numeric control entry. See the UE5 Landscape Technical Guide for the Recommended Landscape Sizes and what values to use.

As far as I know Blender cannot import heightmaps directly as terrains. You would have to export from TerreSculptor as a mesh format such as Obj or STL and import that into Blender. Or use the heightmap as a bump offset or displacement in a material.

@@demenzunmedia thanks!

The World Composition Landscape Transform can be unlocked at any time to change the Landscape transform properties, even after the Levels are loaded. But it is originally locked because actors don't move with the changes. In World composition the Transform is not locked by default.

The Intermediate sizes are only if you are creating a single landscape that is in the Recommended Landscape Sizes category, such as 2017 or 4033. The Intermediate sizes are three additional sizes that will work along with the Recommended Sizes, such as 3025 or 6097. So you could create a valid terrain that is 3025x3025. It isn't for creating rectangular terrains. In theory you could do rectangular with 8129x4033, it has nothing to do with the Intermediate sizes of 1513, 3025, and 6097, they are just three more valid sizes that work and have optimal component counts. World Partition has its own set of optimal sizes which are calculated as (511 x N) - (N - 1). Those sizes should be used rather than the Recommended Sizes.

Cell loading is determined by the Loading Range property.

@@demenzunmedia yes, but I guess as you mentioned. It seems that feature is broken and doesn't work right now as it should. I wonder if there is a workaround. If not, is it possible to delete cells instead of unloading them? How would that work? I am currently testing the city sample. All I want to use are 4 cells. The rest of the map shouldn't be loaded or used in runtime. If the Data Layer doesn't seem to work and the Loading Range Property is buggy... hmm.. how can I achieve that? Maybe just deleting all the other cells I don't want to use? But how to do that?

@@BernhardRieder1 - There is no workaround, it will require Epic to fix it.

@@demenzunmedia hmmm.. and what if I want to use 4 cells in another project? Just exporting the geo that is on 4 cells? When I migrate the level, I do have the same issue. So I wonder what I could do, if I just want to use the geo that sits on 4 cells. Even if I have to create a new project, that's fine. But isn't there any recommended way to do that? Again, thank you sooo much for all your video tutorials. They are simply the best!

@@BernhardRieder1 - The Cell system in World Partition is totally different than the Level system in World Composition.

I will have a video in this World Partition series regarding methods of using foliage. I haven't finished fully researching it yet, so I cannot at this time answer any issues with Foliage Volumes. I should be getting to this step in the next week.

@@demenzunmedia That would be great man, I'm really glad to hear that. I'll continue researching to see what I can dig up until then.

Landscapes cannot be merged. And they usually cannot be positioned adjacent because the edges of the Landscapes have UV issues which messes up the material along the edges. The closest that can be done is to export the Landscape heightmaps and stitch them in external software like TerreSculptor, then re-import as a single Landscape. The World Partition Part 2 video discusses building MiniMaps. Depending on the size of your Landscape and which version of Unreal Engine you are using, you may have difficulties with getting the MiniMap to work.

@@demenzunmedia thank you🙏

@@Comandante_ - Regarding the MiniMap, Epic removed the properties that allow you to edit the size of the MiniMap in UE5.2 and UE5.3, I have no idea why they would do that. So in those engine versions you have to just choose Build MiniMap on the Build menu, and if it doesn't work, there is no way to get around that with the changes Epic made to the engine. With UE5.0 and UE5.1 you can change the MiniMap properties in order to create a smaller texture to get it to properly build.

If your foliage is eating up a good portion of the performance, then you could either decrease the foliage render distance, or change to a better foliage with better LODs so that it renders at a lower performance hit mesh in the distance.

@@demenzunmedia I've already done that, but what better way to manage all of this through HLOD's? the other question is if you say that the visibility should be 5 KM, how do you not run the risk of loading other grids and thus more assets? Have you tried to fill your cards with Foliages so also optimized? and then what the FPS says?

@@OoJxCorrey - The view distance should be whatever is the shortest that you can get away with for the design of the levels. If this is a large open world map similar to RDR or GTA, then you need at least a 3km to 5km view distance. If the level design has thick fog then you can probably decrease the view distance to 1km or less.

@@demenzunmedia Well i´ve found a weird Solution for me to work. I can choose any size of Grid and have no impacts. If i Build HLOD i have to make the Grid very Small. Its not a proper solution and no workaround but i can work on my Project.

Did you just max out all the values in the landscape window when creating your world? Which would mean you're working with an 8k resolution heightmap. If you did this... I would strongly recommending trying a new map with a 4k resolution heightmap, but scaled up at 200% (which gives you the same surface area as 8x8). Or if you REALLY want to optimize for performance which is what I'm doing, lower it to a 2k resolution heightmap and scale up to 400%. (still same surface area as 8x8) Unreal Engine for whatever reason begins to fall apart when you have a landscape resolution greater than 2k. The only trade off I've seen is if you scale up too much @2k your terrain will start to get more and more polygonal, as in flatter edges as opposed to more natural looking curves. So you need to find a balance.

This video was released before UE5.2 was available. World Partition Series video Part 13 discusses HLODs in 5.2 and 5.3.

The Grass is from the Epic KiteDemo, free on the Marketplace. The AutoMaterial I can probably add onto an inexpensive Marketplace item that I already have, it would take a couple of days to get it approved.

@@demenzunmedia thanks a lot for that

@@james_karst8825 - I have added my AutoMaterial to the RGBAK Master Material product on the Marketplace. As soon as that is updated by Epic in the next couple of days, if you want the Material you will be able to get it there. Search the Marketplace for "RGBAK" and you will find it.

@@demenzunmedia thank you very much this is helping me a lot

@@demenzunmedia It worked way better than I expected I also did not thought that the grass would be already painted on the terrain , this saves a lot of time , I'm entering the UE5 lighting master competition as a student , I'll make sure to credit the terresculptor and rgbak master material at the end of the 30 sec clip

If the HLODs are working properly, then the entire terrain is visible.

I agree. I haven't looked at the UE5 source code, but it sure acts like they are creating all Landscape Component textures at the same time, without swapping them out of memory when complete, eating up all of the video memory, both dedicated and shared, requiring large amounts of memory to get that function completed. On the surface it looks like bad/lazy programming to me. I shouldn't be limited to a maximum import of 44km x 44km with 128GB of main memory and an RTX-3090 24GB. The World Composition to World Partition Conversion is the same deal though, bad/lazy programming, for me to convert a 1024 sq km world took more than 26 hours on my R9-5950X, 128GB, RTX-3090. At no time did it ever go above 5% CPU usage and 0% GPU usage.

@@demenzunmedia Once more. It is my understanding that for multiplayer that the world partitioned map needs to be fully loaded in. I can't even imagine the memory requirements for servers using large worlds

@@demenzunmedia I second you, UE5 should have been put off for at least another year. I have yet to come across one new feature that's unique to UE5 that isn't ate up like crazy with bugs, slow processing, and crashes around every corner.

Yes, but it is not fun, see Video Part 10 in this series: kzfaq.info/get/bejne/ldqlhLCSsKm5dn0.html This is currently the only way to extend a Landscape, until UE5.3 or 5.4 come out with Large World support.

@@demenzunmedia yea the thing is i have tried so many options and fiail in this,, thanks for the reply

@@demenzunmedia I think ill create the landscape in ue4 using world partition and just covert it to ue5 after planning the level

@@samuelkilik8233 - UE4 doesn't have World Partition. World Partition is only available in UE5, and it has a limit of a maximum heightmap of 16321x16321. You will have to wait for UE5.3 or UE5.4 to get multi-import on World Partition. You also require a computer with at least 32GB+8GB to import a 16321 heightmap into World Partition. If you are planning on using World Composition, that has been deprecated and no longer supported in UE5 for updates. However, World Composition is still in UE5 and working, so there is zero reason to start with UE4 and transfer it through an upgrade import. Simply create the World Composition directly in UE5. Just don't expect any new features or fixes or support for World Composition any more. With World Composition in UE5, you can create really large landscapes, up to 60,000 or more if you have the system hardware for the original heightmap. You will just lose out on the newer more advanced features of World Partition if you choose to use World Composition.

@@demenzunmedia ouh sorry world composition....the thing is i am trying to create a small map where the size is not gona be fix and should be able to extent down the line of progress

Do you have anything else running at the same time besides Unreal Engine? Is the UE5 Project just the Landscape and no other meshes or content? When you have no software running and at the Windows desktop, what does Windows Task Manager say that your Free Memory, Free Dedicated GPU Memory and Free Shared GPU Memory is? Out of memory crashes can occur in UE5 if the Dedicated+Shared GPU memory gets exhausted, so if there is anything running that is eating up a lot of GPU that could be the issue. On my R9-5950X + 128GB + RTX3090, the Free Memory is 122GB, GPU Free Dedicated is 23.8GB and GPU Free Shared is 64GB.

@@demenzunmedia Nope nothing running besides task manager. I have a similar setup as you, 115gb free memory, 24gb free dedicated gpu and 64gb free shared. When the landscape is loading and proceeds to crash, the gpu is only 25% utilization, memory is 20%, and cpu is around 10-15%. I have tried all the tweaks such as increasing poolsize, pagefile size, using DX11 as well as DX12. Used DDU to reinstall drivers. Here is the log error: LogD3D12RHI: Error: Adapter->CreateCommittedResource(Desc, GetGPUMask(), HeapProps, InCreateState, InResourceStateMode, DefaultState, InClearValue, &NewResource, InName, false) failed at D:\build\++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12PoolAllocator.cpp:430 with error E_OUTOFMEMORY [2023.07.05-20.23.26:667][557] 0.000MB - Pixel buffer memory - STAT_PixelBufferMemory - STATGROUP_RHI - STATCAT_Advanced [2023.07.05-20.23.26:667][557] 289.744MB - Structured buffer memory - STAT_StructuredBufferMemory - STATGROUP_RHI - STATCAT_Advanced [2023.07.05-20.23.26:667][557] 19.355MB - Ray Tracing Acceleration Structure memory - STAT_RTAccelerationStructureMemory - STATGROUP_RHI - STATCAT_Advanced [2023.07.05-20.23.26:667][557] 43.499MB - Vertex buffer memory - STAT_VertexBufferMemory - STATGROUP_RHI - STATCAT_Advanced [2023.07.05-20.23.26:667][557] 4.599MB - Index buffer memory - STAT_IndexBufferMemory - STATGROUP_RHI - STATCAT_Advanced [2023.07.05-20.23.26:667][557] 12.215MB - Uniform buffer memory - STAT_UniformBufferMemory - STATGROUP_RHI - STATCAT_Advanced [2023.07.05-20.23.26:667][557] 16.160MB - Texture memory Cube - STAT_TextureMemoryCube - STATGROUP_RHI - STATCAT_Advanced [2023.07.05-20.23.26:667][557] 40.484MB - Texture memory 3D - STAT_TextureMemory3D - STATGROUP_RHI - STATCAT_Advanced [2023.07.05-20.23.26:667][557] 6366.031MB - Texture memory 2D - STAT_TextureMemory2D - STATGROUP_RHI - STATCAT_Advanced [2023.07.05-20.23.26:667][557] 1.688MB - Render target memory Cube - STAT_RenderTargetMemoryCube - STATGROUP_RHI - STATCAT_Advanced [2023.07.05-20.23.26:667][557] 83.250MB - Render target memory 3D - STAT_RenderTargetMemory3D - STATGROUP_RHI - STATCAT_Advanced [2023.07.05-20.23.26:667][557] 11766.938MB - Render target memory 2D - STAT_RenderTargetMemory2D - STATGROUP_RHI - STATCAT_Advanced [2023.07.05-20.23.26:667][557]18643.963MB total

I narrowed down when the actual crash occurs. I reimported a new 16km map and at first everything worked great and functions as it should. When i close UE and re-open the map it will proceed loading resources and when the dialogue "Waiting for texture resources to be ready for landscape named: Landscape" it crashes. I don't have any material applied to the landscape and tried using virtual textures. Starting to wonder if I have a hardware issue.

@@justintimesYT - Make sure that you are using an actual valid World Partition heightmap size. World Partition sizes are different than Landscape Sizes and World Composition Sizes. And import it as a single large PNG-16 file and don't use Tiles, especially don't use World Composition size tiling. For example, 16321x16321 is a valid WP size. If this is a new project, you also don't want to re-import into the same project over and over while having issues, you will get piles of junk in the OFPA folders for ExternalActors etc. Deleting actors does NOT clean up the OFPA store, which is a really big issue that Epic needs to address.

@@demenzunmedia Yes my size is valid. Did not know that about the OFPA issue. That could possibly be it considering i have just been using the same project.

This is just the Basic Concepts video, it is just a quick overview of World Partition, there is an entire series of videos on the channel that each goes in-depth on a specific subject with World Partition, with more videos in the series under development. If that isn't up to your preferences, then you should go find another video series.

Some people complain my videos are too fast, others complain that they are too slow. I just can't please anyone.