AMD Radeon Software Adrenalin 21.6.1 Released with FidelityFX Super Resolution

[INSTG8R]

There is a 99% chance Earth won't be hit by an effin huge space rock but this chance didn't play out quite nicely for the dinosaurs.

Your gonna die on this hill for a program you’ve probably never even used yourself…I’m an AMD beta tester and I’ve maybe used once in its entire existence that 99% of the AMD user base wouldn’t even know it existed if the notes hadn’t posted the in the notes…

 

[zlobby]

probably

Not trying to pick a fight here but I'm willing to bet you haven't studied properly probaility theory.

 

[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.

 

[evernessince]

Either 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.

 

[milewski1015]

Just upgraded to this version and every time my computer starts/restarts I get this:

View attachment 204980

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…

 

[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?

 

[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.

 

[turbogear]

I installed it as well and did some benchmarks on Time Spy:

The RX 6000 series Owners' Club

@ratirt you have GodFall. Maybe I will also pick it if you think it is fun game. I really like this game so damn much and it looks outstanding. I really wanna see the FSR on this one just to see how good it is. As for the game itself it is really entertaining. I sometimes just launch any stage...

www.techpowerup.com

I found a minor bug though in this driver.
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.
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.

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

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:
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.
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:

 

[INSTG8R]

Not trying to pick a fight here but I'm willing to bet you haven't studied properly probaility theory.

Try to stick to your original fallacy instead of moving the goal posts because your wrong…

I installed it as well and did some benchmarks on Time Spy:

The RX 6000 series Owners' Club

@ratirt you have GodFall. Maybe I will also pick it if you think it is fun game. I really like this game so damn much and it looks outstanding. I really wanna see the FSR on this one just to see how good it is. As for the game itself it is really entertaining. I sometimes just launch any stage...

www.techpowerup.com

I found a minor bug though in this driver.
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.
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.

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

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:
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.
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:
View attachment 205123

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

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.

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%

 

[turbogear]

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

It is not the profiles themselves. They are working but just need to rename them.
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.

 

[erpguy53]

this 21.6.1 driver version killed support for Win7 & Win8.1 along with pre-polaris gpus as pointed out in this Neowin article:

AMD 21.6.1 driver drops support for Windows 7/8/8.1 and pre-Polaris GPUs

AMD releases today the 21.6.1 driver which adds support for FidelityFX Super Resolution (FSR) upscaling technique. Sadly, the driver also ends support for pre-Windows 10 OSes and pre-Polaris GPUs.

www.neowin.net

 

[INSTG8R]

It is not the profiles themselves. They are working but just need to rename them.
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