The problem now is that this can lead to tearing-where the next frame arrives in the middle of a screen update. Now when a frame is ready from the engine, it will show up on your display. One way of combating micro stutter is to disable vsync, but that has its own drawbacks. Neither of those is desirable, especially on a fast PC. Oops, there's some stutter.ĭepending on the game, this can be a frequent occurrence, and some people end up preferring a constant 30fps rather than aiming for 60fps and getting micro stutter. However, if there's a slight hiccup in the engine-a new texture needs to be loaded, or a new model, or maybe just some other background task-you can end up with a frame arriving 0.001 seconds too late. If an engine puts in a hard 60fps cap, it tries to have a new frame ready for each 60Hz screen refresh, and often other parts of the engine 'slow down' so that the frames don't finish too early, physics and netcode don't get messed up, etc. That's a reason to prefer much higher frame rate caps. Micro stutter occurs when the frame rate fluctuates just enough that you might average 60fps, but some frames come a bit early and others come a bit late. If it's not, the display shows the same frame as the previous update, giving you 30fps, and if a new frame is ready you get 60fps.

With a 60Hz monitor, the screen updates every 1/60 of a second, and either a new frame is available in time or it's not. Back in 2013, AMD discovered some driver optimizations that could help reduce microstutter.

Mtasa rokect