What is says on the tin, crashes with out of video memory error. I have a RTX 3080 and have been working on landscapes for over a year in UE5 at this point.
Make new open world map
Try to create a terrain 4k or over simply crashes the editor, tried 4033 and 8129 both crash 100%
Hi Aten,
What ‘Section Size’ and ‘Sections Per Component’ settings are you using when creating it?
I’ll see if it reproduces on my PC.
Cheers
Hi, not sure what it was in the end but upon creating a new project the problem has fixed itself. So maybe there was some iffy setting in the project, I did turn on landscape patch plugin + water plugin which are both still ‘experimental’ so perhaps it was something to do with that?
i have the same problem, and no resolution…
Hey Zhushilin,
What ‘Section Size’ and ‘Sections Per Component’ settings are you using when creating it?
Have you enabled any plugins?
Are you able to reproduce this in a new project?
Thanks
have the same problem with creating river with water plugin since 5.1.
I’ve already created a landscape but the engine has crashed 10+ times since I started making a new large world using world partition. It has something to do with enabling editable layers when creating a new landscape.
If I’m lucky enough to start using the landmass blueprint spline it will crash every time I start to move a spline point.
Engine crashes everytime i right click on layer and hit import on already created landscape(flat) on landscape scupt mode. UE 5.1.
They have somehow made importing large landscapes even worse in UE5, to the point that beyond a certain size or number of weight maps it just flat out will not work. It uses absolutely insane amounts of VRAM doing god only knows what, and then will crash if the landscape is anything remotely substantial. Anything above 16k, whether thats one tile or a thousand, seems to result in problems.
I have a 2080 Ti with 11gb of VRAM, and then 32gb of shared GPU memory. Somehow when importing a 20k x 20k landscape split into 1600 tiles, it manages to blow through all of this and crash. This is with edit layers off of course, since attempting anything with them on is laughably pointless.
Since Epic in recent years basically refuse to acknowledge anything about anything, ever, I’m left to conclude they have problems as a company, and this might come through in any given feature. In fact, as a guide, the more the marketing department tout something, the less likely it is to actually work when a proper stress test is finally done by the end user.
How many times have problems with world partition and memory usage been brought up since UE5 has been available? How many people, how many threads about the issue? And how often have they acknowledged it? What have they done about it?
Nothing, which I expect will also be the sum total of what they have done about it by the end of the engine’s life span. If you want to make little dioramas, UE5 is great. Any claims they make about scale in this engine though, are dancing right on the line of being outright lies. Third party plugins are the only way to actually get functional tools for large worlds, because their creators actually rely on the thing working for their continued income.