Makes AMD FSR 4.1.1 upscaling faster on Radeon graphics cards, on Windows and Linux, by replacing FSR 4's slowest shaders with faster ones. One file to swap, nothing else in the game changes.

1. Download the zip for your graphics card.

Not sure which you have? In Windows, open Task Manager, go to Performance and look at the GPU's name; on a laptop with two, the RX one is the one games use.

2. Choose a version. Each zip holds two folders with one file each:

If you are not sure, take exact.

3. Put the file in the game's folder. The game must already run FSR 4.1.1, for example through OptiScaler.

1. Find amd_fidelityfx_upscaler_dx12.dll in the game's folder (often next to OptiScaler) and rename it to amd_fidelityfx_upscaler_dx12.dll.orig. It must be version 4.1.1.2740.
2. Copy the amd_fidelityfx_upscaler_dx12.dll from the folder you chose into its place.

This works on Windows and, under Proton, on Linux. Linux users can instead use one launch option and leave the DLL alone.

4. Check that it worked. Open OptiScaler's overlay in the game. The FSR version reads 4.1.1-cyboman (or 4.1.1-lossy-cyboman; with the other zip 4.1.1-igpu-cyboman or 4.1.1-igpu-lossy-cyboman), and the upscaler time is lower than before.

To undo it, delete the file and rename the .orig file back.

• The gain depends on the output resolution. It is largest at 4K. At 1440p and 1080p the exact DLL's gain depends on the card: some keep most of it (an RX 7900 XT 30% at 1440p, an RX 6600 XT 24% at 1080p), others show little or nothing (the RX 7800 XT and an RX 7900 XTX at 1080p). The lossy DLL helps at every size, because it skips work instead of only doing the same work faster.

• It depends on your graphics chip, too. FSR 4 time saved at 4K, from testers' timing-kit runs and game reports so far:

  Graphics chip	Exact DLL	Lossy DLL
  Radeon RX 7000	15 to 35% in most reports; about 2% in two RX 7800 XT reports	29 to 49%
  Radeon RX 6000	from nothing to about 30%	23 to 48%
  Integrated graphics and handhelds	from a few percent slower to 6% faster	23 to 35%
  Intel Arc B580 (one report)	6 to 8%	31%
  GeForce RTX 3060 Ti (one report)	none	34%

  We do not yet know what decides where a card falls in its range. Most rows rest on a handful of single runs. Results by graphics chip, timing kit results.

• It only shows when the graphics card is the limit. If the processor limits your frame rate, the frame rate does not change.

• The exact DLL cannot change the picture. Its output was compared with AMD's byte for byte at 720p, 1080p, 1440p, 4K and 5K, in still and moving scenes. One intended exception: on RX 6000 cards under Windows, AMD's own file shows ghosting, and the exact DLL carries the fix, so its picture differs from AMD's there.

• The lossy DLL trades a little accuracy for speed. It runs FSR 4's neural network on every other frame and carries its result along with the picture's motion in between. Measured differences and comparison crops: exact and lossy compared. What the alternating cost means for frame caps and V-Sync: frame pacing.

One card, one game, as an example of the best case: a Radeon RX 7800 XT, Shadow of the Tomb Raider's benchmark, 4K output, FSR 4.1.1 Balanced. Your card and your game will give other numbers:

More games and resolutions: all results.

See what this release changes against the previous one, in pictures and figures →

Ultra Performance only, not representative of other modes. This release's gain is speed, and it is in Ultra Performance alone. In pictures it costs something there; the release page shows a typical frame and the lossy DLL against the exact DLL on every measure.

Help test it: the timing kit

Download the Windows timing kit (experimental, about 10 MB, version 2026-10-15.2): unpack, double-click fsr4time.exe, wait about 15 minutes (up to about 20 on a slow chip). It times FSR 4 with AMD's shaders and with these DLLs on your graphics card, checks that each DLL gives the same picture, and offers to send the result. Reports are in from eleven graphics chips so far; every further card helps, including GeForce and Intel Arc. On Linux and the Steam Deck: the Linux kit.

• New in the Windows kit (2026-10-15.2): a test of whether asking the driver for 64-wide waves speeds FSR 4 up on Windows, with a control that shows which width your driver uses. Details
• New in the kits (2026-10-15): this release's DLLs, each also without one of its two changes that may behave differently on RX 6000 cards, the RX 7600 and integrated graphics than on the card the project is developed on; and Ultra Performance (its figures are for that mode only). Results from those chips are the ones most needed now. What is new
• Optional: the kit asks for a name or nickname for the thank-you page.

What the kits do

You also need a DirectX 12 game in which FSR 4.1.1 already runs, with amd_fidelityfx_upscaler_dx12.dll version 4.1.1.2740.

Both DLLs have AMD's graphics-card check lifted (AMD's own file offers this FSR 4 only on desktop RX 7000 cards), so they start on any card whose driver can run the shaders: DirectX 12 with Shader Model 6.6. That is also why they must not go on an RX 9000 card, where a different FSR 4 would then start as well.

If the first zip is slower than AMD's file on a small RX 6000 card, try the second one: it differs only in one shader that is built smaller. Details: GPU support.

On Linux you can leave AMD's DLL in place and give the game the replacement shaders directly.

1. Download or clone this repository.

2. In Steam, add this to the game's launch options (keep anything already there in front of %command%):

   VKD3D_SHADER_OVERRIDE='Z:/path/to/fsr4-shader-performance-overrides/prebuilt' %command%
   

   Z: is how Proton sees your Linux root, so Z:/home/you/... is /home/you/.... For the lossy version use the folder prebuilt-lossy instead, after reading the WARNING.txt in it.

• The game must be using AMD's original DLL. The launch option does nothing while a DLL from this project is installed, because the files are matched to AMD's shaders.
• The version name does not change with the launch option; OptiScaler shows plain 4.1.1. The upscaler time is how you tell it applied.
• The prebuilt files do not fit every setup. They were made on an RX 7000 desktop card. On one tester's RX 6900 XT, Proton laid the same shaders out differently and the picture came out darker. If the picture looks wrong, build your own files: Linux guide. ./tools/check_prebuilt.sh <dump folder> tells you whether the prebuilt files fit.

If it does not get faster: Linux guide.

Each DLL is AMD's own file with the rewritten shaders swapped in and the version name changed. How that is done, and how to build it yourself: dll/. There is also a ReShade add-on that does the same without touching the DLL: windows/.

The scripts that rewrite the Linux shaders and build the files in prebuilt/ are in tools/ (they were in the top folder until release dll-2026-10-11.3; commands in older posts need tools/ in front).

In some games OptiScaler's upscaler time is only reliable with the frame rate uncapped. If nothing changes at all, check that the game really runs FSR 4.1.1 with AMD's DLL version 4.1.1.2740; other versions have different shaders. See shader variants.

• Nothing else changes. No game files are edited, and the output was compared byte for byte with AMD's at 4K, 1440p and 1080p.
• Game and OptiScaler updates can put the original DLL back; the launch option keeps working.
• Never in online games or games with anti-cheat. This changes the shaders the game renders with, and anti-cheat software can treat that as tampering. Single-player games only.
• Linux: do not set RADV_PERFTEST=cswave32 for a game that runs FSR 4; it adds about 1.1 ms.

The postpass rewrite is adapted from tools/fsr4cap/postpass_lds.py in bbport, a native Linux port of Bloodborne whose author found the slow store pattern and wrote the original rewrite for that project's own FSR 4.1.1 runtime. This repository ports it to the shaders vkd3d-proton generates, so it works in ordinary games.

The scripts are licensed under the GNU GPL v2 or later, like the project they derive from. See LICENSE. The prebuilt shaders are modified versions of AMD's, distributed under the same license together with AMD's notice; see prebuilt/NOTICE.md. Not affiliated with or endorsed by AMD.

Testers who have asked to be named are listed on the thank-you page.

This repository is maintained independently. If this project has provided value to you, and you want to help support the author, consider formalizing your support with a voluntary micro-donation: