Today AMD released FidelityFX Super Resolution, their attempt to answer NVIDIA's DLSS and the source code to it is coming soon for developers to look at. Update 24/06/21 - it does actually work on Linux both in native titles (like Dota 2) and Steam Play Proton - even for NVIDIA GPUs.
What exactly is it then? It's AMD's solution for producing high resolution frames from lower resolution inputs. From what AMD say: "it uses a collection of cutting-edge algorithms with a particular emphasis on creating high-quality edges, giving large performance improvements compared to rendering at native resolution directly. FSR enables “practical performance” for costly render operations, such as hardware ray tracing.".
It supports Vulkan and DirectX, although currently it seems it's actually limited to Windows as mentions of Linux have been absent from any press materials and official announcements from AMD. Once it's properly open source, which AMD say will happen "mid July" on GPUOpen, there should hopefully be nothing to stop Mesa developers hooking up support for it to then work for Linux native titles and Windows games run through Steam Play Proton. The latest "official" AMD driver (being the Radeon Software for Linux) had an update only yesterday, June 21, which simply bumped up the supported Linux distribution version.
Direct Link
AMD's version will at least work across both NVIDIA and AMD GPUs, which may make it end up becoming more of a standard compared to DLSS but they face an uphill battle since NVIDIA has a firm foothold with DLSS already.
Article taken from GamingOnLinux.com.
ElectricPrism Jun 22, 2021
Take Note. This is what <3 Linux looks like.
Big props to AMD, proud to be a AMD consumer on all my home & office electronics the last 5 years.
Open Source AMD stuff on Linux is so nice.
I did see a comment that it needs to be applied too early in the pipeline for it to be added as a post-processing shader. The game itself has to add support for it.
TheRiddick Jun 23, 2021
Ironically DLSS is supported in MUCH MORE games atm thanks to mainstream engines adopting them such as UnrealEngine having it baked in. However gamedevs still need to send off textures to NVIDIA for processing, but maybe one day developers will have access to those tools themselves and NVIDIA won't need to be involved (we can only hope).
Still unsure if my next card will be a RDNA3 or NV4000...
Last edited by TheRiddick on 23 June 2021 at 2:33 am UTC
Quoting: TheRiddickHowever gamedevs still need to send off textures to NVIDIA for processing, but maybe one day developers will have access to those tools themselves and NVIDIA won't need to be involved (we can only hope).They don't.
The AI for DLSS 1 needed to be trained on "what this game should look like" to provide its results, and the per-game magic numbers were included along with the per-game optimisations in the fat Windows driver.
The AI for DLSS 2 is trained on "what games look like" and the one set of magic numbers is used for everything.
Devs need to include motion vectors and the previous upscaled frame in their engine to use the DLSS mechanism for the next frame.
Patreon
PayPal
See more from me