FSR 4 on Vulkan: integrate AMD FSR SDK 2.4 (FSR 4.1 ML upscaling + FSR 4 frame generation), FSR 3.1 as fallback #1600

Open
opened 2026-11-17 23:04:49 +00:00 by sky_line · 3 comments
Owner

AMD's FSR SDK 2.4 (released 2026-10-28) is the first official FSR release with Vulkan support for the FSR 4-era features, at parity with DX12:

  • FSR Upscaling 4.1.2 (ML);
  • FSR Frame Generation 4.0.2;
  • FSR 3.1.6.

FSR 4.1 now also runs on Radeon RX 6000 and newer, not only RX 9000. AMD's driver only upgrades DX12 games, so a Vulkan app has to integrate the SDK itself.

Goal

Integrate FSR SDK 2.4 alongside the FSR 3.1 work in #1555 (FSR 3.1 frame generation):

  • FSR 4 ML upscaling as an upscaler choice where supported (RX 6000+ per AMD; detect at runtime);
  • FSR Frame Generation 4.0.2 where supported;
  • FSR 3.1 as the fallback for every other GPU (NVIDIA, Intel, older AMD).

Open questions to settle first

  1. Linux: coverage says the Vulkan support ships through the SDK's own DLLs. Are there Linux binaries, or enough source to build them? If it's Windows-only, it's a Windows-only feature with FSR 3.1 on Linux.
  2. Licence and redistribution of the SDK binaries, and how they ship with our Windows package (AMD's GitHub release: binaries plus limited source).
  3. Fit with our pipeline:
    • the per-eye VR path;
    • the HDR / SDR frame-generation chain;
    • the UI layer composition (#1536 / #1517 design);
    • GPU-loss recovery: the upscaler and frame generation must re-init on the new device (#1550 restores DLSS/FG; FSR must follow the same rules);
    • #1557 (only FSR / DLSS as temporal AA).
  4. AMD Anti-Lag interplay (#1555 adds Anti-Lag).

Done when

  • On an RX 6000+ / RX 7000 / RX 9000 card (the AMD test box has an RX 7900 XTX), FSR 4 upscaling and FSR 4 frame generation are selectable and work.
  • Other GPUs fall back to FSR 3.1 cleanly.
  • It survives a simulated device loss (RenderVKDebugSimulateDeviceLost).
  • A/B against FSR 3.1 for quality and cost.

Sources: GamingOnLinux, Khronos news.

AMD's FSR SDK 2.4 (released 2026-10-28) is the first official FSR release with **Vulkan** support for the FSR 4-era features, at parity with DX12: - FSR Upscaling 4.1.2 (ML); - FSR Frame Generation 4.0.2; - FSR 3.1.6. FSR 4.1 now also runs on Radeon RX 6000 and newer, not only RX 9000. AMD's driver only upgrades DX12 games, so a Vulkan app has to integrate the SDK itself. ## Goal Integrate FSR SDK 2.4 alongside the FSR 3.1 work in #1555 (FSR 3.1 frame generation): - **FSR 4 ML upscaling** as an upscaler choice where supported (RX 6000+ per AMD; detect at runtime); - **FSR Frame Generation 4.0.2** where supported; - **FSR 3.1 as the fallback** for every other GPU (NVIDIA, Intel, older AMD). ## Open questions to settle first 1. **Linux:** coverage says the Vulkan support ships through the SDK's own DLLs. Are there Linux binaries, or enough source to build them? If it's Windows-only, it's a Windows-only feature with FSR 3.1 on Linux. 2. **Licence and redistribution** of the SDK binaries, and how they ship with our Windows package (AMD's GitHub release: binaries plus limited source). 3. **Fit with our pipeline:** - the per-eye VR path; - the HDR / SDR frame-generation chain; - the UI layer composition (#1536 / #1517 design); - GPU-loss recovery: the upscaler and frame generation must re-init on the new device (#1550 restores DLSS/FG; FSR must follow the same rules); - #1557 (only FSR / DLSS as temporal AA). 4. **AMD Anti-Lag** interplay (#1555 adds Anti-Lag). ## Done when - On an RX 6000+ / RX 7000 / RX 9000 card (the AMD test box has an RX 7900 XTX), FSR 4 upscaling and FSR 4 frame generation are selectable and work. - Other GPUs fall back to FSR 3.1 cleanly. - It survives a simulated device loss (`RenderVKDebugSimulateDeviceLost`). - A/B against FSR 3.1 for quality and cost. Sources: [GamingOnLinux](https://www.gamingonlinux.com/2026/10/amd-fsr-sdk-2-4-is-out-with-fsr-upscaling-4-1-2-for-older-hardware-and-vulkan-support/), [Khronos news](https://www.khronos.org/news/permalink/amd-fsr-sdk-2.4-brings-fsr-4-upscaling-and-frame-generation-to-vulkan).
sky_line added this to the Slipstream project 2026-11-17 23:04:49 +00:00
Collaborator

Findings on the open questions (AMD's SDK 2.4.0 release page and the GPUOpen FSR SDK manuals):

What ships for Vulkan: FSR Upscaling 4.1.2 (ML), FSR 3.1.6 (analytical fallback), Frame Generation 4.0.2, Frame Generation (Swapchain) 4.0.0. Ray Regeneration and Radiance Caching stay DX12-only.

Hardware (one correction to "Done when"):

  • Upscaling 4.1.2: RX 6000 / 7000 / 9000 and some Ryzen AI APUs.
  • Frame Generation 4.0.2 and the 4.0 swapchain: RX 9000 (RDNA 4) or newer only, plus Windows 11. The RX 7900 XTX box can test FSR 4 upscaling but not FSR 4 frame generation; it would stay on FSR 3.1 frame generation. Testing FG 4 needs an RX 9000 card.
  • Driver: Adrenalin 26.10.1 or later for the Vulkan path.

1. Linux: no. The 4.x techniques ship only as signed Windows DLLs ("Applications must use those signed DLLs"), through amd_fidelityfx_loader_vk.dll plus one effect DLL each (e.g. amd_fidelityfx_upscaler_vk.dll). There is no ML upscaler source. So FSR 4 is Windows-only, and Linux keeps FSR 3.1, which we already build from AMD's GLSL source.

2. Licence: the repo states MIT for the samples and points to docs/license.md for the rest; I have not read the DLLs' redistribution terms from that file yet. That needs reading before we ship the DLLs in the package.

3. Fit with our pipeline:

  • Frame generation can be dispatched manually and presented through our own swapchain. AMD's swapchain doc says such integrations just don't get driver-assisted pacing, and we pace ourselves already. So the HDR / SDR chain and the UI layer (#1517 / #1536) can stay ours; their swapchain replacement isn't needed.
  • It is a second integration path next to our source-built FSR 3.1: the loader API, the DLLs in the package (looked up next to the exe or the loader), a runtime query for what the driver / GPU supports, and re-creating the contexts on a new device after a loss (#1550's rules).
  • VR (per eye) and Anti-Lag interplay: not covered by the docs; to be checked in the integration.

Proposed order:

  1. Read license.md and confirm redistribution of the Vulkan DLLs.
  2. FSR 4.1.2 upscaling on Windows through the loader, chosen at run time on RX 6000+, falling back to our FSR 3.1 path everywhere else; device-loss safe. Testable on the 7900 XTX.
  3. FG 4.0.2 with manual dispatch into our chain on RX 9000, FSR 3.1 FG otherwise. Needs an RX 9000 card to test.

Sources: https://github.com/GPUOpen-LibrariesAndSDKs/FidelityFX-SDK/releases, https://gpuopen.com/amd-fsr-sdk/, https://gpuopen.com/manuals/fsr_sdk/techniques/frame-interpolation-ml/, https://gpuopen.com/manuals/fidelityfx_sdk2/techniques/frame-interpolation-swap-chain/

Findings on the open questions (AMD's SDK 2.4.0 release page and the GPUOpen FSR SDK manuals): **What ships for Vulkan:** FSR Upscaling 4.1.2 (ML), FSR 3.1.6 (analytical fallback), Frame Generation 4.0.2, Frame Generation (Swapchain) 4.0.0. Ray Regeneration and Radiance Caching stay DX12-only. **Hardware (one correction to "Done when"):** - Upscaling 4.1.2: RX 6000 / 7000 / 9000 and some Ryzen AI APUs. - Frame Generation 4.0.2 and the 4.0 swapchain: **RX 9000 (RDNA 4) or newer only**, plus Windows 11. The RX 7900 XTX box can test FSR 4 upscaling but not FSR 4 frame generation; it would stay on FSR 3.1 frame generation. Testing FG 4 needs an RX 9000 card. - Driver: Adrenalin 26.10.1 or later for the Vulkan path. **1. Linux:** no. The 4.x techniques ship only as signed Windows DLLs ("Applications must use those signed DLLs"), through `amd_fidelityfx_loader_vk.dll` plus one effect DLL each (e.g. `amd_fidelityfx_upscaler_vk.dll`). There is no ML upscaler source. So FSR 4 is Windows-only, and Linux keeps FSR 3.1, which we already build from AMD's GLSL source. **2. Licence:** the repo states MIT for the samples and points to `docs/license.md` for the rest; I have not read the DLLs' redistribution terms from that file yet. That needs reading before we ship the DLLs in the package. **3. Fit with our pipeline:** - Frame generation can be dispatched manually and presented through our own swapchain. AMD's swapchain doc says such integrations just don't get driver-assisted pacing, and we pace ourselves already. So the HDR / SDR chain and the UI layer (#1517 / #1536) can stay ours; their swapchain replacement isn't needed. - It is a second integration path next to our source-built FSR 3.1: the loader API, the DLLs in the package (looked up next to the exe or the loader), a runtime query for what the driver / GPU supports, and re-creating the contexts on a new device after a loss (#1550's rules). - VR (per eye) and Anti-Lag interplay: not covered by the docs; to be checked in the integration. **Proposed order:** 1. Read license.md and confirm redistribution of the Vulkan DLLs. 2. FSR 4.1.2 upscaling on Windows through the loader, chosen at run time on RX 6000+, falling back to our FSR 3.1 path everywhere else; device-loss safe. Testable on the 7900 XTX. 3. FG 4.0.2 with manual dispatch into our chain on RX 9000, FSR 3.1 FG otherwise. Needs an RX 9000 card to test. Sources: https://github.com/GPUOpen-LibrariesAndSDKs/FidelityFX-SDK/releases, https://gpuopen.com/amd-fsr-sdk/, https://gpuopen.com/manuals/fsr_sdk/techniques/frame-interpolation-ml/, https://gpuopen.com/manuals/fidelityfx_sdk2/techniques/frame-interpolation-swap-chain/
Collaborator

Licence (step 1): docs/license.md lists the signed DLLs under Kits/FidelityFX/signedbin/ (loader and effect DLLs) under the permissive MIT-style licence: redistribution is allowed, with the copyright and permission notice included; no hardware or platform restriction. Everything not listed there falls under AMD's stricter licence (binary-only redistribution, no reverse engineering), which doesn't touch what we would ship. So shipping the Vulkan DLLs in the Windows package needs only the notice in our third-party licences.

Source: https://github.com/GPUOpen-LibrariesAndSDKs/FidelityFX-SDK/blob/main/docs/license.md

Licence (step 1): docs/license.md lists the signed DLLs under `Kits/FidelityFX/signedbin/` (loader and effect DLLs) under the permissive MIT-style licence: redistribution is allowed, with the copyright and permission notice included; no hardware or platform restriction. Everything not listed there falls under AMD's stricter licence (binary-only redistribution, no reverse engineering), which doesn't touch what we would ship. So shipping the Vulkan DLLs in the Windows package needs only the notice in our third-party licences. Source: https://github.com/GPUOpen-LibrariesAndSDKs/FidelityFX-SDK/blob/main/docs/license.md
Collaborator

Plan (decided): one PR. FSR 4.1.2 upscaling and FSR 4.0.2 frame generation through the SDK 2.4 loader on Windows, chosen at run time, FSR 3.1 everywhere else. FSR 4 frame generation stays behind a setting, off by default, until it has been tested on an RX 9000 card; FSR 4 upscaling is tested on the RX 7900 XTX.

Plan (decided): one PR. FSR 4.1.2 upscaling and FSR 4.0.2 frame generation through the SDK 2.4 loader on Windows, chosen at run time, FSR 3.1 everywhere else. FSR 4 frame generation stays behind a setting, off by default, until it has been tested on an RX 9000 card; FSR 4 upscaling is tested on the RX 7900 XTX.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sky_line/Slipstream#1600
No description provided.