The issue is being flagged as high importance and should hopefully have a resolution soon(tm) The 16.30 drivers I tested had working freesync so some last min change somewhere must have broken it. AMD do have a Q/A dept or two and they do flag things up and help repro bugs that people report via the website.
That whole reporting site they have is simply horrible.
There is no way to get feedback or see if other people have the same issue(s).
Microsoft has a open bug tracker now (with private flags if requested/required), and they want active participation on open bugs, with all the people that have the same issue all discussing it. They also have a way to report bugs through the feedback app, which also has the ability to up vote something, for "insiders", but, it really is a excellent feature!
https://insider.windows.com/ https://connect.microsoft.com/ and so on.
Wish AMD would follow the same procedures instead of getting the generic write-up when you make the bug report. Yes, I know the new Radeon setting has a 'report issue' which goes to the "survey" site. Seriously, that really needs to be renamed. Survey for reporting issues?
Then, it asks the user for a ton of information that Radeon settings can EASILY get, like part #, OS, system information, and so on. It really is quite silly that Radeon settings won't generate all the requested information, and either open that as a text file, so you can paste the information in, or just dump it to a file, and then upload it to the "survey" site.
That said, speaking of high importance, one of the biggest problems is the 'black screen' issue that is popping up on 285, 380, 380X, and 480 cards (I imagine 460 & 470 as well). Basically, the monitor gets "powered off", and windows is still running, so you have to do everything blindly.
AMD's forums has lots of posts about this, here is one of the more recent ones
https://community.amd.com/thread/200862
Then you got reddit:
https://www.reddit.com/r/Amd/comments/4f65db/r9_380_users_who_have_black_screen_crashes_help/
and so on...
It reminds me of the 6850 fiasco of the GPU crashing and taking the system down with it.
Sorry Spyre, I don't mean to sound harsh, but it is really annoying that there doesn't seem to be anyone who is thinking of ways to simplify and process these reports in any way that the general public can at least see some kind of feedback on their issues or, more importantly, collaborate on the issue in question to help AMD figure out why and when it is happening. Heck, for those that constantly have the issue, they could even run a special debug driver that captures a ton of information about what is going on, and then AMD would have a ton more useful information to see where things are going wrong.
This keep everything secret mentality is the kind of thinking MS did back before they had a leadership change, and they revamped their whole bug reporting & feedback philosophy.
What's not so good is when they break something that was previously working fine. But hey they're beta so they are issued 'as is' so you pays your money and takes your choice I guess. As I've done just roll back to a previous working driver.
