Catalyst 20.2.1

[pax]

https://www.amd.com/en/support/kb/re...mail&utm_term=

Support For
Zombie Army 4: Dead War™

Fixed Issues
Some users may experience higher than expected memory usage when recording with Radeon ReLive.

HDR content may become overly dark or overly bright in some DirectX®12 API games on Radeon RX 5000 series graphics products.

The camera element may exhibit stutter in recorded clips or during streaming using Radeon ReLive.

The scroll bar is missing for some users in the Compatibility tab of Radeon Software.

Radeon Software may fail to detect VR games when SteamVR is running or has been started.

Radeon Anti-Lag enable and disable beep notifications may be played in error when individually pressing keys assigned to the hotkey.
The Snap Settings feature may fail to apply settings for Auto Tuning controls if other Auto Tuning settings were already applied.

Couple decent fixes in this one...

[Seyiji]

Support For:

• Zombie Army 4: Dead War

Fixed Issues:

• Some users may experience higher than expected memory usage when recording with Radeon ReLive.
• HDR content may become overly dark or overly bright in some DirectX®12 API games on Radeon RX 5000 series graphics products.
• The camera element may exhibit stutter in recorded clips or during streaming using Radeon ReLive.
• The scroll bar is missing for some users in the Compatibility tab of Radeon Software.
• Radeon Software may fail to detect VR games when SteamVR is running or has been started.
• Radeon Anti-Lag enable and disable beep notifications may be played in error when individually pressing keys assigned to the hotkey.
• The Snap Settings feature may fail to apply settings for Auto Tuning controls if other Auto Tuning settings were already applied.

Known Issues:

• Some DirectX®11 API games may experience an application crash when performing a task switch with Radeon Image Sharpening enabled.
• Enabling feature for Radeon ReLive such as Instant Replay, Instant Gif or In-Game Replay may cause the display or UI to flicker or stutter.
• A loss of display with working audio may be experienced on a limited number of displays when performing a mode change on Radeon RX 5000 series graphics products.
• A system crash or hang may occur when running the Final Fantasy XIV: Shadowbringers™ benchmark.
• Integer Scaling may cause some video content to show flicker when the display resolution is set to less than native resolution.
• The Radeon Software Overlay hotkey notification may sometimes be displayed during video playback in web browsers or launching some video player applications.
• Radeon Software may open with an inconsistent size or may not keep its previously set size when opened.
• Modifying the HDMI Scaling slider may cause FPS to become locked to 30.
• Some Radeon RX 5700 series graphics users may intermittently experience a black screen while gaming or on desktop. A potential temporary workaround is disabling hardware acceleration in applications running in the background such as web browsers or Discord.
• Some games may exhibit stutter or appear to be downclocking on Radeon RX 5000 series graphics products.
• A black screen may occur when performing a mode change with a limited number of displays on Radeon RX 5700 series graphics products.

Data farming fix or no?

[eNforcer]

Originally Posted by Seyiji

Data farming fix or no?

Go vote here, it might be a step towards that.

Also, it's pretty apparent that the people don't want any bloat

[Seyiji]

Originally Posted by eNforcer

Go vote here, it might be a step towards that.

Also, it's pretty apparent that the people don't want any bloat

Thanks gai didn't know there was a new one of these floating about.

[Kombatant]

Originally Posted by Seyiji

Data farming fix or no?

You should really call it Seyiji's fix - this is super hard to reproduce. Have you seen any other mentions of this?

[Seyiji]

No dice on others and lawdy have I been looking and tearing my hair out.

On a whim I installed 20.1.4 over 19.11.3 and whatever you guys did with that driver seems to have fixed it. I'm scared to install this 20.2.1 driver though !_!

I don't know what triggered this between between 19.12.2 and 20.1.3 but hopefully it doesn't come back in the future because I was about hit the AMD gpu eject button and abandon ship.

[Kombatant]

Originally Posted by Seyiji

No dice on others and lawdy have I been looking and tearing my hair out.

On a whim I installed 20.1.4 over 19.11.3 and whatever you guys did with that driver seems to have fixed it. I'm scared to install this 20.2.1 driver though !_!

I don't know what triggered this between between 19.12.2 and 20.1.3 but hopefully it doesn't come back in the future because I was about hit the AMD gpu eject button and abandon ship.

Trust me, if this was a widespread issue, Reddit would blow up

There's something on your PC that causes this. That's what makes these weird bugs so difficult to reproduce.

[pax]

IMO this might be one of those times where some MS or other software that interferes with radeon drivers is cross talking the telemetry that windows of those programs do. Its known that some office software will create bugs in some radeon drivers.

Or you have some trojan coin thing or malware going on thats creating the traffic.

[Seyiji]

Originally Posted by pax

IMO this might be one of those times where some MS or other software that interferes with radeon drivers is cross talking the telemetry that windows of those programs do. Its known that some office software will create bugs in some radeon drivers.

Or you have some trojan coin thing or malware going on thats creating the traffic.

Could be except I had ddu set it so ms wouldn't download drivers.

Also could be except I checked and nussing as far as malware. Also wouldn't explain why every time i went back to 19.11.3 all data farming stopped.

So Kombatant was the ip address i posted one of amd's destinations for telemetry you didnt say anything aboot that being one of your guys doings or not. That should clear things up on who it went to exactly.

[Kombatant]

Originally Posted by Seyiji

Could be except I had ddu set it so ms wouldn't download drivers.

Well, here's the thing, and it might surprise you. DDU is not gospel. It has bugs (otherwise they'd never update it). Especially whenever AMD releases a new major version of its driver, and until DDU properly updates its software to recognise all the changed/added files, you got countless cases where ppl brick their Windows systems because DDU aggressively deletes stuff it's not supposed to. And of course AMD gets blamed because nobody thinks to blame DDU.

Also could be except I checked and nussing as far as malware. Also wouldn't explain why every time i went back to 19.11.3 all data farming stopped.
So Kombatant was the ip address i posted one of amd's destinations for telemetry you didnt say anything aboot that being one of your guys doings or not. That should clear things up on who it went to exactly.

Well a quick IP check shows this:


As far as I am aware, AMD uses Amazon's infrastructure - so this IP looks a little bit irrelevant. Plus, when you say that you blocked the file that's doing the traffic, and somehow you still have traffic? Something else is wrong there.

[Seyiji]

Originally Posted by Kombatant

Well, here's the thing, and it might surprise you. DDU is not gospel. It has bugs (otherwise they'd never update it). Especially whenever AMD releases a new major version of its driver, and until DDU properly updates its software to recognise all the changed/added files, you got countless cases where ppl brick their Windows systems because DDU aggressively deletes stuff it's not supposed to. And of course AMD gets blamed because nobody thinks to blame DDU.
Well a quick IP check shows this:
[IMG]https://i.imgur.com/VpKEBtz.jpg[/IMgG]

As far as I am aware, AMD uses Amazon's infrastructure - so this IP looks a little bit irrelevant. Plus, when you say that you blocked the file that's doing the traffic, and somehow you still have traffic? Something else is wrong there.

DDU was only used as a last resort and was fully updated at the time i used it not that that means anything as you said. An no surprises here I don't trust ddu with a 10 foot pole even updated it was only 1 tool in a list to try and figure things out.

I used AMD factory reset/clean install more times during diagnosis.

As for the ip that's what microsofts resource manager gave me as the ip at the time. I'm not too well versed in the art of tracking ip's other wise.

Any way it seems to be sorted now and hopefully stays that way in the future.

[Android1]

Originally Posted by Kombatant

As far as I am aware, AMD uses Amazon's infrastructure - so this IP looks a little bit irrelevant. Plus, when you say that you blocked the file that's doing the traffic, and somehow you still have traffic? Something else is wrong there.

Could you double-check that? It very well could have changed, but I remember distinctly that AMD used to use Akamai for content delivery.

[Kombatant]

Originally Posted by Android1

Could you double-check that? It very well could have changed, but I remember distinctly that AMD used to use Akamai for content delivery.

The AMD User Experience program uses Amazon.

[pax]

So is it possible that some radeon drivers re picking up telemetry or data traffic that is being created by something else?

[Android1]

Originally Posted by Kombatant

The AMD User Experience program uses Amazon.

Gotcha.

[DarkFoss]

The 20.2.2 driver dropped yesterday. Release notes