Tuesday, November 18th 2025
VKD3D-Proton Adds FSR 4, Even for Older Radeon GPUs
While AMD's shiny new FSR 4 is ostensibly exclusive to Radeon RX 9000 series, there have been a number of successful attempts to get it running on older AMD Radeon GPUs after a rather sizeable mistake on AMD's part led to the FSR 4 libraries leaking online. Now, however, a Linux developer working for Valve has implemented a fix to get FSR 4 running on older GPUs right into the Proton translation layer responsible for running Direct3D 12 via the Vulkan API on Linux. Support for FSR 4 is only one of a bunch of updates to D3VK-Proton shipping in the latest 3.0 update.
As of version 3.0 of VKD3D-Proton, the translation layer responsible FSR 4 is present for RX 9000 series Radeon GPUs using the official method, but the Valve developer behind the project, Hans-Kristian Arntzen, has also implemented a "hacky emulation path" that allows FSR 4 to work on older Radeon GPUs. The developer notes that this implementation uses int8 and float16 cooperative matrix support, and that it may come at "significant performance cost." It is, as such, not officially supported by the default build of VKD3D-Proton, and the current official implementation is also mostly a first step in the process of getting FSR 4 implemented "in a more proper way" into Valve's Proton itself. Support for FSR 4 may not be relevant to devices like the Steam Deck, due to the increased performance hit, but it may become more important around the release of the Steam Machine, which still relies on RDNA 3 GPU cores but is expected to provide around the same performance as an AMD Radeon RX 7600M.
Source:
GitHub
As of version 3.0 of VKD3D-Proton, the translation layer responsible FSR 4 is present for RX 9000 series Radeon GPUs using the official method, but the Valve developer behind the project, Hans-Kristian Arntzen, has also implemented a "hacky emulation path" that allows FSR 4 to work on older Radeon GPUs. The developer notes that this implementation uses int8 and float16 cooperative matrix support, and that it may come at "significant performance cost." It is, as such, not officially supported by the default build of VKD3D-Proton, and the current official implementation is also mostly a first step in the process of getting FSR 4 implemented "in a more proper way" into Valve's Proton itself. Support for FSR 4 may not be relevant to devices like the Steam Deck, due to the increased performance hit, but it may become more important around the release of the Steam Machine, which still relies on RDNA 3 GPU cores but is expected to provide around the same performance as an AMD Radeon RX 7600M.

27 Comments on VKD3D-Proton Adds FSR 4, Even for Older Radeon GPUs
The legality or whether this is an official part of Proton yet is irrelevant. This is a Valve employee actively decreasing the value of AMD's latest GPU products. That's not how a good business relationship works. This is like if an Nvidia employee contributed to a Switch 2 emulator. You think Nintendo would just let their partner company undermine their value?
But they still have to work on: 'it comes at a significant performance cost' ;) .
Again, to make the comparison, this is like if an Nvidia employee contributed to a Switch 2 emulator. Do you really think that Nintendo wouldn't call up Nvidia and ask "hey, what the hell is your guy doing? We've bought hundreds of millions of $ of your hardware and this is how you repay us?"
You need to understand that in business, you have to maintain a certain level of professionalism with business partners, regardless of the precise legality or technical capability of something. Can Valve legally do this? Maybe, especially since AMD messed up and released the FSR 4 source code under an open-source license for a few minutes. Should Valve do this? Absolutely not.
Love AMD and I always will, but they haven't impressed me at all with their copycat tactics this round.
I haven't played around with FSR4 enough to comment on actual FPS numbers. I bought AMD because I don't want upscaling. I use TAA if FSR Native isn't available
Ok, serious answer: Linux drivers for AMD are open source. There is absolutely nothing AMD can do about this, other coping and seething. If they dont want their new products "devalued", they should leave their previously loyal customers out to dry. The only thing they could do is take away open source access to their hardware which would be a death sentence for AMD on Unix, not dissimilar to where they were 10 years ago with the RadeonSI drivers.
It's like tinkering with software to get strange things working :D
I like a lot more tinkering with stuff than playing games :)
FSR4 on 7700XT works, but to see a decent upgrade in performance you should use the performance mode, sometimes quality mode didn't give any advantage over native resolution, maybe just a bit crispiness in the image, better than TAA, on lower specs hw the perfomance drop will be even more, the first decent card to see a very little performance drop from fsr3 to fsr4 is the 7900xtx where the lost performance from 3 to 4 are in the 10% range instead of 25-35% of less powerfull card.
I can see your point when it comes to custom hardware, but the newest steam box is not that custom, so coming up with a different vendor for that wouldn't be that hard. And the VR thingie that Valve released is already using a Qcom CPU with SteamOS.
But when it comes to open source, intel has been the LEADING company supporting Linux for a really LONG time. See this as an example, Intel leading the charts 9 years ago:
www.linuxfoundation.org/blog/blog/the-top-10-developers-and-companies-contributing-to-the-linux-kernel-in-2015-2016
Heck, Intel is still a platinum member of the LF (whereas Nvidia and AMD are just silver members):
www.linuxfoundation.org/hubfs/Reports/lf_ar24_121524a.pdf?hsLang=en
AMD was nowhere to be seen back then. AMD's collaboration is really recent, and while great, they're still way behind Intel, even after Intel has decreased their contributions quite a lot, just take a look at the stats for the latest stable:
lwn.net/Articles/1038358/
AMD, Qcom and Nvidia are pretty much in the same ballpark when it comes to contributions. All of them together barely surpass the amount of contributions made by Intel.
AMD doesn't really have that much of a partnership software-wise, Valve has been doing lots of independent work for a really long time. In fact, until recently AMD had their own AMDVLK Vulkan driver, whereas Valve contributed a LOT to RADV (which is part of Mesa), both of which were pretty much independent. AMD finally gave up on that weird driver of theirs to focus solely on RADV:
www.phoronix.com/news/AMDVLK-Discontinued
blog.desdelinux.net/en/The-annual-report-of-the-Linux-Foundation-reports-that-it-only-allocated-2-of-its-income-to-the-Linux-kernel./