Hello, i’m having a problem with the packaged build of my game. I have a map with several sub-levels that are marked with initially loaded so that they load with the game. The problem is that my persistent map loads and shows up but the sub-levels take a long time to load (depending on the packaging configuration sometimes it takes between 90-360 seconds to fully load everything), in the meantime the player is looking at the persistent level which is just an empty shell, which is far from ideal. What might be associated is that my performance is terrible (even after all the levels are loaded) and the framerate is all over the place, going up and down between 15 - 50 fps. In PIE i run it at 120 fps without a problem and loading times are pretty decent. I didn’t have this problem in 4.20 and i started getting it when I migrated to 4.22. I’ve tried a lot of packaging configurations, but it doesn’t matter if it’s development, shipping, for distribution or not, using paks or nor, compressed or not, it always does the same behavior, sometimes slightly faster, sometimes slightly slower. Any idea what might be causing this? I won’t be able to package and distribute my game if i dont fix this.
It’s likely less to do with your package configuration and more to do with how your game is made. It could literally be anything; your shaders might not be optimised, you might be using really heavy meshes with LODs, you might be calling an event tick for way too many events and thus essentially capping the framerate.
Because it’s intermittent framerate issues, I’d assume it was a blueprint issue. Are you using event ticks at all?
I mostly just updated from 4.20 (where the packaging was working flawlessly) to 4.22, i didn’t change the project much after that. If it was a tick issue i would notice it in PIE or standalone, but they run smoothly.