There are several articles online that attempt to explain good patterns and gotchas for a game loop. Two of the most oft-quoted and referenced, at least according to my informal analysis, are Fix Your Timestep and deWiTTERS Game Loop. They are both excellent resources, and I recommend reading them. What follows is my own interpretation of a basic game loop that attempts to keep rendering updates independent of physics updates, with actual running examples in JS.
The two most expensive operations in games I’ve built, computationally, have been drawing and physics. Separating these mean they can run at different speeds to accomodate slower or faster platforms.
For example, let’s say that when running at 60 frames (physics updates and frames drawn) per second, your game plays and looks great. But then you try your game on a retina iPad, where it runs at 20 frames per second, and on your cousin’s 4 year old laptop where it runs at only 45 frames per second. In both cases, the reduced speed either causes your game to be unchallenging or the simulation aspects to explode due to inconsistent timesteps.
And plus, what if you decide to go ahead with that realtime multiplayer expansion, where players are all playing the same game at the same time?
Do you target the lowest common denominator, and make even those people with super beefy gaming rigs run at 20 frames per second?
Nope, there’s another way.
Some Actual Code.
A possible solution is to separate your game code into two segments:
- Rendering / drawing to the screen
- Physics / updating all the world entities
This allows our game to render as fast as the platform allows (in the case of requestAnimationFrame, hopefully 60fps as long as drawing doesn’t take too long), while allowing physics and/or game state updates to happen at another arbitrarily less frequency.
It also handles accumulation of time between frames. In the real world, your deltas between frames will likely be dirty (16.666666ms target frame time, 33.333333ms physics timestep):
Delta Total What Does the Engine Say? 10ms : 10ms not enough for physics update 15ms : 25ms not enough for physics update 18ms : 43ms physics tick, leaving ~9.666666 remaining 16ms : ~25ms not enough for physics update
If physics are running at 30fps (33.333333 ms), then there will always be time left over that is less than a full physics timestep. That is why the delta is added to
this.accumulator above: unused time is carried over until it is able to be consumed.
But there’s still one more problem to solve. Won’t the game look jittery if renders are happening at 60fps, while physics are only being updated every other frame (30fps)?
ASCII Diagrams Might Help.
Let’s pretend that your game is spending most of its time calculating physics. Separating out the physics updates from the rendering (60 fps) could result in physics being calculated every other frame:
Time (ms): 0 16 32 48 64 80 96 112 Physics Ticks: * * * * Render Ticks: * * * * * * * *
Or even something crazy, like every few frames (every 100 milliseconds):
Time (ms): 0 16 32 48 64 80 96 112 Physics Ticks: * * Render Ticks: * * * * * * * *
However, even if you’re rendering at 60fps (16.666666ms between steps), if physics are only being calculated every 100ms, then the animations will appear very jittery, as the following example demonstrates:
There Is a Solution.
First off, every time the physics are updated, we need to store the previous state of the world. For the simple demos presented here, that involves only storing the previous position. In a more complex physics simulation, that could involve also storing rotation and transform matrices. Since the demos here use Verlet integration, the previous position is necessarily stored. Yay! FREEBIES.
Each time the game is rendered, we compute a ratio of how much time has passed since the last physics step, and how much remains until the next step. This effectively gives us a percentage of the “progress” between the previous physics update and now. In the demos, this ratio is automatically computed and passed as part of the
Using this ratio, we can render sometime between the most current physics step and the step before that, meaning our rendering is actually slightly behind our simluation. As stated anecdotally in Fixed-Time-Step Implementation, this is both imperceptible to the user as well as common practice on all major games.
The formula for linear interpolation of two positions given the ratio of time progressed:
renderPosition = (currentPosition * ratio) + (previousPosition * (1 - ratio))
And if we apply this to the previous demo:
Pretty smooth, eh? Any jumping near the edges are just because of crappy bounds checking.
Where to go from here? Well… to multithreaded land via web workers and beyond! Eventually. Ask questions!