Launch your game and disable vertical sync (V-Sync) in the settings menu. Then toggle frame generation.
This will result in screen tearing. To restore vertical sync and keep frame generation working properly, open Nvidia Control Panel, navigate to "Manage 3D settings", and then enable "Vertical sync" for your specific game.
Old framerate limiters don't work correctly. Check if they explicitly support frame generation first.
If you experience crashes while changing graphics settings in menus and are using an external overlay (RTSS, MSI Afterburner, Special-K, ReShade, etc...) try closing the overlay process first. Outdated versions don't support asynchronous frame generation.
Monster Hunter Wilds and the mod depend on REFramework.
If it stopped working after the update, it's likely because the game was patched and broke compatibility with REFramework. This is common after major updates.
You'll need to wait for the REFramework author to update it to match the latest game version. In the meantime, avoid updating the game (if possible), or check the REFramework Discord or its GitHub page for development updates or test builds.
In order to make frame generation work in Half-Life 2 RTX you need to put nvgnx.dll into Half-Life 2 RTX\bin\.trex and dlssg_to_fsr3_amd_is_better.dll near the exe (just to be sure put both of files in these folders)
Half-Life 2 RTX is a very recent and highly customized RTX Remix project, so compatibility with this mod might be limited or broken entirely at the moment.
Make sure you're placing the files (e.g., dlssg_to_fsr3_amd_is_better.dll and a wrapper like version.dll) next to the game's main executable. For RTX Remix games, that location can be tricky — you might need to look inside folders like Half-Life 2 RTX\build\bin\win64\ or similar.
That said, even with correct placement, the mod might not work due to how RTX Remix modifies the rendering pipeline. Hopefully compatibility improves in future updates, either from the mod itself or the game side.
Hello, while using this mod we shouldn't choose Nvidia DLSS Frame Gen, but instead AMD FSR right? As we can keep DLSS as upscaler, but we should choose Frame Gen method as FSR?
This mod replaces DLSS Frame Generation with AMD's FSR3 Frame Generation. So when you select DLSS Frame Gen in a game, the mod intercepts it and injects AMD's FG instead.
That means:
You can still use DLSS as your upscaler if you want (e.g. DLSS Quality, Balanced, etc.).
But you must enable DLSS Frame Generation in the game's settings — not FSR FG — for the mod to activate.
The FSR3 frame-gen logic is handled entirely by the mod, regardless of what the game natively supports. This is why the mod works even in games that don't offer FSR FG at all.
So to summarize: → DLSS upscaler + DLSS Frame Gen in settings = DLSS upscaler + FSR3 Frame Gen via mod
Ah thank you, I had been doing wrong then. I should always pick DLSS FG to make it use properly rather than AMD FSR.
In AC Shadows, when I pick DLSS FG, the camera movement doesn't feel smooth at all while giving me high FPS, but AMD FSR makes the movement feel so much smoother and fluid.
About frametimes, DLSS FG gives around 2 ms frametime while AMD FSR gives 15-17 ms. I'm not sure what I've been doing wrong for DLSS FG. In SM2, DLSS FG works perfectly and smooth.
AC Shadows also working smooth with DLSS FG option with the mod (v0.130 universal/dll version), running on 3060 12GB here and played like 36h so far..In SM2, both works smooth for me, using official FSR3.1 FG in that game as well
You don't need to update official FSR3.1 FG SDK file, I mean not that necessary..
It doesn't matter for me whether it's dbghelp or dll version when it comes to Nukem's FG Mod, dbghelp only helped me in Indiana Jones and The Great Circle back in the time other than that dll version generally works well and compatible with almost every DLSS3 FG supported games..
Thanks for all your replies, what I lastly want to ask is if I use universal mods, should I restore the signature again? Because I also had skipped signature checks.
If you're unsure whether you used the regedit method (disabling NVIDIA's signature check), simply reinstalling your GPU driver will reset it.
For the universal method, you’ll need to try each of the included renamed DLLs (e.g., version.dll, winhttp.dll, dbghelp.dll) until one works with your game.
that's literally impossible. the only one who has to explain is you lmao
The only thing that gets into other games is disabling the NVIDIA checks, because that's system-wide. The mod DLLs don't magically install on other games, however
Used v0.130-Universal/dll version in Last of Us Part 2 Remastered, worked well smooth enough but GPU Utilization is not pegged at %98-99 for some reason. There is not CPU Bottleneck between i5-12400F + RTX 3060 12GB however FPS boost is only around 20-25 FPS at 1080p compared to only DLSS enabled, it should have been at least 40 FPS+ like in many DLSS3 supported games. Drivers are up to date (572.83), getting avg 100-120 FPS on 1080p V.High Textures + High Settings + DLSS4 Quality + Nukem's DLSS FG Mod (with %77-80 GPU usage), V-Sync is set to OFF and there is no FPS limit at RTSS as well..Tried also older versions of the mod but issue still remains the same. How to fix this if anyone had the similar issue? Official FSR FG sucks in this particular game, bad implementation I'd say especially when it comes to smoothness..
Edit: I guess DLSS FG is either broken or very CPU demanding (single thread intensive) in this game, watched another video with i5-12400F again paired with a RTX 4060 Ti, that guy was getting same amount of FPS that I'm already getting eventhough he was using official DLSS FG. So game needs to be patched with further updates in best case hope scenario, mod's working fine..
Edit 2: I have finally figured out what's causing this. In order to make this mod work, you must turn off the DLSS FG and Reflex in the Launcher before start the game. Load your game and once you into the game, go to graphics menu in game and enable DLSS FG and with DLSS Quality or DLAA, this method would pegged the GPU at %98-99 almost all the time with a great FPS Boost, now getting up to 150-160 FPS with a 3060 12GB on 1080p High Settings and DLSS4 Quality.
There is a version.dll inside the dll_version folder in Universal, and there is also a version.dll in Cyber Engine Tweaks (CET). Since I have to choose one, the other one doesn’t stay active. When the version.dll from CET is not installed, I can activate Frame Generation using the version.dll from Universal. However, when the version.dll from CET is installed, Frame Generation doesn’t work because CET’s version.dll overwrites the one from Universal, which is required for Frame Generation to function. Additionally, using winhttp.dll prevents Frame Generation from working alongside CET. I was able to run Frame Generation together with CET by using dbghelp.dll instead.
Just wanted to share this in case someone else encounters the same issue.
Previously, I installed CET via Vortex, and when I manually installed the Frame Generation mod, CET didn’t activate. Because of this, I wanted to try manually installing both CET and the Frame Generation mod, and that’s how I noticed that the version.dll files had the same name. I don’t think the issue is with how I installed it, but if I overlooked something or made a mistake, I’d appreciate it if you could point it out.
A few days ago, someone had the exact same issue as you. Since the search function is available again, I recommend using it — search for Cyberpunk and look for a comment posted by karweng91 on April 1st.
Unfortunately, the search function still seems limited, as replies to comments aren't visible. So here's what I originally posted, just in case it helps:
1. Choose one of the included generic DLLs to use. Possible options are version.dll, winhttp.dll, or dbghelp.dll. In this example, we’ll use version.dll.
2. Locate your game’s installation folder. For Cyberpunk 2077, the typical paths are: - Steam: C:\Program Files (x86)\Steam\steamapps\common\Cyberpunk 2077\bin\x64\ - GOG: C:\GOG Games\Cyberpunk 2077\bin\x64\
3. Copy dlssg_to_fsr3_amd_is_better.dll and version.dll into this folder.
4. Done! A log file named dlssg_to_fsr3.log will be created after launching the game.
Yeah search function is limited, so why are you LeBlack posting the same cut\paste responses that are over a half a page long? Its not hard to see how this pushes very useful information about this mod off the front page... fast.
So I'm currently playing Indiana Jones and the Great Circle with this and it works flawlessy but one gripe I have is the very jarring screen tearing. Any idea on how to fix that?
I got a 4070ti, but returned it... because I couldn't justify the increase\cost in performance coming from this mod... AND A 3070.
No joke. Now I COULD see not knowing about this "mod" (DLSS3 enabler for all rtx) and upgrading to a 4080.
So if you are here, and have an RTX 2000 or RTX 3000, I recommend feeling this "mod" out. Spend a bit of time learning for yourself what this mod is and does. I promise you wont regret it.
6354 comments
This will result in screen tearing. To restore vertical sync and keep frame generation working properly, open Nvidia Control Panel, navigate to "Manage 3D settings", and then enable "Vertical sync" for your specific game.
Old framerate limiters don't work correctly. Check if they explicitly support frame generation first.
If you experience crashes while changing graphics settings in menus and are using an external overlay (RTSS, MSI Afterburner, Special-K, ReShade, etc...) try closing the overlay process first. Outdated versions don't support asynchronous frame generation.
If it stopped working after the update, it's likely because the game was patched and broke compatibility with REFramework. This is common after major updates.
You'll need to wait for the REFramework author to update it to match the latest game version. In the meantime, avoid updating the game (if possible), or check the REFramework Discord or its GitHub page for development updates or test builds.
Make sure you're placing the files (e.g., dlssg_to_fsr3_amd_is_better.dll and a wrapper like version.dll) next to the game's main executable. For RTX Remix games, that location can be tricky — you might need to look inside folders like Half-Life 2 RTX\build\bin\win64\ or similar.
That said, even with correct placement, the mod might not work due to how RTX Remix modifies the rendering pipeline. Hopefully compatibility improves in future updates, either from the mod itself or the game side.
You could try to get help on Nukem's GitHub page.
You're not doing anything wrong — it's likely a limitation for now.
This mod replaces DLSS Frame Generation with AMD's FSR3 Frame Generation.
So when you select DLSS Frame Gen in a game, the mod intercepts it and injects AMD's FG instead.
That means:
The FSR3 frame-gen logic is handled entirely by the mod, regardless of what the game natively supports.
This is why the mod works even in games that don't offer FSR FG at all.
So to summarize:
→ DLSS upscaler + DLSS Frame Gen in settings = DLSS upscaler + FSR3 Frame Gen via mod
In AC Shadows, when I pick DLSS FG, the camera movement doesn't feel smooth at all while giving me high FPS, but AMD FSR makes the movement feel so much smoother and fluid.
About frametimes, DLSS FG gives around 2 ms frametime while AMD FSR gives 15-17 ms. I'm not sure what I've been doing wrong for DLSS FG. In SM2, DLSS FG works perfectly and smooth.
It doesn't matter for me whether it's dbghelp or dll version when it comes to Nukem's FG Mod, dbghelp only helped me in Indiana Jones and The Great Circle back in the time other than that dll version generally works well and compatible with almost every DLSS3 FG supported games..
For the universal method, you’ll need to try each of the included renamed DLLs (e.g., version.dll, winhttp.dll, dbghelp.dll) until one works with your game.
The only thing that gets into other games is disabling the NVIDIA checks, because that's system-wide. The mod DLLs don't magically install on other games, however
THANK YOU
THANK YOU
I hope that everyone of the 1mil+ downloads gives you at least 1$ - you certainly have earned it
Edit: I guess DLSS FG is either broken or very CPU demanding (single thread intensive) in this game, watched another video with i5-12400F again paired with a RTX 4060 Ti, that guy was getting same amount of FPS that I'm already getting eventhough he was using official DLSS FG. So game needs to be patched with further updates in best case hope scenario, mod's working fine..
Edit 2: I have finally figured out what's causing this. In order to make this mod work, you must turn off the DLSS FG and Reflex in the Launcher before start the game. Load your game and once you into the game, go to graphics menu in game and enable DLSS FG and with DLSS Quality or DLAA, this method would pegged the GPU at %98-99 almost all the time with a great FPS Boost, now getting up to 150-160 FPS with a 3060 12GB on 1080p High Settings and DLSS4 Quality.
When the version.dll from CET is not installed, I can activate Frame Generation using the version.dll from Universal.
However, when the version.dll from CET is installed, Frame Generation doesn’t work because CET’s version.dll overwrites the one from Universal, which is required for Frame Generation to function. Additionally, using winhttp.dll prevents Frame Generation from working alongside CET.
I was able to run Frame Generation together with CET by using dbghelp.dll instead.
Just wanted to share this in case someone else encounters the same issue.
Previously, I installed CET via Vortex, and when I manually installed the Frame Generation mod, CET didn’t activate. Because of this, I wanted to try manually installing both CET and the Frame Generation mod, and that’s how I noticed that the version.dll files had the same name.
I don’t think the issue is with how I installed it, but if I overlooked something or made a mistake, I’d appreciate it if you could point it out.
A few days ago, someone had the exact same issue as you. Since the search function is available again, I recommend using it — search for Cyberpunk and look for a comment posted by karweng91 on April 1st.Unfortunately, the search function still seems limited, as replies to comments aren't visible.
So here's what I originally posted, just in case it helps:
Anyone can see this.
I got a 4070ti, but returned it... because I couldn't justify the increase\cost in performance coming from this mod... AND A 3070.
No joke. Now I COULD see not knowing about this "mod" (DLSS3 enabler for all rtx) and upgrading to a 4080.
So if you are here, and have an RTX 2000 or RTX 3000, I recommend feeling this "mod" out. Spend a bit of time learning for yourself what this mod is and does. I promise you wont regret it.
Thank you NUKEM9! Three cheers for NUKEM9!