113
Valve's Linux graphics team has been working a lot around FSR4 and ray-tracing as some of their common themes recently for RADV driver improvements.
In case anyone's wondering where this comes from like I was...
this post was submitted on 17 Jul 2025
113 points (99.1% liked)
Linux Gaming
20356 readers
38 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
No memes/shitposts/low-effort posts, please.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
I should probably add that some of this work is on RDNA3 FSR4 support, which isn't even supported on Windows. It's not amazingly fast, but it's now faster than native and that might be enough to make it worth it (especially in the cases where it improves image quality due to poor TAA implementations).
I admit I don't follow this type of development at all, but I was very surprised that the work is actually being done by Valve, and not AMD. I wonder if they "back port" this into Windows, that'd be... something.
Valve is one of the main contributors to the RADV Vulkan driver for AMD GPUs, and a bunch of other parts of Mesa and the open driver stack in general.
That would require porting Mesa to Windows, which won't happen. At best, someone would be able to extract this to a DLL that could replace the FSR DLL bundled with games.
Oh I mean AMD going "oh that's clever, so I can just do this and change that..." and release a new version of their windows drivers.
That would reduce the value of buying an RDNA4 GPU, so I don't see that happening.
I doubt it. Who's actually buying RDNA4 for FSR4?
FSR is great and all, I just wish developers would stop using it as a crutch, turning it on by default, rather than optimizing their game