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
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#1600
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 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):
Open questions to settle first
Done when
RenderVKDebugSimulateDeviceLost).Sources: GamingOnLinux, Khronos news.
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"):
1. Linux: no. The 4.x techniques ship only as signed Windows DLLs ("Applications must use those signed DLLs"), through
amd_fidelityfx_loader_vk.dllplus 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.mdfor 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:
Proposed order:
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/
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
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.