this post was submitted on 28 Sep 2025
44 points (100.0% liked)
Linux Gaming
21405 readers
295 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
No memes/shitposts/low-effort posts, please.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Frame generation shouldn't be a bottleneck on the CPU though, should it? That stuff is happening on the GPU. I know I saw a video about this stuff but I can't remember the real reason input lag increases with frame generation/interpolation.
Most games aren't bottlenecked by your CPU at all. It spends a lot of time waiting for the GPU to be done drawing you a picture.
"Why isn't the game doing other stuff meanwhile?" you might ask, and part of the answer is surely, "Why do stuff faster than the player can see?", while another part is likely a need to syncronize the simulation and the rendering so it doesn't show you some half-finished state, and a third part might be that it would be very confusing for the player to decouple the game state from what they see on screen, like you see yourself aiming at the monster, but actually it moved in between frames so your shot will miss even if the crosshair is dead on.
I didn't mean the game loop being bottlenecked, I said frame generation. But yeah, all that is also true, I know. 👍
Maybe it's not the CPU but with FSR either way the real frame rate drops which is why you get input lag. The game logic/game loop is only calculated per real frame. Which means if you take a 20% drop in real frame rate you are going to get 20% more input lag.
Isn't FSR supposed to give better performance/real fps?
it’s not. The whole point of FG was to take advantage of high refresh rate monitors as most games can’t render 500FPS even on the fastest CPU… alas, here we are with games requiring FG to get you to 60FPS on most systems looks at Borderlands 4 and Monster Hunter Wilds
Right, but FG shouldn't be touching the CPU in any way, should it? It should be a local thing on the GPU transparent to the CPU, unless I'm misunderstanding how it works.
It's not using CPU
Then I don't understand how it would affect the game loop negatively. I'll look into it though, will do some research.
Because the "delayed" or real input does not correspond to the image you see on the screen. That's why FG is most useful when you already have high base framerate as the input gets significantly lower and the discrepancy between the felt input and perceived image narrows.
Example:
30FPS is 33.3ms frame to frame latency (+ something extra from mouse to displayed image for input)
With 2x FG you get at most 60FPS assuming there's no performance penalty for FG. So you see 16.6ms + mouse to display frame to frame but input remains 33.3ms + mouse to display.
Same from base 60FPS 16.6ms to FG 120FPS 8.3ms perceived but 16.6ms+
Same from 120FPS 8.3ms base to FG 240FPS 4.15ms perceived...
As you can see the difference in input gets smaller and smaller between base FPS and FG FPS as you're increasing the base framerate.
This is however a perfect scenario that does not represent real world cases. Usually your base FPS fluctuates due to CPU and GPU intensive scenes. And during those flucfuations you will get big inpuy delay spikes that can be felt a lot as they suddenly widen the range between perceived image and real input... Couple that with the fact that FG almost always has a performance penalty as it puts more strain on the GPU so your base framerate and therefore input will be automatically higher.
https://lemmy.world/comment/19685489