• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The AMD Driver Thread

What should we be looking at here?

Shared the settings that I think are the best.

-Texture Filtering Quality should be set to High for maximum image quality;
-Anisotropic Filtering to Enabled with 16x preset.
-Anti-Aliasing Method to Adaptive multisampling;
-Radeon Image Sharpening to Enabled and 100% in Windows with Microsoft Edge as the running browser, and up to the user in the games.

What's the difference between Radeon Chill and Frame rate target control?
 
Shared the settings that I think are the best.

-Texture Filtering Quality should be set to High for maximum image quality;
-Anisotropic Filtering to Enabled with 16x preset.
-Anti-Aliasing Method to Adaptive multisampling;
-Radeon Image Sharpening to Enabled and 100% in Windows with Microsoft Edge as the running browser, and up to the user in the games.

What's the difference between Radeon Chill and Frame rate target control?

I checked these settings in the control panel the ? says that these only effect Direct X 9 titles?
 
Anyone ever had a response back from sending an issue report via the drivers?

Getting fed up with driver crashes and BSODs that seem to be down to poor multi monitor support that's been going on for months now (a year+ maybe?). :(

Win10, Vega 64.
 
the new drivers increased my warzone fps by 10

but... I have been getting some weird disconects from the monitor when going to sleep in windows
 
Anyone else having issues installing 21.3.1?

It seems to install ok, but when it gets to the second part where the screen flickers off, it doesnt come back on. Have booted into Safe mode, wiped with DDU and reinstalled 21.2.3.

I've tried various times, but it seems consistent where it fails.
 
Chaps, having an annoying problem with the new card (6900 XT) and my monitor...

About half the times after the monitor wakes up from power saving mode, the resolution drops to 1280x800 (and it won't let me go higher in Windows). I need to turn the monitor off and back on again for it to get back to 3440x1440. This didn't happen with my old Vega 64, so I assume it's a 6x00 series "bug". Monitor is an LG 34GK950F-B.

Any ideas what setting(s) I might need to tinker with? In either Windows or Radeon control panel?

Things I have tried:
  • Tried HDMI rather than DP - this solves it, but I am capped at 85Hz, which is not cool :(
  • No adapters, DP cable going straight to monitor (same cable that I was using with Vega 64)
  • I just tried another "Basics" cable from a major online retailer, and it doesn't even work! Could be a faulty cable, but I get no display at all on DP.
  • The only thing I have enabled in Radeon software > Display is that Freesync is enabled (though I think this was automatic)
  • Windows scaling is set to 100%
  • Windows is up to date (version 20H2)
  • Updated to the latest 21.3.1 driver
Any other ideas please?! Such a weird bug!

Cheers,

Su
 
...About half the times after the monitor wakes up from power saving mode, the resolution drops to 1280x800...
I've had a similar problem many times before. I'm pretty sure it's a timing issue where certain combinations of monitor+GPU wake up slow enough that Windows gives up and assigns the default driver to the monitor, limiting its resolution to something archaic. It seems to only happen with DP, so it's possibly related to the stupid DP autodetection that causes so many multimonitor problems.

I can't offer a real solution, but cycling through the monitor's inputs may fix it quicker than turning it off and on again.
 
Anyone else having issues installing 21.3.1?

It seems to install ok, but when it gets to the second part where the screen flickers off, it doesnt come back on. Have booted into Safe mode, wiped with DDU and reinstalled 21.2.3.

I've tried various times, but it seems consistent where it fails.
do you have a vega gpu and rift installed by any chance, this used to happen to me, didnt happen after the upgrade to 6800, but ive read it may be related to the rift being plugged in.
 
do you have a vega gpu and rift installed by any chance, this used to happen to me, didnt happen after the upgrade to 6800, but ive read it may be related to the rift being plugged in.

I've got a Gigabyte 5700XT with a single AOC monitor - might try updating the monitor drivers and try again, purely because its the only thing I've not tried yet.

Currently running 21.2.3 absolutely fine, so will try again when the next one comes out - might just be an anomaly.
 
I've got a Gigabyte 5700XT with a single AOC monitor - might try updating the monitor drivers and try again, purely because its the only thing I've not tried yet.

Currently running 21.2.3 absolutely fine, so will try again when the next one comes out - might just be an anomaly.
hopefully not the same thing, as it was bloody annoying and happens for a good 4 or so months at least. fingers crossed its a 1 time thing for you.
 
I've had a similar problem many times before. I'm pretty sure it's a timing issue where certain combinations of monitor+GPU wake up slow enough that Windows gives up and assigns the default driver to the monitor, limiting its resolution to something archaic. It seems to only happen with DP, so it's possibly related to the stupid DP autodetection that causes so many multimonitor problems.

I can't offer a real solution, but cycling through the monitor's inputs may fix it quicker than turning it off and on again.

Oh dang that sounds like a super annoying bug :( don't suppose there's a way to edit the Windows timeout value? Or stagger the power up so that the GPU waits for a while until the monitor catches up first?

Cheers,

Su
 
Back
Top Bottom