It’s progressing on the side of Xbox and AMD. After being announced in June 2021 in version 1.0, the company’s FidelityFX Super Resolution 2.0 is now available for developers.
FSR 2.0 available for Xbox SDKs
It was once again Jason Ronald who relayed the news from AMD. One of the lead designers behind the Xbox Series X and Xbox Series S consoles said he’s excited to continue working with AMD and GPUOpen to deliver the latest graphics performance techniques available on both Xbox and PC.
After a first version last year, it is therefore the FSR 2.0 that developers can use today with Xbox development kits. This means that the implementation is now possible for the next games that will be released.
What exactly is FidelityFX Super Resolution 2.0?
We have already mentioned FidelityFX Super Resolution several times on Xboxygen, but a reminder never hurts! This technology is similar to DLSS developed by NVIDIA. Concretely, it is a question of proposing on the screen an image upscaled in a higher definition (for example in 4K definition) thanks to artificial intelligence.
This makes it possible to use fewer resources on the machine than if the image had to be processed in native 4K definition. And these resources can therefore be used for something else, for example to improve the framerate of the game, namely the number of images displayed per second, and therefore its “fluidity”.
AMD says it designed its FSR 2.0 upscaling technology from the ground up and aims to deliver “image quality similar to or better than native image quality” in the affected game, all while using significantly less resources on the machine side.
Like FSR 1.0, FSR 2.0 has different quality modes that allow customizing the balance between image quality and performance according to preference. To see the performance of FSR 2.0, you can consult the comparative images on the AMD website.
At this time, we don’t know when the first games benefiting from FSR 2.0 will be available on Xbox Series X and Xbox Series S. The PC versions of Deathloop and Forspoken are cited in any case, and count on Xboxygen to follow. all this up close.