Integrate AMD FSR 2 in the Vulkan renderer (currently, FSR 1.0 is supported)

[ArseniyMirniy]

Bugsquad edit: Related to #2809, which is about the FSR 1.0 implementation (which is now in master).

Describe the project you are working on

This feature will help almost any project to improve FPS on low-end systems.

Describe the problem or limitation you are having in your project

There is never too many FPS.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

AMD showcased their new FSR 2.0 that has vector data and previous frames data included into the algorithm, so the quality is way better, than the original FSR 1.x branch. It allows to properly work with thin lines, like ropes or netting fences.

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

AMD Described it better: https://gpuopen.com/fidelityfx-superresolution-2/

[All images ZIP – 155MB]

Scene 1 – Native
Scene 1 – Quality
Scene 1 – Balanced
Scene 1 – Performance
Scene 2 – Native
Scene 2 – Quality
Scene 2 – Balanced
Scene 2 – Performance

If this enhancement will not be used often, can it be worked around with a few lines of script?

Nope, not even close. Unlike FSR 1.0 this feature must be enabled on rendering pipeline, so Vector Data and Previous Frames will be available for the algorithm.

Is there a reason why this should be core and not an add-on in the asset library?

Unlike FSR 1.0 this feature must be enabled on rendering pipeline, so Vector Data and Previous Frames will be available for the algorithm. Only with this data small and thin details can be saved on the output.

[Calinou]

Related to #3401, which is a prerequisite for this proposal to be implemented (as motion vectors are required).

Some notes:

• FSR 2.0 does not have a Vulkan/GLSL version yet – it's currently limited to Direct3D 12/HLSL.
• FSR 2.0 isn't open source yet. Given how fast FSR 1.0 was open sourced after being unveiled, I expect FSR 2.0 to be open sourced in about 3 months from now (June-July 2022).

This feature will help almost any project to improve FPS on low-end systems.

Remember that this is a temporal upscaling algorithm, and these aren't cheap to run on very low-end GPUs (like integrated graphics). FSR 2.0 should work out nicely on mid-range dedicated graphics, but old/low-end dedicated GPUs might struggle with it too (except if targeting 30 FPS).

For mobile, FSR Lite (which is a derivative of FSR 1.0) will likely remain the best approach for the foreseeable future.

[ArseniyMirniy]

Remember that this is a temporal upscaling algorithm, and these aren't cheap to run on very low-end GPUs (like integrated graphics). FSR 2.0 should work out nicely on mid-range dedicated graphics, but old/low-end dedicated GPUs might struggle with it too (except if targeting 30 FPS).

For mobile, #3786 (which is a derivative of FSR 1.0) will likely remain the best approach for the foreseeable future.

For my own projects Mid-range devices are probably even more important area, and also, if internal solution with TAA is possible outside of FSR, it's fine to have it. If FSR 2.0 will have Vulkan version, it's also fine to see, which one is better. Totally up to you, guys.

[yhyu13]

@Calinou

FSR 2.0 does not have a Vulkan/GLSL version yet – it's currently limited to Direct3D 12/HLSL.

Do you mean the shader code or does FSR 2.0 relies on DX specific APIs?

[Calinou]

Do you mean the shader code or does FSR 2.0 relies on DX specific APIs?

It's a mixture of both right now. I'm fairly sure Vulkan equivalents do exist for anything FSR 2.0 does, but AMD still needs to do the porting work 🙂

[Calinou]

FSR 2.0 is out in Deathloop (but its code hasn't landed on GPUOpen yet). Here's a comparison against native rendering and DLSS: https://www.techpowerup.com/review/amd-fidelity-fx-fsr-20/

FSR 2.0 seems to compare favorably to DLSS, and it can also be paired with dynamic resolution scaling.

For reference, TAA support in Godot (which is a prerequisite for FSR 2.0 due to the motion vectors) is still being developed as we speak.

[Zireael07]

motion vectors

Does that mean we're finally getting built-in motion blur in Godot?

[ArseniyMirniy]

Does that mean we're finally getting built-in motion blur in Godot?

Yes, it would be great to have the ability to build a proper motion blur (currently, you can make camera-based one)

[ArseniyMirniy]

In addition, it seems, that FSR 2.0 is not just good, but "Better than native" even at 4K resolution, it nearly eliminates common AA artifacts, like shimmery lines:

https://www.youtube.com/watch?v=s25cnyTMHHM