FSR Frame Gen 4 (Redstone) works on Radeon RX 7000 series
AMD has some explaining to do.
A Reddit user, “AthleteDependend926”, says they found a workaround to enable AMD’s new FSR Frame Generation 4.0 on a GPU that is not RDNA 4. That matters because AMD currently limits the new frame generation path to RDNA 4, even though older cards can still use parts of the Redstone stack.
Last week, AMD rolled out FSR Redstone as a bundle of features rather than one monolithic toggle. It covers upscaling, frame generation, and ray reconstruction , and developers can pick what to ship, similar to how NVIDIA splits DLSS into separate components. The rollout has been quite messy. Radiance Caching is still not expected until next year, so the full “Redstone” package is not available yet.
This doesn’t mean Redstone doesn’t ‘work’ with RDNA3 or 2 series. AMD pushes owners of these GPUs into fallbacks. Upscaling can still work, but newer ML-based frame generation defaults back to FSR 3 on those GPUs. That stings for users who remember earlier signs that an INT8 path for FSR 4 could run on older Radeon hardware. They know it works, even if it means lower performance.
Redditor enables FSR FG 4.0 on RDNA3 GPUs
The claim here is that the new FSR 4 Frame Generation can run on RDNA 3 through seemingly the same FP8 emulation route already used for the upscaler. The setup is Linux-only and goes through Proton, plus patched vkd3d-proton D3D12 DLLs. The user also points to OptiScaler as the hook that exposes the FSR frame generation selector and forces the game to pick the 4.0.0 FG path. They say the key toggle is an environment variable, “DXIL_SPIRV_CONFIG=”wmma_rdna3_workaround” which suggests the fix is tied to RDNA 3 WMMA behavior in the DXIL-to-SPIR-V path.
Source: Reddit
Redditor also shared a performance comparison on a Radeon RX 7800 XT. FSR 3.1.6 Frame Generation reportedly takes around 0.07 ms, while the newer FSR 4.0 FG path takes 0.13 ms. That is a higher cost, and it fits AMD’s own positioning that the newer ML-based path is heavier.
Source: Reddit
None of this is official, and it is not a clean “flip a switch” change. It is a community workaround that depends on specific Proton and vkd3d-proton builds, plus third-party injection. Still, it raises an uncomfortable question for AMD: if emulation can make this work on RDNA 3 under Linux, why is there no supported compatibility mode for Windows, and why is RDNA 3 excluded at the feature level in the first place.
Source: Reddit
