Guides/Graphics
Frame generation explained: more FPS, but what about latency?
Frame generation can double or triple the number on your FPS counter. It makes motion look smoother, but it doesn't make the game respond faster. Knowing why tells you when to use it.
How it works#
The game renders two frames, and the frame generation step calculates one or more frames in between from motion data. The generated frames are shown between the real ones. Your inputs only change what's rendered, not the generated frames, so the game responds at the real frame rate. To place a frame between two others, the newest real frame has to wait a moment, which adds a little delay; Reflex or Anti-Lag usually runs alongside to make up for part of that.
The versions#
- DLSS Frame Generation: NVIDIA RTX 40 and 50 series; multi frame generation (up to three generated frames) on RTX 50. Needs hardware-accelerated GPU scheduling.
- FSR Frame Generation: in supported games, on most current cards.
- AMD Fluid Motion Frames (AFMF): in the driver, works in many games without built-in support, on supported Radeon cards.
When it's worth it#
- Good: single-player games running at 60 FPS or more, on a high refresh monitor, where you want smoother motion.
- Not good: base frame rates below about 50 to 60 FPS (artifacts and noticeable delay), and competitive shooters where reaction time matters more than smoothness.
Judge it by how the game feels and by the real frame rate, not by the number on the counter.
Questions#
Does frame generation add input lag?
Is 120 FPS with frame generation the same as real 120 FPS?
Frametide measures FPS, 1% and 0.1% lows and stutters per minute in your own game with PresentMon, before and after a change, so you don't have to guess (Premium).