AMD FidelityFX™ Super Resolution 3.1 source code now available here on GPUOpen!

Originally posted:July 9, 2024

Last updated:July 9, 2024

Colin Riley

Highlights

TheAMD FidelityFX SDK v1.1 update includes our hotly anticipated v3.1update toAMD FidelityFX Super Resolution 3. As we revealed at GDC 2024,AMD FSR 3.1 provides many significant changes:

Frame Generation is now separate from upscaling
Upscaling quality improvements and new features
AMD FidelityFX API implementation
Vulkan® implementation

We’ve also updated our AMD FSR 3 plugin for Unreal Engine to v3.1, and it also supports UE 5.4:

AMD FSR Frame Generation separate from FSR upscaling

With FSR 3.0 frame generation, we required FSR upscaling be performedearlier in the graphics pipeline. This was because the frame generationalgorithm required processed motion vector and depth data that wasalready created as part of FSR upscaling — and so the resources weresimply used from there as a performance optimization. The downside ofthis was that it locked our frame generation to only work with ourupscaling.

We now have aFrame Generation Prepare function, which takes motionvector and depth scene data pre-upscale, and it generates the requiredinputs required for Frame Generation. This allows Frame Generation tooperate with any upscaler, including third party solutions.

Upscaling changes

FSR 3.1 has improvements which allow for better preservation of detail,and less temporal instability. Additionally, there are new features suchas direct support for letterboxing. We also have improved quality incases where items are excluded from our reactive mask inputs.

AMD FidelityFX API

This release of FSR requires an integration via the FidelityFX API.After discussion with partners, the number of code changes required atthe pipeline level to move from one version of FSR to another was quitehigh, and no upgradable DLL path meant game rebuilds were required. Weare resolving this with the introduction of the AMD FidelityFX API.

The AMD FidelityFX API revolves around a very small set of exported DLLfunctions for the creation, destruction, query, configure, and dispatchof effect operations. Those familiar with Vulkan will note itssimilarity to allow for extensions in the future.

We provide prebuilt, signed versions of official releases to ensurestability and upgradability of DLLs, if allowed by individual gamereleases.

Vulkan support

With FSR 3.1, we provide support for the Vulkan graphics API. The framegeneration swapchain in Vulkan is different to DirectX®12, and requiressome additional data from the game-side application to operate, soplease refer to the sample for specific implementation details.

Frame Generation

AMD FSR 3.1 includes many fixes to frame generation to ensure framespresented to the user are as high quality as possible. This alsoincludes additional changes to frame pacing to assist with smoothing outframe times even more than before.

A reminder that Anti-Lag should be disabled in theAMD Software ->Gaming Graphics settings for the best frame pacing experience.

Recommendations for Frame Generation use

When using AMD FSR 3 and FSR 3.1 frame generation, it is highlyrecommended to be always running at a minimum of ~60 FPS before framegeneration is applied for an optimal high-quality gaming experience, andto mitigate any latency introduced by the technology. Consequently, wesuggest you adjust game graphics settings, resolution, and upscalingquality modes to achieve this, based on the capabilities of the graphicshardware being used and your overall system specs.

If you have an AMD FreeSync™ compatible display, ensure AMD FreeSync isenabled in the AMD Software: Adrenalin Edition™ Application displaysettings.

On AMD Radeon™ RX 7000 Series graphics cards when using the Microsoft®Windows® 11 2022 Update, Hardware-Accelerated GPU Scheduling (HAGS)should be enabled in Windows underSettings -> System -> Display ->Graphics Settings**.**

AMD Radeon Anti-Lag should bedisabled in the AMD Software:Adrenalin Edition Application control panel to avoid any issues withframe pacing smoothness or stuttering. This can be done in the specificgame profile in the driver setting. We are working to fully enableAMD anti-lag technologies with AMD FSR 3 frame generation, which we willprovide more details on in the future.

It is not recommended to use AMD FSR 3 and FSR 3.1 frame generation incombination with AMD Fluid Motion Frames. Frame Pacing smoothness mayalso be impacted by using other driver-based technologies and the use ofthird-party graphics overlays.

AMD FSR 3.1 supported products

AMD FSR 3 and FSR 3.1 are open technologies which do not require machinelearning (ML) hardware, allowing support on a broad range of productsand platforms, including consoles. When using FSR 3 and FSR 3.1 withsuper resolution upscaling and/or frame generation we recommend thefollowing hardware:

Supported and recommended hardware for using AMD FSR 3 with upscaling and Frame Generation

AMD	NVIDIA
Supported: AMD Radeon™ RX 5000 Series and above	Supported: NVIDIA GeForce RTX™ 20 Series and above
Recommended: AMD Radeon™ RX 6000 Series and above	Recommended: NVIDIA GeForce RTX™ 30 Series and above

(Note: we do not suggest using frame generation on products lowerthan our recommendations above. How frame generation performs willdepend on the capabilities of your GPU, and on older hardware you maynot have an optimal experience and may see little to no improvement inperformance.)

Find out more

AMD FidelityFX SDK and AMD FidelityFX API

If you want to know more about our other updates to the AMD FidelityFXSDK, including the release of AMD FidelityFX Brixelizer GI, and our brand-new AMD FidelityFX Breadcrumbs library, the otherblogs associated with this release are below:

Links for Unreal Engine developers for AMD FSR 3.1.

Colin Riley

Colin leads AMD's Game Engineering Core Technology Group. Based out of Edinburgh, Scotland, he is focused on helping game developers get the most out of new rendering technologies on AMD GPUs for PC, Unreal Engine, and other partner ecosystems.