Frame Time vs FPS
Gamers often optimize for average FPS or high Hz, but the most critical metric for smoothness is Frame Time (ms). A steady 60 FPS (16.67ms per frame) feels smoother than a fluctuating 100 FPS bouncing between 10ms and 30ms.
Analyze the relationship between your monitor's refresh rate and in-game framerate to optimize input lag, eliminate screen tearing, and achieve perfect frame pacing.
Because your FPS (240) exceeds your monitor's refresh rate (144Hz), the GPU is sending frames faster than the screen can draw them. This results in screen tearing unless V-Sync is enabled (which adds input lag).
Gamers often optimize for average FPS or high Hz, but the most critical metric for smoothness is Frame Time (ms). A steady 60 FPS (16.67ms per frame) feels smoother than a fluctuating 100 FPS bouncing between 10ms and 30ms.
Pro tip: Cap FPS slightly below your monitor's max Hz (e.g., 141 FPS on 144Hz) to keep G-Sync/FreeSync active without triggering V-Sync input lag.
Divide 1000 by your FPS. Example: 1000 / 60 FPS = 16.67ms frame time.
With G-Sync/FreeSync, cap FPS about 3 frames below your max Hz (e.g., 141 FPS on 144Hz) to prevent V-Sync lag.
Tearing occurs when your GPU renders frames faster than your monitor displays them (FPS > Hz), showing pieces of multiple frames simultaneously.
Hz is how many times your monitor refreshes per second. FPS is how many frames your GPU renders. Ideally both should match for smooth visuals.
Yes. The jump from 60Hz to 144Hz is very noticeable in fast-paced games, reducing motion blur and improving responsiveness by ~10ms.
Yes. At 60Hz each frame takes 16.67ms. At 240Hz it takes 4.17ms. This reduces the delay between GPU rendering and display output.