Comment on ELI5: How does Frame Generation even work?
graynk@discuss.tchncs.de 15 hours ago
It does so at the cost of latency. It does not actually predict the next frame, it renders two full frames and then interpolates one frame between them. So it looks smoother but your input also takes that much longer to be displayed on the screen
fulg@lemmy.world 15 hours ago
That is not strictly true, the actual latency increase is half the frame rate. Because the input is not just the frame image but also the motion vectors (in which direction the pixel moved) for the current frame. Frame gen also knows a lot about the image, like which bits have transparent pixels (which move in multiple directions at once) and when the game is done with the frame yet still has to wait for the GPU (time which can be used for more work with little impact).
Frame gen is much more involved than the old “motion smoothing” of televisions, the so called “soap opera” mode, which did increase the latency much more and had no knowledge of how the source image was built, so processing was much more involved.
Stuff like DLSS5 is supposed to use the same inputs (source images and motion vectors), now that is magic to me.
graynk@discuss.tchncs.de 14 hours ago
Yeah, I simplified it to keep it at ELI5 level, but you’re right
ampersandrew@lemmy.world 14 hours ago
It absolutely does increase latency though. If I’ve got the option for steady frame rates without frame gen, I’ll take it over frame gen. Frame gen was just about mandatory for Borderlands 4 at launch, and it gave me a convincing 80 FPS. After a performance patch, the game can get 60 FPS on my machine for real with a few of the settings knocked down, and it feels so much better.
dustyData@lemmy.world 14 hours ago
Isn’t that the thing NVIDIA was found to be lying about?
Natanael@slrpnk.net 11 hours ago
Yeah devs apparently saw it didn’t use internal engine data much at all
SkunkWorkz@lemmy.world 10 hours ago
That was for the Yassify filter.