look at the performance hit from fsr 2.0 vs dlss there's also a fair bit of flicker on fsr 2.0, although overall it stomps 1.0
FSR is getting better definetly looks better then 1.0 maybe a lil slower though? hope for those that dont have DLSS capabilities yet
This is the game that myself and many others are anxiously waiting to test on new hardware. As previously discussed, the Ripperdoc section with all of the NPC's and commotion can bring the mightiest PC down to the low 30s fps. I talking DLSS on quality and max setting in-game and the NCP@ 4K! I truly want to see what a 4090, faster mobo and RAM with the top next gen Intel or AMD CPU can do. If that area and other heavy intense areas can pull 55fps or more with max settings and Psyco Raytracing, I will be impressed. On second thought 55fps is weak! We need to see above 60fps with no compromises with the exception of DLSS on quality. AMD, Intel and Nvidia......Get Busy!
I do not think it's matter of top new hardware, this is exactly what they want us to think! Probably, engine age, and not well optimized! But the main issue is that every new game / partnership, is getting rotten, all they want us to think is exactly what you just said!
Software will always advance with new features that will eventually need stronger and more advanced hardware. It always has. But whatever man. DO YOU!
This doesn't do crap because thats not how DLL's work. Any differences is delusion. When a DLSS enabled title does not find an appropriate DLSS library in its folder, or one that is older than the drivers own downloaded cache of dll libraries, it uses the downloaded cache. You cannot swap DLSS for FSR2.0 by replacing dlls, the imports do not exist.
Not sure what you mean. You can jump on YouTube and see lots of videos of the mod working on Radeon hardware.
Ok so I download and tried the mod on my 6600XT and it works. What this does is not replace the default .dll which is called "nvngx_dlss.dll". Instead the mod has it own called "nvngx.dll" and 2 supporting FSR 2 .dll files that go into your "Cyberpunk 2077\bin\x64" folder. The supporting FSR 2 files are called.... - ffx_fsr2_api_x64.dll - ffx_fsr2_api_dx12_x64.dll It then use's a reg file to modify some entries related to nVidia and Cyberpunk. They are called.. - EnableSignatureOverride.reg - DisableSignatureOverride.reg The contents of that EnableSignatureOverride.reg(which is what you use once you put the files in place) If I had to hazard a guess, the part related to Cyberpunk is probably changing which .dll Cyberpunk use's from nvngx_dlss.dll to nvngx.dll. Making the game use this persons custom .dll to enable the use of FSR 2.
Download and try it yourself. This was with the mod installed and DLSS set to Quality mode. It's buggy, as the modder him self notes, but you can tell it's working. Just look at that ghosting behind my car
I see now, its using a custom written implementation that exports DLSS functions but internally handles them as FSR techniques.
As a programmer I doubt that. If code in game`s binary links statically or dynamically to "nvngx_dlss.dll" library you can`t force it to use "nvngx.dll" instead. I would guess "nvngx.dll" is (global) NVIDIA library and mode just places it`s wrapper (with the same name) into game`s binary folder (locally).
TPU has done some testing at various resolutions and modes. Looks decent to me. Bet Nvidia will figure out some way to sabotage it. https://www.techpowerup.com/review/cyberpunk-2077-fsr-1-0-vs-fsr-2-0-vs-dlss-comparison/
