Tuesday, June 22nd 2021

AMD Radeon Software Adrenalin 21.6.1 Released with FidelityFX Super Resolution

by
btarunr
 Discuss (36 Comments)
AMD today released the latest version of its Radeon Software Adrenalin drivers. Version 21.6.1 beta introduce support for the upcoming FidelityFX Super Resolution (FSR) feature, AMD's answer to the NVIDIA DLSS. We also postedour in-depth review of FSR today. The driver release notes don't mention which exact titles support it at launch, so we'll probably have to wait until a formal launch of the feature. In addition, the drivers also introduce support for the Radeon RX 6800M mobile graphics, and optimization for "Dungeons & Dragons: Dark Alliance."

Among the bugs fixed with this release are one which causes FreeSync to lock up during task-switching, an application crash with "Anno 1800" in DirectX 12 mode; AMD Cleanup Utility accidentally mopping up non-graphics AMD drivers (such as chipset, storage, etc.); lower than expected performance with "Destiny 2" on some products; and enabling raytracing in "Ring of Elysium" causing an application crash. Grab the drivers from the link below.

DOWNLOAD: AMD Radeon Software Adrenalin 21.6.1 beta
READ: Our review of AMD FidelityFX Super Resolution
Support For
  • AMD Radeon RX 6800M Graphics
  • Dungeons & Dragons: Dark Alliance
  • AMD FidelityFX Super Resolution (FSR) support for select titles.
Fixed Issues
  • Radeon FreeSync may intermittently become locked while on desktop after performing task switching between extended and primary displays upon closing a game, causing poor performance or stuttering.
  • Anno 1800 may crash upon launching this game when running DirectX 12.
  • AMD cleanup utility may clean up chipset/RAID installer related folders/registries from the system.
  • Some Radeon Graphics products may experience lower than expected performance in Destiny 2 when compared to previous Radeon Software versions.
  • Upon joining the AMD User Experience Program, the AMD User Experience Program Master service may have higher than expected CPU utilization.
  • Enabling raytracing while running Ring of Elysium on DirectX 12 may cause this game to crash.
Known Issues
  • Resident Evil Village may experience an intermittent application hang or TDR on AMD Radeon VII graphics products in the first mission of the game.
  • Enhanced Sync may cause a black screen to occur when enabled on some games and system configurations. Any users who may be experiencing issues with Enhanced Sync enabled should disable it as a temporary workaround.
  • Connecting two displays with large differences in resolution/refresh rates may cause flickering on Radeon RX Vega series graphics products.
  • An Oculus service error may be received on Radeon RX 5000 & 6000 series graphics products which prevents the Oculus Link setup software from running.
  • Radeon performance metrics and logging features may intermittently report extremely high and incorrect memory clock values.
  • If Ryzen Master is not detected in Adrenalin software after installation, a system restart may be required.
  • If Blue or Black screen is observed in mobile systems, temporarily disable Enhanced sign-in
  • A driver mismatch error may appear when two versions of Radeon software (Windows Store & AMD Support versions) are installed on your system. As a temporary workaround, launch the Windows Store version of Radeon software.
  • AMD is investigating an issue that may cause a small impact to battery life on AMD Ryzen 5000 notebooks.
  • A Blue or Black screen may be observed after updating to the latest Radeon Software. A workaround is to disable core isolation.
  • AMD is investigating a D3 error code that may be seen in some motherboard after updating to the latest Radeon Software.
  • Lower than expected performance may be observed on select AMD Athlon mobile systems.

Related News

Add your own comment

36 Comments on AMD Radeon Software Adrenalin 21.6.1 Released with FidelityFX Super Resolution

#26
zlobby
INSTG8Rprobably
Not trying to pick a fight here but I'm willing to bet you haven't studied properly probaility theory. :D
Posted on Reply
#27
Sihastru
Just upgraded to this version and every time my computer starts/restarts I get this:



Good job AMD! /s

What a POS. Even the driver UI keeps crashing once in a while when I click on different tabs. The only way to fix it was to revert to 21.5.2.
Posted on Reply
#28
evernessince
birdieEither I do not understand anything at all or AMD doesn't care about FSR that much.

When DLSS was released we had a dozen of reviews right from the get go.

AMD FSR? Not a single review. I've found a 1080p lone video on youtube where you can barely see anything and that's it.

GCN 1-2-3 have been moved to Legacy. Wow.
Or it could be that it's 4:37 AM when you posted that comment. Given that the feature has officially been launched now with games, this comment looks incredibly foolish.
Posted on Reply
#29
milewski1015
SihastruJust upgraded to this version and every time my computer starts/restarts I get this:



Good job AMD! /s

What a POS. Even the driver UI keeps crashing once in a while when I click on different tabs. The only way to fix it was to revert to 21.5.2.
It IS listed as a beta driver…
Posted on Reply
#30
Caring1
"A driver mismatch error may appear when two versions of Radeon software (Windows Store & AMD Support versions) are installed on your system. As a temporary workaround, launch the Windows Store version of Radeon software."

Is AMD saying the Windows store version is somehow better than their direct download of the same drivers? :eek:
Posted on Reply
#31
GamerGuy
I'd installed Adrenalin 21.6.1 for my main rig without issue, I ran AMDCleanuputility in 'Safe Mode' first before restarting and installing the driver. Something odd though, I think AMDCleanuputility inadvertently removes USB driver or at the very least, does something to it as I find my USB devices being reinstalled even as I was installing the Adrenalin driver. Still, everything seemed to work (I'd even just before the installation completed downloading Godfall) but it was kinda late here, about 2 am, I'd decided to hit the sack.
Posted on Reply
#32
turbogear
I installed it as well and did some benchmarks on Time Spy:
www.techpowerup.com/forums/threads/the-rx-6000-series-owners-club.276164/post-4546490

I found a minor bug though in this driver. :D
I use Wattman profiles to switch between OC profiles on the fly.

I was not able to load the profiles saved with previous driver version.:wtf:
Then I tried to create new profile and that also gave same error saying: Unable to load settings; the requested Radeon Wattmann Settings configuration file is not compatible for your current graphics device.:roll:

Afterwards I found the reason. The new driver does not like % symbol in the file name. :laugh:

Never had this issue on any of the previous drivers since owning different RDNA2 cards.
For example this does not work anymore:
2750MHz_1175mV_15%_power_limit.xml

But this works::p
2750MHz_1175mV_15_power_limit.xml

I have been using such names since December on different driver versions.
I wanted to report it here in case somebody else has same issue and wondering what is going on.

@INSTG8R
As you are part of Vanguard program maybe you can try it.
I find the error message quite odd. :p
Maybe something like invalid file would be better than saying these settings are not compatible for your current graphics device.


Here is the screenshot regarding the error message that I get:
Posted on Reply
#33
INSTG8R
Vanguard Beta Tester
zlobbyNot trying to pick a fight here but I'm willing to bet you haven't studied properly probaility theory. :D
Try to stick to your original fallacy instead of moving the goal posts because your wrong…
turbogearI installed it as well and did some benchmarks on Time Spy:
www.techpowerup.com/forums/threads/the-rx-6000-series-owners-club.276164/post-4546490

I found a minor bug though in this driver. :D
I use Wattman profiles to switch between OC profiles on the fly.

I was not able to load the profiles saved with previous driver version.:wtf:
Then I tried to create new profile and that also gave same error saying: Unable to load settings; the requested Radeon Wattmann Settings configuration file is not compatible for your current graphics device.:roll:

Afterwards I found the reason. The new driver does not like % symbol in the file name. :laugh:

Never had this issue on any of the previous drivers since owning different RDNA2 cards.
For example this does not work anymore:
2750MHz_1175mV_15%_power_limit.xml

But this works::p
2750MHz_1175mV_15_power_limit.xml

I have been using such names since December on different driver versions.
I wanted to report it here in case somebody else has same issue and wondering what is going on.

@INSTG8R
As you are part of Vanguard program maybe you can try it.
I find the error message quite odd. :p
Maybe something like invalid file would be better than saying these settings are not compatible for your current graphics device.


Here is the screenshot regarding the error message that I get:
I’ haven’t tried the new public’s but this isn’t the first time changes have been made that render previous profiles invalid. I’m fighting to get that horrible new Wattman profile file explorer fixed
GamerGuyI'd installed Adrenalin 21.6.1 for my main rig without issue, I ran AMDCleanuputility in 'Safe Mode' first before restarting and installing the driver. Something odd though, I think AMDCleanuputility inadvertently removes USB driver or at the very least, does something to it as I find my USB devices being reinstalled even as I was installing the Adrenalin driver. Still, everything seemed to work (I'd even just before the installation completed downloading Godfall) but it was kinda late here, about 2 am, I'd decided to hit the sack.
That was what the known issue was….why did you use it despite the warning ,,,,As I posted way back was you don’t need to use it for any reason. Factory Reset install cleans out all driver traces as well as DDU would.

Sorry @zlobby apparently some people can’t read release notes and end up like Gamer Guy…found the 1%
Posted on Reply
#34
turbogear
INSTG8RI’ haven’t tried the new public’s but this isn’t the first time changes have been made that render previous profiles invalid. I’m fighting to get that horrible new Wattman profile file explorer fixed
It is not the profiles themselves. They are working but just need to rename them. :laugh:
The new driver does not like % symbol in file name.
All old drivers had no problem with that but new driver gives you strange error message about profile not supported if file name has % symbol in it as I explained in the previous post.
Posted on Reply
#36
INSTG8R
Vanguard Beta Tester
turbogearIt is not the profiles themselves. They are working but just need to rename them. :laugh:
The new driver does not like % symbol in file name.
All old drivers had no problem with that but new driver gives you strange error message about profile not supported if file name has % symbol in it as I explained in the previous post.
Yes the new file explorer in wattman is terrible I’ve already raised a stink over it
Posted on Reply
Add your own comment
Nov 24th, 2024 12:13 EST change timezone

Latest GPU Drivers

New Forum Posts

Popular Reviews

Controversial News Posts