Spatial Profiler showing 6.6GB memory & red frame times on a completely blank map

Summary

While optimizing a separate custom project using the Spatial Profiler, I noticed that no matter how much I aggressively cut down textures and static assets, the baseline memory usage would not drop. The profiler was also tracking references to native Fortnite assets (like vehicles) that were not present anywhere in my map.

Out of curiosity, I created a completely blank project using the default template just to check the baseline.

The results of the blank template:
Memory Usage: 6.5 GiB – 6.7 GiB (Triggers Orange “Warning” status)
Frame Time: 33.33 ms – 35.33 ms (Triggers Red “Critical” status)

This is on a project that literally only has two player spawners and a few default grid planes. Nothing else is on the map.

Is this actually normal, expected UEFN performance out of the gate, and something creators should just ignore? It’s a very weird performance curve to be handed a critical warning before placing a single prop.

My system: RTX 3090, 128gb of ram, ryzen 9 (12core)

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Memory Calculation

Steps to Reproduce

Create an island on blank template

Expected Result

Every stat on spatial profiler should be green since it is a completely blank map

Observed Result

Spatial Profiler showing 6.6GB memory & red frame times on a completely blank map

Platform(s)

PC

Upload an image

Video

see screenshots

Additional Notes

I get this result with all my projects. I initially thought i wasn’t optimizing my work enough but it seems like a deeper issue

FORT-1117699 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.

I wonder if disabling V-Sync will have an effect on Frame Time. I will check when I get the chance.

I was checking it in 3 of my maps after update to v41.00 and it was showing critical warning because of memory usage around 7 GB in all of them although they are very different regarding overall size and usage of unique actors in them, so I would not expect memory usage at the same level like this.

I watched the whole FN’s stream about it few days ago and it was said that Memory Snapshot should take into consideration loaded actors from the actual running game session and not from the editor. But when I searched for individual actors in Memory Snapshot I found there actors from the whole map even if there is big distance between them so all of them are never loaded at the same time in the actual game when the player is just at the edge of the map, while streaming is enabled and everything is set up for streaming and working correctly in edit session and also in live versions.

Then I checked the map that I am working on right now that has locations separated from each other by big areas of nothing (with streaming enabled of course) to optimize memory usage and it looks like it doesn’t take it into consideration, because it also showed memory usage around 7 GB again right from the start area that is on the edge of a long line of individual locations with free spaces between them. When I am in edit session, other locations are correctly not visible, because they are not loaded, but it looks like these memory tools doesn’t think so. Or there is just some issue why it shows in very different cases I tested memory usage right around 7 GB.

So I am just ignoring it for now, because it doesn’t make sense.