Q1 Why does a packaged build run about 30% slower than in the editor? I thought it was supposed to be more efficient.
Q2 In editor, it doesn’t matter what size the screen is, the frame rate is the same. Why, in a packaged build, does the rate drop as the window size increases?
Full marks to anyone who can answer Q1.
For Q2, I know that a bigger picture has more pixels. But if the fps doesn’t change in the editor, why can’t it stay the same in the build?
At the moment, it looks like shipping my game with the editor is the best option, which can’t be right…
Cooking Insights provides a profiling method to gather and display information about the way packages are cooked. To record a cook session, start from the command line using the argument -trace=default,cook.
When you enable the cook channels, this adds a panel to Timing Insights called Packages. This displays a list of all the packages associated with that cooking event. For each package, there are statistics available, including: LoadTime, SaveTime, BeginCache, IsCacheCooked, and Asset Class. Each of these is displayed in a column that can be grouped and sorted.
Use the option Grouping > Path Breakdown - Package Name to generate a collapsible hierarchy view of the data. You can also group by Asset Class.
I noticed, while thrashing around with this, that if I make a new 5.1 proj, the frame rate is comparable to before, but it’s opening my 5.03 proj that dive bombs. Even on the first person default level.
Strange…
It makes migrating to the new engine a bit of a pain in the butt.
I haven’t been going through the entire change log as its size is comparable to the Bible, but they have most likely changed something for you to experience this issue. I am glad you don’t experience this in a new project at least.
Hopefully someone else is able to chime in on the subject.
Hey Clockwork! I know this is an old post but seeing as it’s relevant to me at this time I figured I would check in. I’m noticing the same issue. Only my framerate in the editor is 120 and in the packaged game it’s 30. I’m currently using 5.2.
For future answer seekers, it’s impossible to guess why a game is slow, so you should always measure the game to see exactly what is slow before guessing why anything is slow.
HEY, @ClockworkOcean (also, @Ari_Epic - I’ve watched your videos), have you figured out what is causing this? In the EDITOR, I’m getting 35-55, and in the PACKAGED GAME I’m getting 30-50.
There’s settings that I assume is causing this, but I have no idea, at the moment, which ones.
Some people suggested limiting the RESOLUTION and MAX_FPS, but that makes no sense to me. If the game can run 35-55 in the EDITOR with a bunch of assets cached, then it should run even better with assets cooked.
More people need to package their games so this issues is less ambiguous.
I just got better at finding out what was slowing things down. Not through profiling, but just by removing things and putting the back until I found the culprit.
You can just get it working better in editor, then it will work better in the packaged game.
I know it’s not ‘cool’ to say you didn’t profile stuff, but I actually don’t find it very helpful
There’s a pretty big learning curve before you can dig down and find the problem when profiling, it was just quicker for me to chop and change stuff until it worked.
Logically still doesn’t make sense why EDITOR > PACKAGED GAME, however, I’m still in the throws of optimizing. So, this is more of a preventative concern than anything.
I won’t start freaking out until I’ve finished my optimization pass and still have low FPS.
It’s steadily going up, so hopefully, when I’m finished it’s okay.
I certainly will take your advice and do this if, after finishing my pass, I still have issues. I really try to avoid avoiding issues, and take them on as early as possible, so I’m being a little premature here.
