Frame creation on AMD – some confusion around performance and responsiveness
Frame creation on AMD – some confusion around performance and responsiveness
I’d love some assistance with understanding a few points about Frame Generation and input latency. I’m working with AFMF and FSR 3.0 for frame generation. There are aspects I’m still unclear about, especially regarding frame generation and its effect on input delay.
For instance, when you see “Frame Gen Lag,” does it indicate that the system is delaying frames by around 26ms while creating new ones? Or is it simply showing an overall added lag in inputs? Regarding the stuttering at 36%, it seems relatively high compared to my 118 FPS setup on a 60Hz monitor. Even with a slight drop to 150 FPS, I’m still above 60 FPS, so does the small reduction really matter? I know VSYNC can increase input delay, and I understand that generating frames adds extra latency, but it still feels confusing. For me, having a native frame rate of 45FPS on a 60Hz display shouldn’t significantly affect input lag. If I switch to COD:MWIII with FSR 3.0 and Frame Generation enabled, I’m currently achieving around 110 FPS. Does that extra latency from frame generation actually help lower input delay, or is it making things worse?
I’m also puzzled by the difference in reported frame counts when using AFMF versus AMD Adrenaline driver. The “FRAME GEN LAG” shows “N/A” with AFMF, but not with the driver I use. Could it be related to how each method tracks FPS?
In terms of input latency, I have different situations to consider. If I keep my monitor at 60Hz with AMD Anti-Lag and FSR 3 in Quality, I’m currently at 120 FPS. After enabling Frame Generation, I managed to reach 220 FPS. Does this improvement actually reduce input lag, or is it just a change in how the numbers are reported?
Thanks for your help—I’d really appreciate any clarification on these points.
Gen Lag may point to the delay added when using frame generation methods such as AMD's AFMF or FSR 3.0. In your situation, a "N/A" value suggests the software isn't tracking this metric, which might happen because of how these technologies are applied. Even with smoother visuals, micro-stuttering can still disrupt gameplay flow. More frames don’t always mean better performance; they might just increase input latency. This trade-off can make your experience feel less fluid if the stutter persists. When using these frame generation tools, you’re balancing higher perceived smoothness against possible input delays. If you're already hitting 110 FPS on a standard monitor without them, boosting to double the FPS may not significantly improve smoothness or cut down lag. The extra delay from generating frames could negate the gains. AMD’s Adrenaline driver overlay shows raw FPS, while FSR 3.0 accurately counts generated frames—this discrepancy likely stems from how each handles engine integration and monitoring. The issue probably comes from implementation differences. Adjusting settings and testing in your specific games will help you find the right mix of responsiveness and visual polish. If you’re considering FSR 3.0 for competitive play to squeeze more FPS, it might not be worth it right now; stick with FSR 2 at list until you see real benefits.
The main goal of frame generation is to smooth motion. It doesn't boost actual speed and adds extra delay. Anti-lag can reduce some of this delay, but it won’t fully fix it. For minimal lag, turn off frame generation and use anti-lag separately. Frame generation isn’t useful if your monitor can’t display more than 60 frames per second. Beyond that, the extra frames don’t make motion feel smoother—they just add more delay. When enabled, the engine shows frame 1 first, then holds back frame 2. The GPU combines them to create frame 2, which appears later. After a short pause, it displays the engine’s frame 2. Only generated frames influence what is shown. By the time you see frame 2, the data used came from several milliseconds earlier. This extra delay is the lag from both regular input and frame generation. So the final frame you see reflects an older input value plus the latency introduced by generation.
FSR 3.0 offers noticeable improvements over FSR 2.1, making Frame Generation optional while maintaining strong upscaling performance. The response was generated based on the conversation context.
Hey, that makes sense. However what I don't get then is... when it is ideal to use Frame Generation? Not in competitive games because of Input Lag. In single player games, if you have more than FPS than your monitor's max refresh rate (frequency) there is no point really as you use more GPU and CPU than you need, and if you are enabling it to reach 60FPS it might introduce some important input lag or causing micro stutters. You would normally only use Frame Generation to get extra frames to reduce input lag or to reach your target FPS, however, if you are under 60FPS with your 60hz it might not be very responsive and if you get 120FPS in a 144Hz monitor enabling Frame Generation is a bit pointless as you are introducing again input lag when your FPS were good and did not require Frame Generation to feel good visually and in terms of input response. I just don't understand when you will enable Frame Generation no matter how or which are objectively the right circumstances in which enabling it provides real benefits.
FSR 3 enhances your game by creating additional frames between the ones your GPU displays, giving a smooth, jelly-like feel. This approach increases latency. FSR 2 operates at a lower resolution and employs AI to upscale images, delivering clearer visuals with less impact on frame rate and latency. Think of spreading peanut butter: applying it one slice at a time is slow but precise, while dipping the bread in peanut butter offers a quicker, messier alternative that still achieves a satisfying result—similar to balancing performance and visual quality.
Are you turning off Frame Generation? AMD offers two options: FSR3, an upscaling method, and you can also turn on Frame Generation inside FSR3 or use the AMD Driver with AFMF, which provides the same functionality without upscaling. Unlike AFMF, FSR3's Frame Generation works better and accurately displays FPS. AFMF inserts frames directly at the driver level without relying on the game engine, just combining two rendered frames to create the third.
FSR3 serves as a self-contained upscaling method or can be paired with Frame Generation. AFMF operates at the driver level for frame creation, functioning separately from the game engine and possibly yielding less precise frames. You may apply FSR3 for upscaling without activating Frame Generation. FSR3 includes two key parts: the upscaling component that enhances image clarity by enlarging lower-res frames, and the Frame Generation part that produces additional frames to boost frame rate. FSR 3 utilizes motion vectors to achieve more accurate frame generation.
So then it is not like you said in the previous comment. FSR 3.0 is perfectly fine, no point in me going to use FSR 2.1 in competitive games if FSR 3.0 is available. Since I don't need to enable Frame Generation if I don't want to, avoiding issues with input lag, etc. My question was more like... if I have a 60hz monitor and I get 120FPS without Frame Generation, am I getting a benefit in terms of input lag by going to 200FPS thanks to Frame Generation together with AMD Anti-lag?
When playing a single-player game with low latency and well under your display's refresh limit, frame generation can help bridge the gap to higher performance. On a 144 Hz monitor, a game running at around 70 fps without extra frames can approach 144 fps using this method. This approach only makes sense in specific scenarios. The extra frames created by generating them on the GPU don’t actually boost the game’s speed—they’re just added by the engine. The real performance remains unchanged except for input lag, which stays consistent with what you experienced before enabling frame generation. There’s no gain from reducing input latency alone; anti-lag offers a clearer advantage when used separately. If your input lag is 20 ms, enabling frame generation might raise it to 40 ms, but with anti-lag it could drop to about 35 ms. Enabling anti-lag alone can lower that further to around 15 ms instead of 20 ms.