OptiFG Issues thread
Since there's been an increase in OptiFG issue threads, we've decided to relay them all to this central one as there's no need for another dozen of them.
OptiFG is currently on the backburner and isn't being actively investigated due to lacking free time. Nitec is still battling with HUDfix refactor branch which should hopefully improve OptiFG, but it's not a priority due to the whole "hacky" nature of the feature.
Helpful OptiFG documentation:
Now if you still want to make an issue report, please comment down below with:
- Game name (e.g. Talos Principle 2)
- Full Optiscaler version (e.g. OptiScaler_v0.7.7-pre8_20250418)
- GPU (e.g. RX 6950XT)
- OS (Win 11 24H2)
- Used automated or manual install? If on AMD/Intel and Automated, used DLSS inputs?
- Please describe the issue and steps to reproduce it
- And if possible, please attach Optiscaler.log and screenshot of game folder/Opti Overlay
Dead Space (2023) Crashes - https://github.com/cdozdil/OptiScaler/issues/181
Avowed random crashes with OptiFG - https://github.com/cdozdil/OptiScaler/issues/225
FG problems with HITMAN 3 - https://github.com/cdozdil/OptiScaler/issues/228
Frame generator closes itself - MSFS2024 - https://github.com/cdozdil/OptiScaler/issues/234
Hud fix crash stalker2 - https://github.com/cdozdil/OptiScaler/issues/235
Like a Dragon Pirate Yakuza issues - https://github.com/cdozdil/OptiScaler/issues/318
Rise of the Tomb Raider freeze when enable OptiFG before launching - https://github.com/cdozdil/OptiScaler/issues/399
Shadow of The Tomb Raider crash when playing with OptiFG for about 25 minutes - https://github.com/cdozdil/OptiScaler/issues/413
The Elder Scrolls IV Remastered - Active OptiFG Crash about 2 min - https://github.com/cdozdil/OptiScaler/issues/414
Clair Obscur Expedition 33 - Crashes after climb in Spring Meadows - https://github.com/cdozdil/OptiScaler/issues/423
Oblivion Remastered - Crash to Desktop Mid Game #434
Clair Obscur Expedition 33 crashes after loading an archive with OptiFG enabled #444
Game name (e.g. Clair Obscur: Expedition 33) Full Optiscaler version (e.g. OptiScaler_v0.7.7-pre8_20250418) GPU (e.g. RX 5700XT) OS (Win 11 24H2) Automated Install and DLSS INPUTS mini crashes every 5 seconds with optiFG check
Clair Obscur OptiScaler_v0.7.7-pre8_20250418 AMD RX 6650XT Win10 22H2 Manual install, DLSS inputs, Nvidia spoofing enabled
Bug description: OptiFG works on my system, but there is interface ghosting during camera movements without HUDFix. When HUDFix is enabled, it's like motion blur is forced and some frames are randomly flashing.
Game name: Clair Obscur: Expedition 33 Full Optiscaler version: OptiScaler_v0.7.7-pre9_Daria GPU: RTX 3060 TI OS: Win 11 24H2 Used automated or manual install? Tried with both automated and manual, same issue. Currently on automated install. The issue and steps to reproduce it: When FG Hud Fix is enabled in OptiFG, the game crashes after a few minutes of playing. This happens every time. With the option disabled, the crashed stop, but the menus are all messed up and make playing the game a really unpleasant experience. I tested the game without the FG Hud Fix and played for 3 hours without crashes, turned on FG Hud Fix and it crashed within a few minutes again. I tested with different limits for FG Hud Fix, the issue persists for 0, 1, 2, and 3.
is it possible to use nukems FG in games that don't have native frame gen? since clair obscur is one of the affected games that doesn't work with hud fix, i would use that, but the game has NO native frame gen, so i don't think you can even use nukems.
is it possible to use nukems FG in games that don't have native frame gen? since clair obscur is one of the affected games that doesn't work with hud fix, i would use that, but the game has NO native frame gen, so i don't think you can even use nukems.
It's my understanding that this doesn't work with nukems fg as DLSS would have to be turned on in settings, and for that to be possible the game would need to have at least FSR frame gen, or any kind of frame gen. I might be wrong, but when I tested it didn't work.
@Miyazono1 @arminolat Nukem mod requires the game having native DLSS-FG so it can convert it to FSR-FG, hence the name dlssg-to-fsr3. There's a reason the image on Readme shows Nukem coming from DLSS-FG and the installation steps mentioning DLSS-FG in-game.
@Miyazono1 @arminolat Nukem mod requires the game having native DLSS-FG so it can convert it to FSR-FG, hence the name
dlssg-to-fsr3. There's a reason the image on Readme shows Nukem coming from DLSS-FG and the installation steps mentioning DLSS-FG in-game.
yeah i thought so. since the game doesn't have any kind of native FG, you can't use nukems in clair obscur. thanks.
Just a heads-up regarding OptiFG and HUDfix.
Nitec has been working on HUDfix the last few days and he was able to identify some resource tracking issues which were now hopefully fixed. While the WIP build is currently in testing on the Discord server, testers have reported massively improved stability in Clair Obscur so far, some mentioned even playing for hours without crashes.
We could always use more testers for different games too.
Just a heads-up regarding OptiFG and HUDfix.
Nitec has been working on HUDfix the last few days and he was able to identify some resource tracking issues which were now hopefully fixed. While the test build is currently in testing on the Discord server, testers have reported massively improved stability in Clair Obscur so far, some mentioned even playing for hours without crashes.
We could always use more testers for different games too.
Could you please share the invite for the discord?
Could you please share the invite for the discord?
Linked in the Github frontpage Readme, end of the About section.
Game name and version:
Clair Obscur: Expedition 33 Steam Mods and mod versions used
https://www.nexusmods.com/clairobscurexpedition33/mods/39?tab=posts&BH=1
OptiScaler_v0.7.7-pre9 + Reshade Version 6.4.1 GPU
RX 7900 XT 4k resolution
Ryzen 9 5900X
OS
Windows 11 64 bit Used automated or manual install?
Manual
If on AMD/Intel and Automated, used DLSS inputs?
Yes, i am using DLSS inputs from optiscaler.
Also please mention in description which upscaler inputs are used (which upscaler you selected in game settings).
Frame generation with .ini file from this webside https://www.nexusmods.com/clairobscurexpedition33/mods/39?tab=posts&BH=
FG Active FG HUD Fix 1 or 3 FG Extended FG Allow Async Did you check the Wiki?
Yes
I have read: https://github.com/cdozdil/OptiScaler/wiki/Clair-Obscur-Expedition-33 https://github.com/cdozdil/OptiScaler/wiki/Hudfix-incompatible Please describe the issue and steps to reproduce it
Optiscaler is the only frame generator where I am getting up to 70-80 fps. Without it I am at 28 fps. "Lossless Scaling" as an alternative is not working for me.
I am running Optiscaler and Reshade almost without a problem. Both are configurated each time alone when I am starting the game. Then I start the game again and do not open optiscaler or turn/off reshade. This way I can play with both of them.
"All you need to do is for the dxgi.dll file, rename it to winmm.dll , make sure to have another dxgi copy for later. With it renamed to winmm, trigger the bat file that comes with optiscaler, when it asks to select 1-8, use 2, it should be exactly the name winmm.dll - This worked for me, I was able to turn off all the effects I find cluttering the screen, while still allowing pressing insert to change to fsr after graphics setting moving to dlss and then I can open reshade with home. Make sure to paste in the dxgi.dll back into the directory folder where all this is being completed after the bat file does it's thing."
Somone wrote to disable Anti-Lag in Adrenalin. It helped to remove the Screen tearing. But there are still shadows / black silhouettes moving later then models.
FG HUD Fix Limit 1 = no screen tearing buth with later moving black silhouettes of objects FG HUD Fix Limit 3 = no black silhouettes of objects but with screen tearing
Do you know how fix the later moving silhouettes? Is it possible to get something between it? I have attached
OptiScaler.log _(set LogLevel=0 and LogToFile=true in Optiscaler.ini,
The log is too big for an upload in github 64 MB. Here is a link to an upload on gdrive: https://drive.google.com/file/d/19kdGOQkXzFhciOTqXZrUCxAd9XcZBM64/view?usp=sharing
Screenshot of game folder (where you placed Opti)
Image
Screenshot of Opti overlay in-game _(opens with shortcut, default Insert)
Optiscaler is working without a problem, I have just to disable reshade one time for configuration. But I am using the Standard settings after install without changes. Except using the .ini from nexusmods and activating the options in Frame Generation. Image
i too wanna participate in testing, however the link for discord has expired, any active links to share please?
Discord link in Readme works fine, just checked it.
Using Vpn?
Using Vpn?
No i'm not using a vpn, you mean should i use it ?
No when i use vpn can't join any Discord server. I thought maybe its same for you
Since there has been an active increase in new issues without any basic info to help troubleshooting, we're releasing this Issue Report Template that should help troubleshoot without our magic 8 ball. Going forward, issues that do not follow the Template will be ignored.
Game name and version:
clair obscur expedition 33 (steam)
Mods and mod versions used
optiscaler v0.7.7-pre9 clairobscurfix
GPU
rtx 4060
OS
win 11
Used automated or manual install?
- [x] Automated
- [ ] Manual
nvidia
Also please mention in description which upscaler inputs are used (which upscaler you selected in game settings).
dlss dlaa
Did you check the Wiki?
- [x] Yes
- [ ] No
Please describe the issue and steps to reproduce it
game crashes in monoco introduction scene using hudfix
I have attached
- [
] OptiScaler.log (set LogLevel=0 and LogToFile=true in Optiscaler.ini, zip it if too big)
- [
] Screenshot of game folder (where you placed Opti)
- [
] Screenshot of Opti overlay in-game (opens with shortcut, default Insert)
Since a stable build is still away from being published, I'm uploading Pre11 and latest Pre12 here. Pre11 had some big improvements which testers reported worked quite well for Clair Obscure (some mentioned playing several hours without an issue with OptiFG even) - we're still recommending to use Lyall fix for Clair Obscure for removing the forced sharpening and similar. Pre12 continued with these revamps, but due to major code changes, might be less stable with OptiFG atm.
Anyway, try them out and see if it works for you. Please don't open new issue threads, if you have something to report, then do it here.
ok thank you!
I'm trying OptiFG on A Plague Tale: Requiem right now and either its crashing, not fixing the HUD or its "Working as intended" but actually its not displaying any generated frames. I find the last behaviour especially weird.
Tried with v0.7.7pre9 and v0.7.7pre11
Am I doing something wrong? On expedition 33 I am trying to activate FSR3 from Xess UQP+ and the game just stops rendering, I can hear the character moving but nothing is rendered after I choose FSR3.1 or 2. I also added nvidia spoof stuff and it works fine as it lets me activate DLSS. And files are on teh correct folder which is the binaries from sandfall folder.
In general, you can't use OptiFG on XeSS inputs in Unreal Engine games. As per Note 1 in the readme, XeSS UE plugin does not provide depth, so OptiFG is impossible to work correctly. Same goes for all the other upscalers, except XeSS and FSR4 which are the only ones that work properly. So DLSS inputs are the only ones that will work for OptiFG in Clair Obscur atm.
In short, XeSS UE -> Opti XeSS and XeSS UE -> Opti FSR4 work, everything else including OptiFG is not possible.
In general, you can't use OptiFG on XeSS inputs in Unreal Engine games. As per Note 1 in the readme, XeSS UE plugin does not provide depth, so OptiFG is impossible to work correctly. Same goes for all the other upscalers, except XeSS and FSR4 which are the only ones that work properly. So DLSS inputs are the only ones that will work for OptiFG in Clair Obscur atm.
In short, XeSS UE -> Opti XeSS and XeSS UE -> Opti FSR4 work, everything else including OptiFG is not possible.
Thanks, I did that and it worked, sadly I finished the game on xess prior to finding this out but I didn't lose much since I just wanted to try what the difference fsr3.1 one would make as I only have a 6900xt. I also want to ask, if I leave the game on DLSS and don't convert it to anything, does it still uses DLSS for me or just does nothing since I have an AMD gpu ?
You get free DLSS and Jensen starts sweating since his master plan was foiled /s
But nope, you can't run DLSS on non-Nvidia, Opti just automatically doess DLSS -> XeSS by default as you can see in the overlay.
You get free DLSS and Jensen starts sweating since his master plan was foiled /s
But nope, you can't run DLSS on non-Nvidia, Opti just automatically doess DLSS -> XeSS by default as you can see in the overlay.
Haha thanks, I bet he sweats all the time due to the thickness of that jacket but getting xess or FSR is fine by me. I don't even usually use them but exp33 was somewhat demanding and a UE5 game.. Otherwise I never use these type of stuff. Thanks for all the answers.
Hi guys,
Last night I think I have solved a few big resource tracking issues. This build is for specially for testing hudfix crashes. So what I am asking is testing games which are crashing (immediate or randomly) when OptiFG is enabled.
Let's see if we have some improvements 👍
Does anyone has issue with detecting fsr in Alan Wake 2 with drivers 25.6.3? I'm not able to select dlss and switch to use fsr4.
Game name: Alan Wake 2
Full Optiscaler version: OptiScaler_v0.7.7-pre12_20250707
GPU: RX 9070 XT
Drivers: 25.6.3
OS: Win 11 24H2
AMD/Intel and Automated with DLSS inputs
Added dlssg-to-fsr3-0.130-738-0-130-1742150748 and fakenvapi-v1.3.3
@MateuszKrawczuk aside from posting in a completely unrelated thread, you also completely ignored the part where in Wiki Installation - Nukem it says to copy ONLY the dlssg_to_fsr3.dll, nothing else. You broke it with the unsigned nvngx.dll. Deleting it should fix it back.
Next time try properly reading our guides as there is a reason they exist in the first place.