FFS, really? Async Reprojection only for RX480 and RX470? No love for us FuryX owners? I call total Bullshit

did AMD abandon the R9 series and the Fury line? It seems that way, but my 390 is still new :(

xkm1948FFS, really? Async Reprojection only for RX480 and RX470? No love for us FuryX owners? I call total Bullshit

Yea no kidding! It's ok they want to sell us the new FURY GPU's that are compatible and coming out soon.... ;(

-1nf1n1ty-did AMD abandon the R9 series and the Fury line? It seems that way, but my 390 is still new :(

Tonga/Fiji use a more sucky version of Carrizo DCE/UVD/VCE. In which, the RX/Bristol/Stoney lineup uses an updated version of that same stuff.

AMD's driver team is starting to piss me off. SteamVR Async Reprojection was added last November. That is about 5 months. And now they come out with this half @ssed driver that only support RX480/470. RX480 is no where near playable for 90% of VR titles and they prioritize that GPU over their only available flagship GPUs. Meanwhile, all Nvidia 10XX and 9XX GPUs have full support for Async Reprojection.

Am I the only one having major issues with these drivers? Crashes(BSOD) while installing(before and after restarting). Tried installing them twice now and it keeps happening. Opening GPU-Z after installing says something about Open CL not being installed and to try reinstalling graphics drivers. And it displays wacky clocks(see pic). Afterburner is totally broke. Won't apply OC profiles or let me adjust clocks, voltage, power limit, or fan speeds. My card was stuck @ 500/1500 w/100% fan speed(see pic).



Used DDU to uninstall and then reinstalled previous drivers. Fixed all the problems. So are these drivers screwed or what? I guess I'll try downloading them from AMD and trying one more time. If that doesn't work I quit.

MrGeniusAm I the only one having major issues with these drivers? Crashes(BSOD) while installing(before and after restarting). Tried installing them twice now and it keeps happening. Opening GPU-Z after installing says something about Open CL not being installed and to try reinstalling graphics drivers. And it displays wacky clocks(see pic). Afterburner is totally broke. Won't apply OC profiles or let me adjust clocks, voltage, power limit, or fan speeds. My card was stuck @ 500/1500 w/100% fan speed(see pic).



Used DDU to uninstall and then reinstalled previous drivers. Fixed all the problems. So are these drivers screwed or what? I guess I'll try downloading them from AMD and trying one more time. If that doesn't work I quit.

Can confirm new Crimson driver DOES NOT play nice with Afterburner.

As a matter of fact I have not touched Afterburner/Trixx ever since Wattman support was added to FuryX. I use Wattman to decrease core voltage and overlock a small amount only.

MrGeniusAm I the only one having major issues with these drivers? Crashes(BSOD) while installing(before and after restarting). Tried installing them twice now and it keeps happening. Opening GPU-Z after installing says something about Open CL not being installed and to try reinstalling graphics drivers. And it displays wacky clocks(see pic). Afterburner is totally broke. Won't apply OC profiles or let me adjust clocks, voltage, power limit, or fan speeds. My card was stuck @ 500/1500 w/100% fan speed(see pic).



Used DDU to uninstall and then reinstalled previous drivers. Fixed all the problems. So are these drivers screwed or what? I guess I'll try downloading them from AMD and trying one more time. If that doesn't work I quit.

Look at your clocks in GPUz, they are screwed, and it's probably corrupting the signal sent to the card asking for insane clocks when multiple programs are polling the hardware and accessing or interrupting the card.

Working fine and dandy for me @MrGenius. Wattool is working as well.

I downloaded them directly from AMD and had the same problems after installing. So TPU's copy isn't the issue. I guess I'll roll back to 17.3.3 and report the problem to AMD then. :ohwell:

After seeing your first post @MrGenius I was hesitant to try out the latest beta driver. Figures though it wouldn't cause any issues with a RX 480.

Edit: AMD fixed the issue with "EDID overrides not loading on startup." The only way to fix it at the time was by turning off then on GPU Scaling.
www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU

MrGeniusAm I the only one having major issues with these drivers? Crashes(BSOD) while installing(before and after restarting). Tried installing them twice now and it keeps happening. Opening GPU-Z after installing says something about Open CL not being installed and to try reinstalling graphics drivers. And it displays wacky clocks(see pic). Afterburner is totally broke. Won't apply OC profiles or let me adjust clocks, voltage, power limit, or fan speeds. My card was stuck @ 500/1500 w/100% fan speed(see pic).



Used DDU to uninstall and then reinstalled previous drivers. Fixed all the problems. So are these drivers screwed or what? I guess I'll try downloading them from AMD and trying one more time. If that doesn't work I quit.

Because your GPU is pretty old? First reason. Second: why even update, when the "update" has nothing for your GPU (yes, nothing)? Completely senseless move and problems caused by it.

MrGenius

Lol, that's pretty epic.

No problems here on my 290X.

KananBecause your GPU is pretty old? First reason. Second: why even update, when the "update" has nothing for your GPU (yes, nothing)? Completely senseless move and problems caused by it.

That may be the case with these drivers. But they have fixed things in rather recent drivers relating to my GCN 1.0 card. As recently as 17.2.1 for example www.reddit.com/r/Amd/comments/5gqm2u/async_compute_disabled_on_gcn_10_since_1692/

MrGeniusThat may be the case with these drivers. But they have fixed things in rather recent drivers relating to my GCN 1.0 card. As recently as 17.2.1 for example www.reddit.com/r/Amd/comments/5gqm2u/async_compute_disabled_on_gcn_10_since_1692/

Hint: check log before you update and only update if necessary not if you "feel like it" or so. :rolleyes:

KananHint: check log before you update and only update if necessary not if you "feel like it" or so. :rolleyes:

That's not necessarily bad advice. But the fact is they don't always list things that are fixed with later drivers. AMD has never confirmed or denied causing, and later fixing, the GCN 1.0 async compute issue. But it was in fact a REAL issue(verified buy user driver version experiments including my own). You'll see no mention of the fix in the Radeon Software Crimson ReLive Edition 17.2.1 Release Notes. So you might be getting fixes you don't even have any easy way of knowing about(like being told ahead of time about them in the release notes). Not to mention the fact that if I go to AMD's website they still recommend these latest drivers for my ancient card.

I've seen this "you don't have to install the latest drivers" notion gaining traction lately. And, personally, I find it ridiculous. I have always installed, and will continue to always install, the latest compatible drivers for all my hardware. And I still recommend anybody else to do the same. If it causes a problem, then uninstall them and install previous drivers. It's called rolling back. And the function is built-in to Windows for that very reason.

While I in part agree with your first reasoning your second is just what you said yourself, "ridiculous". Drivers are a thing you should only update when needed or if it's of any (increased) use. Going for updates like this prevents you from doing mistakes like the one you cried about here earlier. Nobody ever said "always install the latest drivers", it's just your opinion, feeling or whatever you mixed up with, why you're doing it (perhaps a inner feeling of "loss" when you don't do it, but it's just a feeling). I don't think AMD or Nvidia are recommending doing so, and I don't recommend doing so, because I know it's not optimal in many cases - upgrading/changing a driver is always a risk too. So going for other drivers when needed, for whatever reason, is simply way better (and avoids unnecessary risks). You could ask me now, how often I had problems with drivers (AMD/Nvidia) - well I'm gonna say it anyway: just a few times, in 15 years+. I bet with your "strategy" it would've been many many times more than that. "Ridiculous". :laugh: "Not necessarily bad advice" - it's way better advice than what you said, I'm pretty sure.

xkm1948AMD's driver team is starting to piss me off. SteamVR Async Reprojection was added last November. That is about 5 months. And now they come out with this half @ssed driver that only support RX480/470. RX480 is no where near playable for 90% of VR titles and they prioritize that GPU over their only available flagship GPUs. Meanwhile, all Nvidia 10XX and 9XX GPUs have full support for Async Reprojection.

Isn't the Fury X reaching eol if it hasn't already?

For me only 17.1.2 works i beter wait some whql whitout blue srean.

xkm1948AMD's driver team is starting to piss me off. SteamVR Async Reprojection was added last November. That is about 5 months. And now they come out with this half @ssed driver that only support RX480/470. RX480 is no where near playable for 90% of VR titles and they prioritize that GPU over their only available flagship GPUs. Meanwhile, all Nvidia 10XX and 9XX GPUs have full support for Async Reprojection.

Reportedly, almost all of them are working on Vega.

I myself would not run out dated drivers unless the manufacture advised so or if i had an issue.. For me this is common sense, but to each their own.

DRDNAI myself would not run out dated drivers unless the manufacture advised so or if i had an issue.. For me this is common sense, but to each their own.

Common knowledge and universal also - Don't fix which isn't broken.