Correct GameLoop Frame timing
1 month ago Edited by Adrian on July 20, 2018, 11:54 a.m. Reason: Initial post
So, I've come back to work on my game engine a little bit more. And this is only possible by Casey providing the best content to learn from I ever came across. Without Handmade Hero this hobby wouldn't be anything I could really spent time on because of the lack of good documentation. Especially for game engine related stuff as mostly anybody uses Unity or whatever.
However there is one part, I can't really figure out how to get right and its -- TIMING.
From my understanding and from anybody elses too a basic game loop seems to look like the following pseudocode:
And this is basically how I am doing it too. For the future I would like to play around with some basic physics simulation. And to be able to I have to get timing right. As I've seen in more complex Systems and also in Handmade Hero the estimated frame time is passed to the game itself so that the game can advance it's physics and world simulation based on the time spent until the next frame is displayed.
I really want to understand this and get this right since it bothers me a lot!
As I am using MacOS X I use mach for timing and OpenGL to "blit" the RenderBuffer to the screen. Back when I was starting with this project I didn't quite understand that using mach_wait_until(NStoSleep) makes no sense when vSync is enabled. And I was always wondering why my animations where always kind of stuttery but I couldn't really tell if they actually were.
Knowing that I commented mach_wait_until(NStoSleep) and suddenly I got super smooth animation movement. Even though my FPS were between 58-62 but this could be caused by calculation and rounding problems I guess.
So how would I ever be able to create an !!halfway!! percice physics simulation when my frame timing code results in quite jittery animations?
I get that vSync is used to prevent tearing as it swaps the Buffers at the exact same time when the Screen refreshes. But as I understood when vSync is enabled the program waits at [GlobalGLContext flushBuffer] until the swap happened. So I gess that the OpenGL timing is more percice than mine.
So my Questions are:
1. Am I doing something wrong with my timing code or is this behaviour expected when vSync is disabled?
Moreover if this behaviour is expected, how are smooth animations with 30fps achieved since vSync syncs to 60fps?
2. Or can I vSync to 30fps somehow?
3. Is there a way to get a more percice timing, as my timing seems to vary a lot even when run without XCode. There has to be a way to get even smoother animations without vSync enabled right?
4. And how is timing handled right now in Handmade Hero since BEGIN_BLOCK(FramerateWait) until END_BLOCK(FramerateWait) is completely "commented out" through if 0? Only through vSync?
5. I am not multiplying character movement with the expected frame time as I was not sure if my timing was correct anyways. Could this produce smooth animations without vSync?
Here is all the timing code thats present in my current build:
This code produces smooth animations as vSync is enabled and mach_wait_until(now + (SleepNS)); is not used. But when I disable vSync and use mach_wait_until animations get jittery which makes me think my timing is corrupted. It wouldn't make sense to base physics on corrupted timing...
I deleted everything that has nothing to do with timing to increase readability.
If I got something wrong please correct me. Also feel free to point my to any resources.
I would really appreciate your help!
Thank you very much, and have a nice day!
1741 posts / 1 project
Correct GameLoop Frame timing
1 month ago Edited by Mārtiņš Možeiko on July 20, 2018, 6:17 p.m.
1. Small fluctuations are expected without vsync. If you want 30fps you can vsync to every second frame. Or better - use delta time to adjust all your motion.
2. Depends on graphics API, but with D3D or OpenGL you definitely can (no idea about Metal).
3. You get smoother animations by usuing delta time for all your motions.
4. Yes, it is handled only though vsync. But Casey mentioned that he will add code to do timing and sleep if necessary. Because you cannot rely only on vsync - user can forcefully turn it off in GPU driver settings.
5. Yes, you want frame time in your motions.
For simple games maybe you can get away without using frame time in calculation motion and physics. But in more physics oriented games it is very important. For real physics simulations you actually want to fix your physics time step. Without fixing it the variance in frame times can lead to various artifacts like box falling through floor or similar.
On basic level physics (including character motion) simulation should look like this:
There are various modifications on this to achieve better precision when delta is not multiple of physicsUpdateDelta or similar. Here's more details: https://gafferongames.com/post/fix_your_timestep/
Don't use vsync as synchronization for your update time step. Different monitors have different vsync's. Sure majority is 60Hz, but what if user has 120Hz, what if 144Hz? If you don't use frame time in calculation motion/physics then your game will run 2x or more faster on these machines. You don't want that. And what if user has GSync or FreeSync monitor - these can do arbitrary "vsyncs", game should run as fast as it can and monitor will handle "sync-ing".
This is a problem that many old DOS games had. They were made for 8086 CPU which run at 4.77MHz, but later when 386 or 486 CPUs came out with much faster MHz then many games were not playable - everything moved super fast because game updated fixed movement per frame. Turbo button reduced clock rate down to smaller number so games were playable: https://en.wikipedia.org/wiki/Turbo_button If game update would have used timer to calculate movement, this would not be a problem.
Use vsync only as feature to limit rendered frame count per second. Either to avoid rendering more than monitor is capable of. Or to limit CPU usage to save battery (important on laptops).
Correct GameLoop Frame timing
1 month ago Edited by Luke Salisbury on July 21, 2018, 3:19 a.m. Reason: typos
I am most likely wrong, but should it not be mach_wait_until(now + (SleepNS / (sTimebaseInfo.numer / sTimebaseInfo.denom))); since now is in mach_time ( https://developer.apple.com/library/archive/qa/qa1398/_index.html ) and SleepNS is in nanoseconds.
Based on mmozeiko reply, If you don't separate physics update, Can I also recommend having a max value for the frame delta, so if a person can't hit a certain FPS target, they wouldn't warping around but slow down instead, as it was something I had issues with when working on Mokoi.