This, though, seems to be trying to sleep to slow down frame rate. What the? Maybe it's intended as some way to make all users' experiences suck equally even if they have fast boxes. Maybe.
Or to conserve power, why burn CPU and render at hundreds of fps when the output is limited to 60 or even 30?
I don’t need my machine loaded at 100% when playing slay the spire or dungeons of into the breach.
Which is why you use vsync, ensuring the game renders once for each frame your monitor shows, as opposed to having the game just guess when it should present frames - which can produce tearing or be at the wrong frame rate entirely.
Comments
Or to conserve power, why burn CPU and render at hundreds of fps when the output is limited to 60 or even 30?
I don’t need my machine loaded at 100% when playing slay the spire or dungeons of into the breach.
Which is why you use vsync, ensuring the game renders once for each frame your monitor shows, as opposed to having the game just guess when it should present frames - which can produce tearing or be at the wrong frame rate entirely.
What about when you want to render at half the vsync rate to conserve battery?
That seems easy, just keep the frame around in a buffer and send it twice?