Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

5.5 C
New York

The AMD FidelityFX™ SDK 1.1.3 is now available on GPUOpen

Published:

The AMD FidelityFX™ SDK is our easy-to-integrate solution for developers looking to include AMD FidelityFX technologies into their games without any of the hassle of complicated porting procedures.

We are happy to share that the AMD FidelityFX Software Development Kit (SDK) 1.1.3 is now available for download!

What’s changed?

The AMD FidelityFX SDK 1.1.3 is a patch release that includes a number of fixes for issues discovered with FSR 3.1.1/2. This release also contains all code changes needed to update the Microsoft® Game Development Kit (GDK) version of AMD FSR 3 Frame Interpolation sample for both Xbox and desktop configurations.

  • General cleanup in Frame Interpolation backend.
  • Added letterbox changes to Vulkan®.
  • Removal of Vulkan binding shifts which could cause some compile issues.
  • Fixes for potential incorrect backbuffer sampling in GAME_MOTION_VECTOR_FIELD pass.
  • General framework fixes and updates.
  • Fix typos in the backend.
  • Vram query added to Vulkan.
  • Changes to Vulkan queue selection and behavior.
  • Removal of unused distortion texture channels.
  • Addition of new debug lines to test pacing.
  • Enablement of separate backbuffer and hudless formats.
  • Typeless format support for DX12/GDK.
  • Expose frame pacing tunings such as opt in to use hybrid spinlock.
  • Fix for UpdateTileMappings() deadlock.

Our existing AMD FidelityFX™ technologies

AMD FSR 3.1.3 includes several fixes for issues discovered with FSR 3.1.1/2, and adds new opt-in hybrid spin lock pacing support.

AMD FidelityFX™ technologies in the Microsoft GDK

The Microsoft Game Development Kit (GDK) with Xbox Extensions includes several AMD FidelityFX samples that are optimized specifically for Xbox consoles.

New FSR 3.1.3 Frame Interpolation sample

Updates made to the AMDFidelityFX_FSR3FrameInterpolation GDK sample, bringing native FSR 3.1.3 support to Microsoft’s Xbox and desktop ecosystem sample.

Try it out!

Full source code and binaries are now available on GitHub under MIT license.

The AMD FidelityFX GDK source code and binaries to be made available by Microsoft via the GDK under MIT license.

Don’t forget to check out our extensive AMD FidelityFX SDK documentation.

And of course, make sure you visit our AMD FidelityFX SDK home page or our AMD FSR 3 page here on GPUOpen!

Help contribute to the SDK!

Do you have feature requests or found issues with the SDK? Please get in touch with your AMD representative, or reach out to us with @GPUOpen on Twitter or @GPUOpen@mastodon.gamedev.place.

All requests and feedback are very valuable to us, and we will read and try to respond to everyone.



Source link

Related articles

Recent articles