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.
Check if a log file named dlssg_to_fsr3.log is being created in the same folder where you placed the mod files. If it is, copy and paste its content here.
So, the mod is working. Your issue must be elsewhere. Is your FPS locked at 60, perhaps? If so, disable any frame limiter and/or VSync. It might not be ideal on a 60Hz display, but that's my best guess.
Working on stellar blade but some time have a fps drops for me i use on my rtx 3070ti without fg i can play around 60-80 fps and no problem. but when i use fg mod fps go to 120+ and normal frame around 60 FPS . but sometime i have a little bit lag i saw on STEAM overlay my real fps drop to 40-45 fps. my setting is maxout 2K DLAA.
I got no issue on RTX 3060 12GB when enabling Frame Gen in Stellar Blade, played the Demo at around 2-3 hours without closing the game and game was working silky smooth for me. I had no any huge frame drops like you mentioned, maybe you can try to reduce the Texture Quality to High instead of Very High or 4K Textures, because I was seeing like 10-11GB+ VRAM usage even on 1080p.
I love every part but after a recent mess up on my PC, i have tried to repeat what i did for Warhammer 40K: Darktide, it is told to not use it there but i've seen hundreds use it with no issue, So i tried using it again but now when i do it, Nothing is happening, I followed the guide, Did the registry edits first, added the files, ran the program but now it's not even making a log, it doesn't show it's working, I even turned my DLSS on and off with multiple tests, Turned off my Latency option before it all, Still nothing, No clue why i can not repeat what i did consider i followed the steps word for word, Even after multiple restarts, edits to my settings, even toggling FSR on then off, Nothing. I don't know what else i can do considering it worked before and no longer, it is on a Fresh OS because i had to reinstall but nothing is different from what i did before and i'm a 3070Ti. You got any idea Possibly? (Sorry for rant but when this patch works, it works WONDER's, Loved every part of it with any game that supports Frame Generation)
🔧 Troubleshooting Checklist – DLSSG-to-FSR3 Not Working (No Log, No Effect) If the mod worked before and now doesn’t — especially after a fresh OS install — follow this checklist: — 🟡 1. Undo the Registry Method (If Previously Used) • The old registry method is deprecated and unsupported. • It may conflict with the Universal Method and block the mod. → To revert: – Run RestoreNvidiaSignatureChecks.reg – Or reinstall your NVIDIA drivers to reset the registry. → Stick with the Universal Method only. — 🟡 2. Use a Supported DLL Name • The mod package includes version.dll, winhttp.dll, and dbghelp.dll. • They are identical in function and can be renamed to any of these supported names: – version.dll – winhttp.dll – dbghelp.dll – dxgi.dll – winmm.dll – wininet.dll → If one fails, delete it and try another name or just rename it. — 🟡 3. Verify File Placement • Place both dlssg_to_fsr3_amd_is_better.dll and the renamed generic DLL in the same folder as the game’s .exe file. → For Darktide, this is usually: ...\steamapps\common\Warhammer 40,000 DARKTIDE\binaries — 🟡 4. Check for Log File • After launching the game, look for dlssg_to_fsr3.log in the same folder. → If it’s missing, the mod didn’t load. — 🟡 5. HAGS Must Be Enabled • Required for Frame Generation to function. → Settings > System > Display > Graphics > Default graphics settings > Hardware-accelerated GPU scheduling → ON • Reboot your PC after enabling. — 🟡 6. Disable Overlays • Turn off overlays like: – MSI Afterburner / RTSS – GeForce Experience – Steam Overlay → Launch them after the game if needed. — 🟡 7. Select DLSS Frame Generation In-Game • Make sure you’re using DLSS + Frame Generation in the settings. → Do not enable FSR Frame Generation in-game if both options exist. — 🟡 8. Lower In-Game Settings Temporarily • Drop resolution and settings to minimum. → Reduces VRAM load and helps isolate the issue. — 🟡 9. Clean Mod Reinstall • Remove all previous DLLs. • Reinstall: copy dlssg_to_fsr3_amd_is_better.dll and one renamed generic DLL. — 🟡 10. Confirm Driver Version • Use the latest NVIDIA Game Ready Driver → Some outdated drivers may block the mod or not support FG properly. — 💬 Final Advice: Avoid mixing methods (registry + universal). Start fresh if needed. Try different DLL names and make sure the game is set to use DLSS Frame Generation. Share your log or setup if you're still stuck.
🔧 Regedit Method (Legacy Trick) This older method required editing the Windows Registry to redirect DLSS Frame Generation calls to the mod’s DLL by spoofing an RTX 40 series GPU. It tricks the game/system into believing you own an RTX 40 card by forcing the use of a specific DLL (usually version.dll).
Advantages: • Was previously the only workaround for enabling FG on unsupported systems • Enabled FG in games hard-locked to RTX 40 series
Disadvantages: • Affects your entire system, not just a single game • Can cause unexpected behavior or crashes • Risky – registry edits can be harmful if done wrong • No longer recommended – obsolete and not supported by current versions of the mod
—
🧩 Universal Method (Recommended) This is the currently supported and preferred method. It uses one of several compatible DLL names inside the game folder to inject the mod – no registry changes needed.
Advantages: • Safe and reversible • Per-game setup – doesn’t affect other games • More flexible – supports multiple DLL names like winhttp.dll, dbghelp.dll, or version.dll • Compatible with current and future mod versions
Disadvantages: • May require testing different DLL names for compatibility • Some overlays (like RTSS or Steam Overlay) might interfere and need to be disabled
—
🏆 Verdict: Use the Universal Method. It’s safer, cleaner, and only affects the game you’re modding. The Regedit Method is outdated and should no longer be used.
The upscaling and frame generation settings in the graphics settings have been separated, so frame generation can now be set regardless of the upscaling setting. For example, with NVIDIA RTX 3000 hardware, you could potentially choose NVIDIA DLSS upscaling with AMD FSR frame generation, and other similar mixed settings.
So this might not be needed anymore for anyone's interested
How can i make this work on Star Wars: Jedi Survivor? I have tried installing it in the game folder but it still says frame gen is not supported. I have a RTX 3080.
A log file is not created when I start Red Dead Redemption 2. I have a Lenovo Legion 5 Pro with an RTX 3070. I followed the Universal installation instructions and dragged and dropped version.dll and dlssg_to_fsr3_amd_is_better.dll into C:\Program Files (x86)\Steam\steamapps\common\Red Dead Redemption 2. What did I miss?
This has already been asked many times. Use the search function at the top of this page and search for Cyber Engine Tweaks or CET. Look for recent comments—just check the dates and click on Page Link; it will take you directly to the entire thread.
6348 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.
the option to turn on dlss frame gen is on but it doesn't work sadly
[19:38:13] [warning]
[19:38:13] [warning] dlssg-to-fsr3 v0.130 loaded. AMD FSR 3.1 Frame Generation will replace Nvidia DLSS-G Frame Generation. Note this does NOT represent a native
[19:38:13] [warning] implementation of AMD FSR 3.1.
[19:38:13] [warning]
[19:38:13] [warning] dlssg-to-fsr3 is freely downloadable from https://www.nexusmods.com/site/mods/738 or https://github.com/Nukem9/dlssg-to-fsr3/releases.
[19:38:13] [warning] If you paid for these files, you've been scammed.
[19:38:13] [warning]
[19:38:13] [warning] DO NOT USE IN MULTIPLAYER GAMES.
[19:38:13] [warning]
[19:38:17] [info] NVSDK_NGX_D3D12_Init_Ext
[19:38:17] [info] Hardware accelerated GPU scheduling is enabled on this adapter.
[19:38:17] [info] Present metering interface is available.
[19:38:17] [info] NVSDK_NGX_D3D12_PopulateParameters_Impl
[19:38:17] [info] NVSDK_NGX_D3D12_PopulateDeviceParameters_Impl
[19:38:24] [info] NVSDK_NGX_D3D12_Init_Ext
[19:38:24] [info] Hardware accelerated GPU scheduling is enabled on this adapter.
[19:38:24] [info] Present metering interface is available.
[19:38:24] [info] NVSDK_NGX_D3D12_PopulateParameters_Impl
[19:38:24] [info] NVSDK_NGX_D3D12_PopulateDeviceParameters_Impl
[19:38:30] [info] NVSDK_NGX_D3D12_CreateFeature
[19:38:30] [info] NVSDK_NGX_D3D12_CreateFeature: Succeeded.
[19:38:58] [info] Using assumed HDR luminance range: 0.0001 to 1000 nits
[19:38:58] [info] NVSDK_NGX_D3D12_EvaluateFeature: Succeeded.
[19:39:53] [info] NVSDK_NGX_D3D12_ReleaseFeature
Stellar blade
Red Dead redemption 1
Marvel Spiderman 1 and 2
FFXVI
Black myth wukon
So far this is only game it doesnt work with, I even Reinstall the old game I used this mod on to test mod and it still work perfectly for them
I don't know if you have first beserker Khazan but if you can you tell me if it works on your device
ADM FSR frame gen works in game option but it require me to use ADM fsr and it looks ugly compare to dlss
As a last resort, you could try OptiScaler. Join their Discord for help.
edit: I just realize that the latest update is from july 02
I deleted the game before that time so I can't tell anymore sorry
i use on my rtx 3070ti without fg i can play around 60-80 fps and no problem.
but when i use fg mod fps go to 120+ and normal frame around 60 FPS .
but sometime i have a little bit lag i saw on STEAM overlay my real fps drop to 40-45 fps.
my setting is maxout 2K DLAA.
If the mod worked before and now doesn’t — especially after a fresh OS install — follow this checklist:
—
🟡 1. Undo the Registry Method (If Previously Used)
• The old registry method is deprecated and unsupported.
• It may conflict with the Universal Method and block the mod.
→ To revert:
– Run RestoreNvidiaSignatureChecks.reg
– Or reinstall your NVIDIA drivers to reset the registry.
→ Stick with the Universal Method only.
—
🟡 2. Use a Supported DLL Name
• The mod package includes version.dll, winhttp.dll, and dbghelp.dll.
• They are identical in function and can be renamed to any of these supported names:
– version.dll
– winhttp.dll
– dbghelp.dll
– dxgi.dll
– winmm.dll
– wininet.dll
→ If one fails, delete it and try another name or just rename it.
—
🟡 3. Verify File Placement
• Place both dlssg_to_fsr3_amd_is_better.dll and the renamed generic DLL in the same folder as the game’s .exe file.
→ For Darktide, this is usually:
...\steamapps\common\Warhammer 40,000 DARKTIDE\binaries
—
🟡 4. Check for Log File
• After launching the game, look for dlssg_to_fsr3.log in the same folder.
→ If it’s missing, the mod didn’t load.
—
🟡 5. HAGS Must Be Enabled
• Required for Frame Generation to function.
→ Settings > System > Display > Graphics > Default graphics settings > Hardware-accelerated GPU scheduling → ON
• Reboot your PC after enabling.
—
🟡 6. Disable Overlays
• Turn off overlays like:
– MSI Afterburner / RTSS
– GeForce Experience
– Steam Overlay
→ Launch them after the game if needed.
—
🟡 7. Select DLSS Frame Generation In-Game
• Make sure you’re using DLSS + Frame Generation in the settings.
→ Do not enable FSR Frame Generation in-game if both options exist.
—
🟡 8. Lower In-Game Settings Temporarily
• Drop resolution and settings to minimum.
→ Reduces VRAM load and helps isolate the issue.
—
🟡 9. Clean Mod Reinstall
• Remove all previous DLLs.
• Reinstall: copy dlssg_to_fsr3_amd_is_better.dll and one renamed generic DLL.
—
🟡 10. Confirm Driver Version
• Use the latest NVIDIA Game Ready Driver
→ Some outdated drivers may block the mod or not support FG properly.
—
💬 Final Advice:
Avoid mixing methods (registry + universal). Start fresh if needed. Try different DLL names and make sure the game is set to use DLSS Frame Generation. Share your log or setup if you're still stuck.
—
🔧 Regedit Method (Legacy Trick)
This older method required editing the Windows Registry to redirect DLSS Frame Generation calls to the mod’s DLL by spoofing an RTX 40 series GPU. It tricks the game/system into believing you own an RTX 40 card by forcing the use of a specific DLL (usually version.dll).
Advantages:
• Was previously the only workaround for enabling FG on unsupported systems
• Enabled FG in games hard-locked to RTX 40 series
Disadvantages:
• Affects your entire system, not just a single game
• Can cause unexpected behavior or crashes
• Risky – registry edits can be harmful if done wrong
• No longer recommended – obsolete and not supported by current versions of the mod
—
🧩 Universal Method (Recommended)
This is the currently supported and preferred method. It uses one of several compatible DLL names inside the game folder to inject the mod – no registry changes needed.
Advantages:
• Safe and reversible
• Per-game setup – doesn’t affect other games
• More flexible – supports multiple DLL names like winhttp.dll, dbghelp.dll, or version.dll
• Compatible with current and future mod versions
Disadvantages:
• May require testing different DLL names for compatibility
• Some overlays (like RTSS or Steam Overlay) might interfere and need to be disabled
—
🏆 Verdict:
Use the Universal Method. It’s safer, cleaner, and only affects the game you’re modding. The Regedit Method is outdated and should no longer be used.
- The upscaling and frame generation settings in the graphics settings have been separated, so frame generation can now be set regardless of the upscaling setting. For example, with NVIDIA RTX 3000 hardware, you could potentially choose NVIDIA DLSS upscaling with AMD FSR frame generation, and other similar mixed settings.
So this might not be needed anymore for anyone's interestedupdate: put dll_winhttp files where the BBQ-Win64-shipping.exe
its located BBQ > Binaries > Win64
Thanks.
You .cannot. spend your money more wisely in this entire hobby. I invite anyone to disprove this.
But it didn't even work! help?
Thank you so much, G!