Sigh still has Core OCing issues on Radeon VII....part of me thinks they did this on purpose to make the 5700XT more attractive >.>

75Hz bug is still present for RX 5700, just tested (random flickering lines on top of the screen) State of Decay 2 in Windowed Fullscreen stops at 37-38fps when having 75Hz set. Already reported this a while back with others people, yet it's still not under Known Issues, why AMD?

Is the setting for switching to RGB 4,4,4 FULL back?

ClockClocker:

Is the setting for switching to RGB 4,4,4 FULL back?

Since this has been fixed in previous driver, why would AMD break it again?

Crossfire profiles disappeared from the atiapfxx.blb file a few drivers ago but the power profiles can still show some details. These were added as of 19.8.2 HighPerfGPUAffinity HighPerfGPUAffinity HighPerfGPUAffinity HighPerfGPUAffinity HighPerfGPUAffinity HighPerfGPUAffinity HighPerfGPUAffinity HighPerfGPUAffinity HighPerfGPUAffinity HighPerfGPUAffinity HighPerfGPUAffinity HighPerfGPUAffinity HighPerfGPUAffinity HighPerfGPUAffinity HighPerfGPUAffinity So... Assassin's Creed Origins Assassin's Creed Odyssey Uplay Plus version (New exe, likely a new UPlay client ID too.) and the separate Tour/Discovery mode and the Uplay plus version of these. (The Uplay client premium subscription service Ubisoft is doing kinda like EA's program on Origin.) Borderlands 3 Oak Game (Something 64-bit UE4 from what it's looking like unless Borderlands is now using tree code names and it's that.) Control DX11 and DX12 (DX11 mentioned in the release notes though so nothing surprising here.) Man of Medan

little offtopic ... AC Origins ... hoped it will run better than on RX5700 than with my previous RX580, but nope, still can't hold 60 fps

Anyone else getting black screen issues with this and Chrome? i.e. The full window of Chrome is black and nothing can be seen if GPU acceleration is enabled. This is on 2 PC's one with an RX480 and the other with an RX580 Current work around I have is to launch with -disable-gpu at the end of the shortcut and then disable hardware acceleration.

"Radeon Overlay may intermittently fail to appear when toggled in game" Still not fixed thanks AMD

ClockClocker:

Is the setting for switching to RGB 4,4,4 FULL back?

It should be.

This driver fixed all my problems with 5700xt and BFV. No more stuttering, 120-140 on high-ultra settings.I use to get 80-130 on previous driver. The card runs more stable clocks. Also freesynch was not working previously as the screen would dim it self when launching the game. Now is fixed. Very good driver so far.

warlord:

Does your CPU provide enough horsepower to be surely away from DX11 overhead or bottlenecks? Assassin's Creed franchise, all versions, all games, benefit Nvidia mostly by a large margin like the way those games meant to be played. You can't expect much here. It is Ubi's racism, not AMD's problem.

The CPU usage is mostly around 35-55%. If I disable SMT, it's close to 75-85% but with little better fps. I read few times fps on AMD cards also struggling in AC Origins/Odyssey due to missing DX11 Multithreading. I'm not gonna buy NVIDIA card though, just because of that ;-)

d_mouse:

Anyone else getting black screen issues with this and Chrome? i.e. The full window of Chrome is black and nothing can be seen if GPU acceleration is enabled. This is on 2 PC's one with an RX480 and the other with an RX580 The current workaround I have is to launch with -disable-GPU at the end of the shortcut and then disable hardware acceleration.

I'm not using Chrome, but if I keep HW acceleration enabled in Firefox I get random BSOD. I thought these issues or similar ones are only affecting AMD Navi owners?

Guess I need to clean with DDU, as now I get plenty of videos not displaying at all with potplayer and in software mode it is mostly black.

spajdrik:

The CPU usage is mostly around 35-55%. If I disable SMT, it's close to 75-85% but with little better fps. I read few times fps on AMD cards also struggling in AC Origins/Odyssey due to missing DX11 Multithreading. I'm not gonna buy NVIDIA card though, just because of that ;-)

Origins and Odyssey are these two oddities at the moment, AMD compared to NVIDIA had a pretty noticeable performance difference upwards of 40% in the worst spots but the CPU and GPU behavior also differs a bit since the games threading seems to come from NVIDIA's method of using NVAPI and deferred render contexts so it spawns an additional 8 threads for this purpose. (And always 8 thus octa core being the recommended though a hexa is good too outside of some major bottleneck areas like the main cities in each game.) So on NVIDIA GPU systems CPU usage from this and the D3D11.1 driver command list function you get a near 100% CPU load on the primary core and pretty high load on the other six to eight cores though a bit below what CPU0 is doing and besides Athens of Odyssey and Alexandria of Origins it's manageable although stuttering starts becoming more pronounced on a quad core system even if it's a higher clocked model or even a overclocked one. For AMD the newer GPU's also handle some of the issues such as tessellation and geometry performance better although culling and discarding unused data I think is still not quite on par and these games would likely have benefited from D3D12 even if it's mainly to get the CPU command list functionality going where it's a standard and not a optional part plus other improvements over D3D11 even if 11.1 and on has a few additions too but not quite the same as with D3D12 itself. 🙂 So yeah not the best at explaining and it's a complex odd little issue but older AMD GPU's kinda run into issues with this game and even without the additional threading the game is still pushing CPU pretty hard but AMD systems tend to hover around the 70% utilization other than again the big cities with a ton of geometry details, NPC and other stuff to calculate and work with for CPU, GPU, RAM and HDD though DirectX 11 might be hampering things a bit as well for these games. 😀 Radeon VII shows some improvements over Vega though being less bottlenecked and just faster (Brute force it all!) and then Navi and it's RDNA improvements for shader performance and the way that it does Wave32 instead of a Wave64 where it requires less threading and getting full effect also makes it excel in these games where it holds up pace with the VII despite having less cores total so it's a interesting game but I am curious how much D3D11 is holding total performance back but it's speculative until Ubisoft implements either DirectX 12 or Vulkan for the current version of Anvil Engine on PC maybe for the third game coming in 2021 or so but we'll see and even if that happens it might be pushing even greater visual fidelity (Playstation 5 and the next XBox coming out too.) so a direct comparison might not be doable and who knows what else they might be implementing. I find them good test cases for D3D11 and potential bottlenecks although not perfect and also a indication of future titles going more mainstream with almost requiring a hexa or even octa core minimum. (Performance wise though this system is held back by RAM and HDD among other bits but I hope to be able to improve that next year sometime depending on how things go.) Also nice to hear confirmation on more fixes for the 5700(XT) / Navi10 though yeah a few of the remaining issues are still there once again but I suppose AMD has been focused on fixing up Navi and settling a few of the other reported issues and current snags like the pixel format option somehow disappearing for a lot of users.

For a lot of previous driver version (this included), I have a Flickering video in youtube with Microsoft Windows Egde in fullscreen mode (1440p and 144Hz monitor). Chrome and Firefox no problems, but this two dont have HDR Youtube support.

Looks like BSOD in WoW classic, Apex Legends is a bit more variable, hardware acceleration in browsers is better but still not fixed (Difference in format used and things like 60FPS perhaps?) and undervolting doesn't seem to be doing much in Wattman for earlier GPU models anymore which I need to check. So for the 5700 / 5700 XT there's BSOD issues in a few games and hardware browser acceleration particularly for video playback can lead to a BSOD but seems to be less frequent than 19.8.1, Apex Lengends can crash to black screen and force a complete system shut down and start up to get back from that and WoW classic BSOD's with some AMD .sys error. Vega reports indicate that for a number of users Wattman doesn't apply undervolt and a few also report that the fan curve settings doesn't do anything (It works here but I need to check the voltage value.) and then the Radeon VII well there's the elevated clock speeds and some reports about stability but nothing specific from what I've found so far. Polaris seems to be having similar issues as before but some users are also running on a older version of Windows 10 or without the cumulative for fixing the screen color corruption problem. Still have more to read though, usual bias also applies with reports being far more frequent when something does happen compared to everything working so a quick glance could make it seem like the drivers since 19.5.1 are totally busted although there are a few titles and situations that seem to be 100% repeatable and should be easy for AMD to test and unless it needs software updates for the affected games or programs fixing these should then be possible in a later driver release. 🙂 https://www.reddit.com/r/Amd/comments/cvry5c/radeon_software_adrenalin_2019_edition_1982/

Thanks for the all the info @JonasBeckman you are very helpful guy. Gonna be trying these tonight and see how it goes with the polaris. I didnt had any of the mentioned issues with previous whql driver.

d_mouse:

Anyone else getting black screen issues with this and Chrome? i.e. The full window of Chrome is black and nothing can be seen if GPU acceleration is enabled. This is on 2 PC's one with an RX480 and the other with an RX580 Current work around I have is to launch with -disable-gpu at the end of the shortcut and then disable hardware acceleration.

I had the same problem on R9 290(probably not related to specific hardware). I found solution for this is to remove the catalog C:\Users\your_username\AppData\Local\Google\Chrome\User Data\ShaderCache The catalog will rebuild itself after starting chrome.

Undying:

Thanks for the all the info @JonasBeckman you are very helpful guy. Gonna be trying these tonight and see how it goes with the polaris. I didnt had any of the mentioned issues with previous whql driver.

Yeah it's been smooth so far for 19.x with this Vega GPU though Wattman has changed a bit and the fan curvature could be less stair-steps and more curves but well it's overall a fairly minor issue and mostly concerns being more careful when building a custom fan "curve" (stepping really.) doubt it's going to be changed now that Overdrive 8 landed with the VII and Navi taking it further where it's all curvy and can scale in a way that prior GPU's just don't have the hardware for but I do need to verify what the voltage is actually doing because if that's on stock it would confirm that it's at least partially broken on Vega and a slight increase in temperature and less GPU clock speed though it shouldn't impact performance too badly. (Worse for the VII though but it's suffering from other issues as well wonder if it kinda got a bit squeezed between old Vega and new Navi as something that just isn't quite either thus it hits a few additional issues.) No crashes other than self induced ones during testing or game specific issues and no particular OS problems either so far although the known issues do make it clear AMD has some work still and the earlier GPU models also hit a few snags that would need to be resolved up until support ends which would start with GCN 1.0 so Polaris should be good for a number of years more if drivers don't make a mess of things on the software side which I hope can be fixed once these first couple of months for Navi support are wrapped up.

RzrTrek:

I wish AMD would mention if it's WHQL or not on the driver page, but it still won't say in either 19.5.2 or 19.8.1 driver highlight, but at least I get their friendly reminder after a few days of use.

All drivers intended to be installed on creators edition and higher are required to be whql and sha2 signed.