So there it is… Every single time I attempt to create a reasonable landscape My editor crashes claiming it is out of Vram… I have 36 gigs of vram… can someone please explain this to me. I have the editor set to medium quality while working and I can’t seem to figure this out. It is insane that 36 gigs is not enough.
1 Like
I’m actually looking for some insight here, the maximum amount of vram I have seen it using while monitoring it is 16 gigs… not even half of what I have. Something is very wrong and My project is literally on hold until I can figure out why I can not even generate a landscape.
Hey there @Korwinthale! This issue itself can often stem from the size of the landscape created. I also believe the issue stems from hitting the Shared GPU memory container’s maximum instead of your full VRAM. Does this occur for smaller landscapes as well?
Occasionally i get crashes even on a little bitty 64 x 64 map trying to just test it. I have 20 gigs of pure Vram and 36 shared
for tiny landscapes I can now get it to remain stable after switching to Dx11, but still have issues with my large world map. At this point I have literally build ALL of the coding for the game done all of the core work. I now need my world map and I’m stuck because I can’t seem to build it without crashing. I have reinstalled UE5 I have exhausted my searches and I REALLY do not want to have to switch engines and rebuilt all this work because I can’t make a map…
Interesting, so it’s likely tied to too much resource usage for building large landscapes considering your experience. Though it seems inconsistent between users, there is an upper bound where the scale starts to break down, though smaller landscapes usually don’t end up hitting it alone.
I am going to go out on a limb and hope that throwing in another monster chunk of ram might help. The biggest issue is that I get no real information in the crash logs so it is virtually impossible to track down the problem … just the obligatory “out of vram” message even though I am monitoring vram usage and am at like half my total when it goes poof.
I’ve got another 128 gigs of ram coming and if that fixes it I’ll let you know. It really “feels” like a memory access issue . I’ve tested the heck out of my ram and found no issues but who knows. I have actually gotten it to create the landscape a few times and even manipulated the regions etc but eventually it just explodes and trying to load the same landscape it just created after the crash results in a number of errors in various regions. It’s all very confusing. I have actually already done the height map in a 3rd party software and plan to import it but I’m waiting to fill those other 4 memory slots and see how that goes.
I’m uncertain on if it would help if it’s more of a resource timeout issue than a resource maxing out issue, keep me updated on how that goes! This has been an issue with the landscape system for some time, though some users are able to generate 50+km landscapes while most run into either this issue or the HLODs requiring unlimited resources and failing by crash or never completing.
Alright well, I put an ungodly amount of ram into my system and now it is working, I’m at 88 gigs of shared vram now and It has stopped crashing (as much) It still loves to randomly crash, but I guess that’s just URE5 for you. I made the mistake of believing the system requirements posted for it and thought I was good to go I have since upgraded and am now cruising through map production.
1 Like
That is definitely one solution! For now this is the workaround we have, though memory shouldn’t be capping so high, as this previously wasn’t (as much of) an issue. But knowing that increasing the amount of shared RAM basically solves it can definitely help ascertain what could be occurring. Thanks for the follow up!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.