AMD released FSR SDK 2.4 on 28 October 2026, adding Vulkan support for its machine-learning upscaling and frame-generation technologies. The developer package also includes FSR Upscaling 4.1.2 integration for Radeon RX 6000 graphics cards and selected Ryzen processors with integrated graphics.
The SDK follows AMD’s broader FSR 4.1 support announcement and Adrenalin 26.10.1 driver release on 20 October. For players, the available features depend on the GPU, the game’s integration and whether it uses DirectX 12 or Vulkan. ML Frame Generation 4.0.2 remains limited to Radeon RX 9000-series GPUs or later.
What RX 6000 and Ryzen owners get
The expanded hardware support covers ML upscaling, which reconstructs a higher-resolution image from lower-resolution frames. It does not give every supported device access to the SDK’s ML frame generation or ray-tracing denoiser. Our Cyberpunk 2077 Update 2.5 breakdown shows why those features need to be considered separately when checking a game’s graphics options.
AMD uses different upscaling models to suit the hardware. Supported discrete Radeon GPUs and Ryzen AI Max processors run full models. More constrained integrated GPUs use a lightweight INT8 model that is less than half the size of the full INT8 version. The SDK selects the model automatically.
| Hardware | ML upscaling 4.1.2 | ML frame generation 4.0.2 |
|---|---|---|
| Radeon RX 9000 series | Full FP8 model | Supported on Windows 11 |
| Radeon RX 7000 and RX 6000 series | Full INT8 model | Not supported |
| Ryzen AI Max 300 and 400 series | Full INT8 model | Not supported |
| Supported Ryzen AI 9 300 and 400 series | Lightweight INT8 model | Not supported |
| Ryzen AI Z2 Extreme, Ryzen Z2 Extreme and Ryzen Z2 A | Lightweight INT8 model | Not supported |
Model size alone does not establish a frame-rate gain or identical image quality across devices. Results vary by game, resolution and quality mode. On integrated GPUs, shared-memory bandwidth, power limits and cooling also affect upscaling performance.
DirectX 12 and Vulkan have different upgrade paths
On supported hardware, compatible DirectX 12 games with FSR 3.1 or later can qualify for driver upgrades to ML upscaling through Adrenalin 26.10.1 or later. The ML frame-generation upgrade path requires a compatible FSR 3.1.4 or later integration and an RX 9000-series GPU.
Those version numbers describe eligibility, not a guarantee that every game will receive every effect. An application can also pin an effect to a specific version, opting that context out of driver-provided replacements.
Existing Vulkan games using FSR 3.1 do not automatically gain the ML effects through a driver update. Developers first need to integrate the new SDK libraries. Vulkan integrations using Upscaling 4.1.2, Frame Generation 4.0.2 or Frame Generation Swapchain 4.0.0 or later can then qualify for future automatic upgrades.
SDK 2.4 supports Vulkan 1.2 for upscaling and frame generation. Ray Regeneration and Radiance Caching remain DirectX 12 effects. Intel PresentMon frame-type reporting is also limited to DirectX 12.
AMD lists Windows 10 and Windows 11 as supported operating systems, with Windows 11 required for ML Frame Generation 4.0.2 and Ray Regeneration 1.2.1. The Vulkan release does not establish official Linux, Proton or Steam Deck support.
Driver requirements need a careful reading
AMD’s pages give conflicting guidance for the game-shipped APU and Vulkan functionality. The release blog says those capabilities come through the SDK DLLs without requiring a specific driver version. The SDK requirements page lists Adrenalin 26.10.1 or later for both. The published documentation does not resolve that discrepancy.
Driver-delivered upgrades and Driver-Assisted Frame Pacing have explicit Adrenalin 26.10.1 minimums. For handheld devices, AMD’s driver release notes direct users to the device manufacturer for device-specific drivers.
The Unreal Engine plugin also has a separate update schedule. It still uses Upscaling 4.1.1 and Frame Generation 4.0.1, with the newer versions planned for a later plugin release.
More consistent frame delivery on RX 9000
Driver-Assisted Frame Pacing lets the display driver handle final presentation timing. AMD says this produces smoother frame delivery and lower CPU overhead than the existing user-mode busy-wait approach. The change concerns when frames reach the display, so average FPS alone does not describe its intended benefit.
The feature requires RX 9000-series hardware or later, Adrenalin 26.10.1 or later, and Frame Generation Swapchain 4.0.0 or later. Frame generation must be dispatched during swapchain presentation. Unreal Engine integrations also require OverrideSwapChainDX12 to be enabled.
Other conditions include exclusive fullscreen or borderless fullscreen covering the display, VSync disabled and presentation within the display’s variable-refresh-rate window. These are conditions for this pacing feature, rather than a general recommendation to disable VSync in every game.
The driver selects the feature automatically when the requirements are met. Otherwise, the swapchain uses its existing pacing path. AMD’s validated configuration is Windows 11 with Hardware-accelerated GPU Scheduling enabled.
Ray Regeneration and older GPU fallbacks also change
Ray Regeneration 1.2.1 adds standalone ambient-occlusion and specular-occlusion denoising, alongside fixes to GPU memory-usage reporting. It still requires an RX 9000-series GPU or later, DirectX 12 and Windows 11.
Older compatible GPUs retain the analytical FidelityFX Super Resolution paths. The 3.1.6 upscaler receives precision and reprojection improvements, while analytical Frame Generation 3.1.6 and its Swapchain 3.1.7 gain Vulkan support. AMD lists RX 5000-series graphics or equivalent hardware as the baseline for those analytical frame-generation components.
Sources: AMD’s SDK 2.4 announcement, AMD SDK features and requirements, official SDK 2.4.0 release notes.