I was dumb and upgraded to Unreal Engine 5.4. I recently packaged my project, but when I try to load the first level it crashes and says I’m out of virtual memory. I have 32 gb of virtual memory and 32 gb of ram and the game plays fine in the editor. I tried upgrading to 5.4.4, but the problem persists. Does anyone else have this issue? Is it something specific to UE 5.4 maybe?
1 Like
It sounds like you’re running out of VRAM.
When you run the game in editor, do you get a red message about VRAM during play?
What’s your GPU, how much VRAM does it have?
1 Like
Greetings @derf0007
As Clock mentioned, this sounds like you’re running out of RAM. I’d check the areas Clock recommended. You can also pop open your task manager while opening UE and watch your levels.
1 Like
The only thing that is red is "Video memory has been exhausted by 450mb
I’ve had that in the past without issues. Everything is nanite and my frame rates at 90 FPS at 4k. Where do you suggest I start looking or things that usually eat up VRAM? I didn’t have this issue with 5.3.
1 Like
Packaged project start on the highest graphics setting. You seem to be running out of memory in the initial states of the project. Have the game run a benchmark blueprint to auto set the settings and save them.
Or you can edit the ini files of the packaged game so that they have lower settings (high instead of epic)
1 Like
When you get the error, take a look at
This is the VRAM
and the list show the biggest offender first 
1 Like
What does this function do? Set the game to the computer specs?
Yes, it’s a benchmark tool that is supposed to set the optimal settings for texture, model lod etc automatically (set max allowed value to fit pc specs).
1 Like
Ok, it could be two things:
-
You’ve got a large level. Is this just an apartment, or is it a city etc?
-
The editor will just keep filling up VRAM and won’t flush it. You’ll need to quit the editor, and then just open and go directly to this level. Then take a look at the tool. ( probably a good idea to make this map the default one )
1 Like
It is a large level. I’m making a Backrooms game where you start in an apartment and then fall into the backrooms that go on and on and on. Very large lol. Doesn’t making everything nanite negate the texture size issue? What are your suggestions for starting to get this to be managable?
1 Like
Are you using world partition, or streaming?
1 Like
You can look into virtual textures. There was a really good talk not long ago on the Unreal’s youtube that pretty much tackles this problem
1 Like
Ummmm maybe neither? I’ve never made a lever this big before. I’m guessing you might have found the issue. Which is better?
1 Like
Neither is better, they both use the same tech.
You might be using WP without knowing it, depending on what level template you started with.
WP will manage the grid for you and stream things in and out as you move around.
With level streaming, you can either setup volumes to tell the system when to load/unload, or you use blueprints, but you have more control.
1 Like
I’ve played with level streaming volume in the past where it loads portions of the level when you arrive at certain points, but doesn’t nanite make that irrelevant? If not, then I can try that.
1 Like
Nanite does not make streaming redundant, otherwise why would there be world partition?
You also still have the problem of using too many textures…
1 Like
Ah, ok so I should use world partition? Also, it seems 5.4.4 has changed it. I no longer see an enable button.
What do you mean using too many textures? How do I check that? Sorry, I only have about a year’s worth of knowledge of Unreal.