DLSS and FSR updating

[FuriousMeow]

I didn't see this as a topic and thought maybe it could be useful for anyone looking to maintain the latest version of one, or both. I have tested both on a 4080 Super with DLSS Quality, DLAA and FSR AA. I didn't bother with FSR itself because after not liking DLSS I just didn't see the point. Plus FSR AA is pretty performant as is. 

This also seemed like the most appropriate sub-forum for this for the Korea title, but if not I apologize.

You can gain image clarity or performance, or nothing noticeable but being on the latest could just mean stability.

DLSS is pretty straightforward.

1) Download the latest dll from this site: https://www.techpowerup.com/download/nvidia-dlss-dll/ Upper left has the latest release, with previous releases below it. Usually updates the dlls before driver package updates.

2)Two locations driveletter:\KoreaFolder\game\bin\game\ and driveletter:\KoreaFolder\game\bin\editor\ 

3) Rename the current file extensions: nvngx_dlss.dll to nvngx_dlss.old or .orig

4) Download the latest dll from the site above to both folders. I haven't had a single issue, I've been doing this since release multiple times now. You can check the current file's version by right clicking it, selecting properties, Details tab, File version:

That's it for DLSS. Any issues, rename the new files to .new extensions and original files to .dll. 

FSR requires a bit more, now that AMD has changed from a single file to multiple - but its still pretty easy. With FSR AA I gained a bit of performance going from the latest version in the patch to the latest version in the SDK.

1) Go to the AMD website for the latest SDK: https://gpuopen.com/amd-fsr-sdk/  and locate the download for the latest SDK. INFO: My Firefox browser said there was malware in the file - there isn't, its from the official AMD website.

2) Rename the amd_fidelityfx_dx12.dll to amd_fidelityfx_dx12.old or .orig in driveletter:\KoreaFolder\game\bin\game\ and driveletter:\KoreaFolder\game\bin\editor\ 

3) Locate the downloaded SDK, open the zip file, navigate to: zipfile\FidelityFX-Samples-v2.3.0-prebuilt.zip\Samples\Upscalers\FidelityFX_FSR\dx12\x64\Release within the zip file, copy the 3 files below and paste to the driveletter:\KoreaFolder\game\bin\game\ and driveletter:\KoreaFolder\game\bin\editor\ locations.

4) Rename the amd_fidelityfx_loader_dx12.dll to amd_fidelityfx_dx12.dll in both locations.

Old on left, new on right fsr dlls:

 

And you're all set. If you have issues, you can just rename the .dll to .new or whatever and the .old or .orig back to .dll and you'll be all set. No need to remove the other two files with the AMD fidelityfx package, they don't do anything without the new amd_fidelityfx_dx12.dll file in place as a .dll extension. I haven't had any issues, I can't imagine there would be any because these are release files but just have to add that for informational purposes.

Edited August 26 by FuriousMeow

[Redeye]

Well I personally use a little program called DLSS swapper that allows you to download the latest DLL and remembers which version came shipped with the game. 
 

Easier then doing it manually and it does it on a program by program base.

[Viking1]

Folllowed this instruction carefully for FSR. I've been running 4k with no FSR and MSAAx2 and the game is stunning and on my system its fast. After following the above I switched to FSR for AA and back went to TE to load a mission. Mission loaded.. black screen except the MAP and HUD. Hmm. Back to msaa.

[FuriousMeow]

That's strange. Been working on my end, just updated to the latest nVidia drivers and will see if it's still working. 

EDIT: Oh right, you have an AMD card BUT I saw others with AMD cards doing this same process - albeit for other games - so it's odd it doesn't work for you. Especially since it launched into the game and displayed everything it seems... prior to mission load at least. Very bizarre.

Edited September 4 by FuriousMeow

[C6_Zorkaiev]

Same here with a 9070 XT. In VR, I get a black screen—except for the HUD—when the mission is loading. It works fine before that.

[Viking1]

I suspect the problem is the newest AMD driver. I'm going to roll it back and check.

[=S=NooBAsTiK]

05.09.2026 в 21:04, Viking1 сказал:

I suspect the problem is the newest AMD driver. I'm going to roll it back and check.

Nothing can change, AMD is very far behind Nvidia. We need to wait until the developers add a new FSR to the game. The picture with FSR4 looks much nicer than with MSAA. You can use FSR4 through OptiScaler, but then you cannot play online

[Viking1]

Im only using MSAA for AA not for upscale, so no texture distortion. Ground detail is very very good.

[=S=NooBAsTiK]

35 минут назад, Viking1 сказал:

Im only using MSAA for AA not for upscale, so no texture distortion. Ground detail is very very good.

FSR4 and DLSS 4.5. using AI to render an image is no longer just upscalers and the image becomes better than using MSAA and others. I turned on FSR4 in the game and now I don’t want to play without it, those nvidia are luckier they can already use DLSS 4.5.

[JG14_Jagr]

The latest AMD driver, 26.8.1 crashes the game when loading multiplayer for a lot of people.  We all rolled back to 26.7.1

[AndreiTomescu]

On 9/9/2026 at 12:08 AM, JG14_Jagr said:

The latest AMD driver, 26.8.1 crashes the game

Also in single player. The 26.7.1 is the way.

Also to avoid /reduce stuttering, tessallation on "application settings", and fps capped from ingame, not radon chill.

[Valis]

22 minutes ago, AndreiTomescu said:

...and fps capped from ingame, not radon chill.

In-game limiter doesn't work for me - only AMD chill.

FYI, 26.9.1 is available (and works OK) but you have to visit AMD drivers page to get it.

[AndreiTomescu]

5 hours ago, Valis said:

In-game limiter doesn't work for me

For me it works only in flight, but not in menus or flight map.

Thank you for the 26.9.1 tip. Didn't know.

EDIT: on the new driver's notes (26.9.1) the previous bug crashing Korea (there you can  read Starfield, but we fall in the same slot) is mentioned to be fixed  

Edited September 21 by AndreiTomescu

[Husar]

Default in game FSR AA (no upscaling )is good,  no smearing/ ghosting and 72 fps in VR but the new model is not able to maintain 72 FPS. I don't know how it works and if it has some kind of presets like DLLA where M is also fps heavy but K or other older are good for maintaining 72 fps in VR  with DLAA ( no upscaling).

[YoYo]

On 9/28/2026 at 3:22 PM, Husar said:

Default in game FSR AA (no upscaling )is good,  no smearing/ ghosting and 72 fps in VR but the new model is not able to maintain 72 FPS. I don't know how it works and if it has some kind of presets like DLLA where M is also fps heavy but K or other older are good for maintaining 72 fps in VR  with DLAA ( no upscaling).

Do we know which version of FSR AA in IL-2 Korea currently uses by default? I really like the FSR AA implementation here; the image quality is comparable to DLAA in terms of antialiasing, and the performance is excellent. If they ever update IL-2 Korea to a newer version of FSR AA, it might be worth reverting to the old FSR AA preset I think.

[Husar]

22 minutes ago, YoYo said:

Do we know which version of FSR AA in IL-2 Korea currently uses by default? I really like the FSR AA implementation here; the image quality is comparable to DLAA in terms of antialiasing, and the performance is excellent. If they ever update IL-2 Korea to a newer version of FSR AA, it might be worth reverting to the old FSR AA preset I think.

I don't know for sure, educated guess wound be FSR 3.1.3.

You can make a copy of current DLL for later use. I updated to  new version, but didn't test the performance good  enough in VR - I think my first test wasn't correct (I think that I forget to  rename the file), in 2D looks the same, but 2D is different story as there is plenty of FPS and 10 fps less/more wouldn't be noticed. 

Edited October 10 by Husar