<aside> 📖

Return to the main hub Miya’s Unreal Engine Notes

</aside>

Because a good game that doesn’t run is a bad game.

Many recommandations: Optimization on a Budget // Memory Management Blog Talk // Rethinking Performance: Nanite & Lumen / Supporting Systems //

First I’ll talk about general tools and good practice, then delve deeper into specific aspects of a game or the engine.

ALWAYS PROFILE WITIN A PACKAGED PROJECT

The Editor takes a lot of performance, especially CPU and Memory so the data is NOT usable in many cases. Profile in Development to have access to more tools, the performance should be more or less the same between Development and Shipping.

Useful Tools for Profiling

• Tools > Audit > Statistics is very useful for finding info such as total triangle count, memory size, texture size and everything.
• When testing a build, ALWAYS run the command-line argument -clearPSODriverCache. This will simulate launching on a PC for the first time for everything PSO and Shader-Loading related.
  • To run command-line arguments on a packaged game, take the .exe for the packaged game, create a shortcut for it, then right-click the shortcut, in the field “Target” you can add command-line arguments.
• The Memreport available with command memreport is a great tool for memory management. Source for most of it.
  • Count is the number of elements of this class that are loaded right now
  • NumKBytes is the size of the objects currently loaded
  • MaxKBytes is… I don’t know what honestly
  • ResKBytes is the combined size of UObject resources referenced by that Class. Will count duplicates multiple times (if 10 materials use the same texture, it’ll count that texture’s size 10 times.)
  • ExclusiveResKBytes is the “Amount of memory used by non-UObjects that are solely used by that class, such as sound buffers.”
• Unreal Insights is the main tool for profiling in Unreal Engine. See here Unreal Insights.