What Does a Game Engine Actually Do Every Frame?

When a game runs at 60 frames per second, its engine repeats the same sequence of work sixty times each second. That sequence is known as the game loop, and it explains a lot about why games behave the way they do. Following a single frame from start to finish is a good way to see what the engine does, and why performance problems appear where they do. For a broader introduction, see our game engines explained for curious players.

Step one: read the input

The loop begins by checking what the player did. Did a button get pressed? Did the stick move? Did the mouse turn? The engine collects these events and passes them to the game's logic. The sooner input is read and applied within a frame, the more responsive the game feels.

Step two: update the game state

Next, the game logic runs. Characters move according to input and artificial intelligence, timers count down, doors open and scores change. Scripts and gameplay code decide what should happen. Because this work often runs on the processor, a scene with many characters or complex rules can become heavy even if the graphics are simple.

Step three: simulate physics

The physics system updates positions and checks for collisions. A falling crate hits the floor, a vehicle bumps into a wall, cloth moves in the wind. Physics is often calculated in fixed time steps so that behavior stays consistent, even if the frame rate changes. Many objects with detailed collisions make this stage more demanding.

Step four: animate

Animation systems blend prepared movements and apply them to skeletons or objects. A character may combine a walking animation with an aiming pose and a head turn. The engine calculates the final pose for every bone, which can add up when many characters appear at once.

Step five: decide what to draw

Before drawing, the engine figures out what is visible. It skips objects behind the camera, hidden behind walls or too far away to matter. This process, called culling, saves a lot of work. It also chooses detail levels, using simpler models for distant objects. The better the engine culls and manages detail, the more complex a world it can show.

Step six: render

Now the processor prepares instructions and sends them to the graphics card. The GPU draws geometry, applies textures, calculates lighting and shadows, adds effects like fog or reflections and finally applies post-processing such as color grading. Each of these steps takes time, and the total must fit within the frame budget.

The frame budget

At 60 frames per second, the whole sequence must finish in roughly 16.7 milliseconds. At 30, it has about 33. If any stage runs long, the frame is late and the player may notice a stutter. Developers use profiling tools to measure how long each part takes and decide what to optimize.

Why this matters to players

Understanding the loop explains common observations:

• A processor-heavy game might not improve when you upgrade only your graphics card.
• Lowering resolution helps when the GPU is the limit, but not when the processor is.
• Smooth physics and consistent timing depend on how the engine handles time steps.
• Loading new areas in the background can cause hitches if it takes too long.

Our article on why frame rate stutters even when the average is high shows how to spot some of these problems in practice.

Beyond the basics

Many engines spread work across several processor threads so that physics, animation and rendering preparation can run in parallel. Others add asynchronous loading to stream assets without freezing the game. These techniques make the loop more complicated but allow richer worlds.

Frequently asked questions

Is the game loop the same in every engine? The idea is similar, but the details differ. Engines organize and schedule these tasks in their own ways.

What is a frame budget? It is the amount of time available for all work in a single frame, based on the target frame rate.

Why do some games lock physics to a fixed rate? Fixed steps keep simulation results consistent regardless of how fast the game renders.