If a game has a consistent 30fps is it rendering a frame every 33 milliseconds or might it render a bunch of frames at the first half of the second and just wait the second half of it because it has finished for that second?
I imagine some frames must be more computationally complex to render then others so if it always allocates 33ms it seems like if some of the harder frames come up later in the second it’ll miss the 30fps mark for that second.
But if it renders frames as quickly as it can and then waits it seems like the game would stutter.
In: 0
They generally try to spread the frames out evenly.
The issue is that when we say a game runs at a certain rate, there are actually two thinfs that have to run at that rate: simulation (the game logic: how things move and what they do) and rendering (how things look). Theae things generally have to be kept in sync and running as smoothly as possible. If the simulation gets out of time with the rendering, then either the rendering is drawing things that are out of date, or time slows down in the game as the simulation struggles to catch up. You may have seen this kind of slowdown on older consoles: this is one of the things that can cause it.
Time needs to run smoothly in games, so they try to spresd out the simulation frames. Since they spread out the simulation, the rendering has to stay close to that.
Latest Answers