VcoreLeone
Posts: 289 +146
For me, the threshold for playable fps on controller is my monitor's g-sync compatible range, which is around 44 fps I noticed. For kb+m I prefer 60+, but for all games that have a rpg-like structure (inventory+ skill tree/crafting upgrades), I choose controller anyway. I'm really glad RR also makes PT run faster, cause those few percent are actually make or break on rtx3080. I stay above that 45fps 99% of the time in gameplay, less in cutscenes (seen 40-41fps at times), but fps in cutscenes doesn't matter much - some games have them pre-rendered at 30 fps and I don't complain either.now. likewise on a personal level. As long as something I'm interested in runs at 30+ fps in 1080p, I'm happy. I prefer realism in the image to resolution and FPSs.Whatever I buy today should deliver at least 45fps/1080/Ultra now, so it should last me a few years before going down 30fps.
Also, you just have to try using 1440p dlss/fsr in balanced modes over 1080p native, better looking and runs the same
All (SR/RR/FG) are separate functions, have separate files, and consequently different file/version names. Why update FrameGen file name to 3.5.0 if it's not really being updated for quality...... If they renamed 3.1.1 dll to 3.5.0 just for the sake of naming it, you'd complain that it's the same quality as old one."Cyberpunk 2077, for example, has been updated to use DLSS 3.5 but only for the ray reconstruction part; Super Resolution is still on version 3.1.1, and Frame Generation is on 3.1.13. Similarly, there will be games that use DLSS 3.5 Super Resolution, but don't integrate ray reconstruction. Still with us?"
I think keeping potential (and existing) buyers confused, dazed and dazzled by screen shots has been working very well for Nvidia.
I truly believe that having well informed people is very bad (especially) for certain political parties and definitely for certain technical companies!!!
How is not updating the name of something that's not being updated more confusing ? All you're really ranting about is that the new denoiser dlssd.dll file works fine with old super resolution files (dlss.dll) and frame gen files (dlssg.dll)
The user does not have to access or know the version of the file for any of those features to work, you know......
Last edited: