I’m going to prefix this with, moving forward it’d be helpful for our teams to avoid Core Creative Only posts here in the forums until we are ready to expand for that. We want to make sure that we can maintain focus on UEFN as efficiently as possible and avoid distracting too much from it as there are also different teams that work on different aspects between Creative and UEFN.
But at the same time I don’t want this to feel like it falls on deaf ears, and I happen to have insight into these in particular so I’ll address them as best as I can. Note these are all considerations for Core Creative, UEFN introduces a lot of additional complexity and hence is an entirely different conversation and one actively being discussed.
For anything I mention as bugs, please do continue to report them in the official Creative Discord. Frequency of reports is something taken into consideration for prioritization sake, so don’t worry if you or someone else has already reported it.
So for #6, you should be able to toggle to the Number version of the heatmap map. The “thermometer” keybind cycles between No Heatmap, Heatmap without Numbers, and Heatmap with numbers. The numbers should show you exactly how much over 100K you are. If not, then that’s definitely a bug.
For #7 (over 100K memory locks editing), definitely a frustrating experience we are aware of and we have a plan in place to improve this experience. Stay tuned.
#5 (deleting prop memory inaccuracy), preview should definitely be accurate and that’s a bug. As for the memory shifts, hard to tell for sure, but I believe the memory shifts are related to the fact that the thermometer is adjusting based on what you are looking at (which constantly changes as you work with props). Also something we’d like to address as well.
#4 (minimap at all times) due to how the minimap generation works in Core Creative the only way to render it all on the map is to actually having all the objects spawned, which would risk blowing out memory on platforms. BR’s minimap is a completely different system and is not feasible for how Creative works sadly. Since we are in the UEFN forums… as we introduce the ability for larger islands in UEFN, the original minimap system needs to change as it’s not going to scale well. It’s something that is actively being discussed. There are pros to the current system (like dynamically adjusting for runtime changes like player builds and destroyed structures) that are difficult to account for with other solutions. So this is definitely a TBD, but something we are aware of.
For #3 (massive memory increase on projects), it’s slightly related to #7 and my next few notes on #1/2.
For #1/2 (display of memory and memory impact), the current display of the thermometer isn’t ideal and its difficult to understand the impact of placing a prop. We want to show more information overall and have it be more comprehensive for debugging purposes and we have newer designs being discussed so that’s TBD. But we are definitely aware of that need.
Overall memory is a hot topic internally for sure, but also a difficult one. The feedback is definitely appreciated and helps us ensure we course correct as needed. But I do want to reiterate, that it’ll be helpful for our teams to maintain the focus of the UEFN Alpha forums on things related to UEFN. 