Version |
0.7.9, 0.9-pre5 |
Filename |
version.dll, winmm.dll (UWP/GP), dxgi.dll (avoid for UWP/GP)
|
OS |
Windows 10, Win 11 24H2 |
GPU |
RTX 2080S, RX 6950XT, RX 9070XT |
Inputs |
DLSS + DLSS FG, FSR3 (check Known Issues) |
Settings |
- |
FG-Settings |
If you’re using Nukems dlssg-to-fsr3, then use v0.120+ |
Known Issues |
-
Game auto enables FSR3 for AMD users (maybe Intel too) which causes the crash on boot as their FSR3 inputs by default aren’t compatible with Opti
-
FIX for stopping FSR3 inputs crashing - add r.FidelityFX.FSR3.UseNativeDX12=1 to game’s Engine.ini config file (check screenshot below, located in _%LOCALAPPDATA%\Alabama\Saved\Config\Windows_ or _WinGDK_) (might crash on switch to 3rd person perspective)
-
Or disable FSR3 inputs for Opti by setting EnableFsr3Inputs=false in OptiScaler.ini - in that case, you have to use DLSS inputs as they’re the only other available (recommended to use OptiPatcher to avoid spoofing overhead)
-
To prevent crashing past loading screen - set ColorResourceBarrier=0 in Optiscaler.ini (seems to be relevant only for DLSS inputs)
-
GamePass users might have to delete the Config folder to reset settings if not working after everything
-
For fixing UW issues where upscaler context breaks in cutscenes/dialogues, check link
|
Notes |
-
Slight ghosting on weapons seems to be a lingering effect, not related to Nukems mod
-
FSR4 requires Auto Exposure enabled (through the Overlay or INI)
|
Reported By |
congle & 𝔏𝔲𝔠𝔦𝔣𝔢𝔯, TheRazerMD |
