Unreal Engine Optimization Techniques

# CHAPTER 15

Unreal Engine Optimization Techniques #

1. Introduction #

2. Learning Objectives #

• Identify CPU Bottlenecks vs. GPU Bottlenecks.

• Use the stat fps and stat unit console commands.

• Understand the concept of "Draw Calls" and Material complexity.

• Implement Level Streaming (World Partition) to save RAM.

• Use the Unreal Insights profiling tool.

3. Finding the Bottleneck (CPU vs. GPU) #

• The GPU (Graphics Card): Responsible for drawing the pixels on the screen. If you have 8K textures, 5 million un-Nanited polygons, and complex Lumen lighting, the GPU will choke.

• The CPU (Processor): Responsible for the game logic. If you have 500 AI enemies running complex pathfinding calculations every single frame, or a massive physics simulation with 1,000 bouncing boxes, the CPU will choke.

4. The Magic Commands: Stat Unit #

• Type stat fps: Shows your Frames Per Second. (Goal: 60 FPS = 16.6 milliseconds per frame).

• Type stat unit: Shows four critical millisecond (ms) timers:

• Frame: Total time to render one frame.

• Game: How long the CPU took to calculate logic (Blueprints/Physics).

• Draw: How long the CPU took to tell the GPU what to do.

• GPU: How long the graphics card took to render the picture.

5. The Enemy: Draw Calls #

• If you have 10,000 individual rocks in a scene, the CPU has to make 10,000 separate Draw Calls. The CPU gets overwhelmed just giving orders, and the game lags (High Draw time).

• The Solution: Use Instanced Static Meshes (like the Foliage Tool uses). This tells the CPU, "Hey, here is one rock. Draw it 10,000 times in these locations." This is 1 Draw Call. Massive performance saved.

6. Managing RAM: Level Streaming & World Partition #

• Level Streaming: The world is chopped into chunks. When the player walks near "Zone B", the engine quietly loads Zone B into memory in the background. When the player leaves "Zone A", the engine deletes Zone A from memory.

• World Partition (UE5): Epic automated this process. You build one massive map, and UE5 automatically breaks it into a grid and streams the cells in and out based on the camera's location.

7. Visual Learning: Optimization Workflow #

1. Notice game is running at 25 FPS.
2. Open Console (`~`) -> type `stat unit`.
   Game: 5ms | Draw: 8ms | GPU: 38ms  <-- (The GPU is choking!)
3. Investigate GPU:
   - Are textures too large? (Drop 8K to 2K).
   - Are there too many dynamic lights casting shadows? (Turn off shadow casting on minor lights).
   - Is Lumen calculating bounce light on millions of glass objects?
4. Fix issue -> FPS returns to 60.

8. Best Practices #

• Event Tick is Evil: Do not use Event Tick (running code every single frame) in your Blueprints unless absolutely necessary. If you have 500 enemies all calculating Event Tick to check if they are near the player, your CPU (Game thread) will die. Use Timers (e.g., check once every 0.5 seconds) or Event-Driven logic (Overlap events).

9. Common Mistakes #

• Ignoring Texture Compression: Beginners download massive 8K raw textures from the internet and apply them to a tiny coffee cup in the game. That one cup is eating 150MB of Video RAM. Use appropriate texture resolutions (e.g., 512x512 for small props).

10. Mini Project: Profile Your Level #

1. 1. Open a heavy level (or spawn 500 characters in your template).

1. 2. Press Play.

1. 3. Press ~ to open the console and type stat unit.

1. 4. Press ~ again and type stat engine.

1. 5. Look at the numbers. Identify which thread (Game, Draw, or GPU) is the highest.

1. 6. Now, pause the game, and add 50 Point Lights directly next to each other. Ensure they all have "Cast Shadows" checked.

1. 7. Hit Play. Look at the GPU time. It will have skyrocketed because dynamic shadow calculations are the most expensive thing a GPU can do. Delete the lights to restore performance.

11. Practice Exercises #

1. 1. Define a "Draw Call" and explain why having 10,000 separate Draw Calls causes CPU bottlenecks.

1. 2. Explain the purpose of Level Streaming (World Partition) in an open-world game like *Grand Theft Auto*.

12. MCQs with Answers #

13. Interview Questions #

• Q: A level designer places 5,000 individual tree assets by dragging them one by one from the Content Browser. The game's Draw thread maxes out and FPS drops to 10. Explain what is happening under the hood, and how you would fix the level to run at 60 FPS using the Foliage tool.

• Q: Explain the difference between a GPU bottleneck and a CPU bottleneck. What commands in UE5 help you isolate the issue?

• Q: Describe how you would track down a memory leak or a severe logic bottleneck in a complex C++ project using Unreal Insights.

14. FAQs #

15. Summary #

16. Next Chapter Recommendation #