After resuming from sleep and playing back video content the system may become unresponsive on Radeon RX Vega series graphics products.

Radeon ReLive Toolbar and Instant Replay features may experience issues or fail to work when playing Guild Wars 2™.

Mouse stuttering may be observed on some Radeon RX graphics products when Radeon WattMan is open and running in the background or other third party GPU information polling apps are running in the background.

Radeon Software Installer may shrink or appear very small when installing on some 4K HDTVs.

Radeon Settings may sometimes experience a hang or crash when viewing the Display tab.

Moonlight Blade™ may fail to launch on some Radeon Graphics Core Next series products.

Titanfall™ 2 may experience a hang or crash on some Radeon GCN1.0 series graphics products.

- CGN 1.0 UVD bug still present.
- As with 17.8.1 and 17.8.2, from a clean installation stopped detecting all installed games on the Gaming tab, and requires a manual scan that will now only detect Steam installations.

And from countless reports they got for it, I am sure 1 person would be able to fix it in couple minutes. I kinda don't get people who buys AMD cards these days for not-mining purposes...

Click to expand...

FLMAO! Yea lets bash AMD here while using 7 year old tech. Yawn. As someone who has had 2x 7850s, 2x 7950s, 4x R9 290s, Fury X and now regulaur fury the problems have been pretty few. Less then I did have with 2X GTX 670s and 2x GTX 970s.

Maybe I never got the UVD bug with my 7850s and 7950s because I ran 3 monitors. I also ran custom bios on my 7950s without the boost.

Everyone will have something that doesnt always work when it works for someone else. But the crying and bashing over the UVD bug is beyond laughable at this point. Really is time to get a new card or go team green. They are not problem free either. I dare you to try 21:9 resolutions on DVI-D and see what happens with an Nvidia gpu. And Nvidias HDMI scaling is a complete effin joke. Or how god awful slow their control panel is even on a nice SSD.

Currently have R9 Fury in main rig, no issues that have happened to me with it in a while, GTX 660 in my server, used for game streaming.Not really any bugs, but at least Geforce Experience looks nice now and loads faster. NCP is a slow ass joke though. 8600GTS in my HTPC. Even with an 80GB raptor its slow as hell to load NCP on Win 7. That is used for older games and media. Then I have a spare rig with GTX 650ti 2GB boost in SLi. That rig is pretty problem free but its a PIECE OF SHITE with HDMI scaling when we using it with HDMI on the TV. Doesnt matter which GPU of the 2 is used. Now this is where it gets funny. Using my HD 5770, HD 6950, guess what, its almost too easy to scale the image to the TV and it still will be 1920x1080. not 1826x1016.

GCN 1.0 is not moved to legacy. This bug is not 1 month old, it's more than 1 year old, there is even a topic on amd forum with someone from amd saying they will look at it but nothing has been done for 1+ year.

But the crying and bashing over the UVD bug is beyond laughable at this point. Really is time to get a new card

Click to expand...

It's his right to complain. Without critics that can be backup with evidences there will be no progress at all.
Want to talk about GCN 1.0 and AMD drivers history? For 1 year after release they had a bug where the textures in dx9 games were showing random corruption, they blamed it on the games when pre GCN AMD/ATI gpu had no such issue. Now for more than 1 year there is this UVD bug that affects GCN 1.0.
So basicaly GCN 1.0 had for more than 2 years nasty bugs in the drivers...
Maybe things are not good on green side also but you know at some point you get tired of the problems that are on one side and you just decide to switch.

Not everyone has the money to buy 101 gpu. But when you can afford to buy 101 gpu it's a bit hard to understand that others can't do that.
The fact that someone doesn't donate to them every 6 months by buying a new gpu doesn't remove his right to ask for drivers that work without problems.

And this is not even the first UVD bug. Someone that had a HD 5xxx knows that if u watch something that uses UVD clocks and play a game the game will not make the card switch to max clocks, it will be stuck at UVD clocks. AMD refused to fix this at driver level, it's an easy fix. Manufacturer refused to release bioses that fix this problem, and guess what it's not exactly the easiest fix by editing the bios with RBE because in some cases you need to change to what the UVD clocks is pointing and not edit that value cause you break stuff (like while you are gaming it will switch like a mad between lowest possible clocks and highest because there is no mid clocks), and that particular change is not available directly in RBE, you need to hex edit the bios and you need to know what you have to change there (btw using RBE to hex edit the bios will make RBE change some bits in some areas that it shouldn't, I don't talk about the checksum fix, yes it works with those changes but those changes are not needed!)...
AMD answer to requests to fix the problem with UVD and HD 5xxx was to upgrade to HD 6xxx.

I can say about Linux support... How Mesa is the only option for not so old cards (while nvidia still offers proprietary drivers for considerable older gpu) and surprise Mesa doesn't work properly with some games and bug reports are closed because Mesa devs don't show real care about games, they care mostly about their stuff passing academics tests, main problem here is that well games don't really follow those academics stuff... Sure progress has been done with Mesa, but there are problems that won't be fixed in the next years due to some Mesa devs mentality!

So yes enough reasons for someone to start to think that this is a shady move from AMD part.

Have you ever took into consideration that someone might not need a new gpu for several years maybe because all the games he/she play work on his 5 years old gpu depiste the fact that are new games (and you need game profiles for most new games, game profiles that are available only in newer drivers that well come with the nice UVD bug)?
Or maybe cause if he/she wants to spend the same amount of money as 5 years ago on a new gpu he/she is not really getting a real upgrade, but mostly a side upgrade?

Wonder how you will react when someone will say that he/she has no problem with NVIDIA gpu because it just happen that he/she doesn't uses HDMI?!? It's kinda same level of ignorance to be honest.

******

I don't really post in this forum because I got tired of people saying that well you use 5+ years hardware (that it just happen to still be listed in the newer drivers as supported) go buy a new one if you have a problem caused by the drivers and of some fanboys/pr that doesn't want to reveal that he/she works for x company (even fanboys have some limits, someone working at pr department has no limits) that think they know everything when the only thing they show is how much blind they are.
Go ahead feed them with money after all this is what they actually want, go ahead believe all their lies and buy their fail products (because it's for the future, a future that well never comes).

When extracted if you check the software included with the driver this one includes a new "PPC" one which when I checked the properties for it the MSI reported as Performance Profile Client but I do not know what it actually does, it did not come up as a choice during the installation process when doing a custom install so it has no purpose on my system and I do not know if it's CPU or GPU related though Polaris and the new Vega GPU's might see it as a choice if it's GPU and if it's CPU some of the Ryzen users might see it pop up as a available install choice if so.

When you set a folder to unpack the driver into you can find the PPC folder and it's MSI file under:

.\Packages\Apps\PPC

I tend to clean out unwanted software before commencing with the driver installation. (Bethesda64 for example with the last three or so drivers, it's their launcher for what I guess is Quake Champions?)

For the rest?

Atiapfxx.exe -r -sys -s test.xml is based on a post by Kn00t for how to dump atiapfxx.blb into a .xml file instead, the command here will dump test.xml in syswow64 which I then cut and paste into a separate folder and then I use the compare plugin (v2.0) for NotePad++ to compare against the previous driver which I also dumped in this way.

That's the Witcher 3 one, what each of these flags do is pretty much unknown, the first one tends to be what gets changed with I think 17.8.2 using 0x22 or something and here it's 0x30 instead, it's a big blob of hex value flags so I have no real idea on what each of them mean. (There's like a hundred+ of them too.)

After that you have the DXX for what I assume is something related to DirectX but I do not know exactly what, this is the pCars2 profile for that.

Near the top of the dump XML you also have a list of OpenGL properties under <area Name="OGL" Privacy="Defined"> some of them have identifiable names like FreeSync but most are unknown though occasionally a driver will see a new property added to this or a edit to a existing one, I assume this is for OpenGL extensions and what not such as OpenGL 4.5 support, unsure if AMD has any support for the upcoming 4.6 version.

Following that there's the PXDynamic profiles which look a bit like this:

These appear to set a Crossfire profile up agianst a specific game or software exe.

Occasionally it'll also have something like this for Steam games in addition to the game exe.
File="Steamappid:570">
(Helps separate things a bit, hi game.exe and launcher.exe although the above example is for DOTA2)

EDIT: Oh and the display driver tends to have further profiles inside the actual .dll files sometimes these are also newer than what the .xml reports so chances are some new upcoming games might be in there and still be supported even if the .xml doesn't have entries for them, yet.
(Halo3.exe might still be in there but it's a few years old now so the initial release plan probably didn't pan out for Microsoft.)

I can say about Linux support... How Mesa is the only option for not so old cards (while nvidia still offers proprietary drivers for considerable older gpu) and surprise Mesa doesn't work properly with some games and bug reports are closed because Mesa devs don't show real care about games, they care mostly about their stuff passing academics tests, main problem here is that well games don't really follow those academics stuff... Sure progress has been done with Mesa, but there are problems that won't be fixed in the next years due to some Mesa devs mentality!