AMD Readies Catalyst Omega 2015 Drivers for November

[Szb84]

...Never fun especially with constricted supplies...

Exactly, they sold a relatively small ammount of FIJI GPU based cards, yet this specific issue is pretty common (just check the AMD support thread) with Fury X, Asus/Sapphire Fury cards and possibly with the Nano.
If this is a hardware issue it affects pretty much all of these GPU's.

A Fury X owner on another forum said he does not have the issue but he's using the card on a Linux distro with a driver which disables powerplay - I think this would explain why he didn't have it. Not to mention AMD has a history with idle state powertune/powerplay issues just remember the blackscreen, flickering, artifacting, etc. issues with too low 2D memory clock on the first GCN cards and the R 200 series.

 

[ZoneDymo]

I have to say that it is pretty sad to hype a driver update.
They are something that should be taken as granted.

....its about the features that potentially are added....Its not about just driver support....did you even read the article?

 

[GhostRyder]

Exactly, they sold a relatively small ammount of FIJI GPU based cards, yet this specific issue is pretty common (just check the AMD support thread) with Fury X, Asus/Sapphire Fury cards and possibly with the Nano.
If this is a hardware issue it affects pretty much all of these GPU's.

A Fury X owner on another forum said he does not have the issue but he's using the card on a Linux distro with a driver which disables powerplay - I think this would explain why he didn't have it. Not to mention AMD has a history with idle state powertune/powerplay issues just remember the blackscreen, flickering, artifacting, etc. issues with too low 2D memory clock on the first GCN cards and the R 200 series.

Yet for me who owns first generation R9 290X's (3 to be precise) I did not have the issue. A lot of that played into unlucky cards mixing poorly with power play just like it does now. Otherwise everyone would have experienced it yet not everyone (And certainly nowhere near even a decent chunk of the cards) had the problems. Its probably going to involve a driver update that changes how the low power state works to correct the problem on the cards that have this issue or your going to have to RMA for a better card that can handle the aggressive settings.

....its about the features that potentially are added....Its not about just driver support....did you even read the article?

Probably not since most assume its all about drivers (Which we get plenty of as is).

 

[Easo]

....its about the features that potentially are added....Its not about just driver support....did you even read the article?

Please believe me that I did read it. I mean't what I said - it still is hype about driver update.

 

[Casecutter]

If this is a hardware issue it affects pretty much all of these GPU's.

I hope you are taking the initiative to work through Sapphire to replace the card, as right today it no long appears FuryX supplies are constrained. And in the past Sapphire has from what I've known pretty accommodating, but at this time your full-court- press is better in rattling them.

I have to say that it is pretty sad to hype a driver update.
They are something that should be taken as granted.

"we do not yet have details on what exactly the update will deliver this time"
Read more: http://wccftech.com/second-special-edition-drivers-amd-november-catalyst/#ixzz3pyXXm9mj

Honestly, someone got an inkling there's a update near-ready for release, and to breath life into the story writers speculate something like Omega, and starts adding fluff to make it appear bigger than what was said in passing.

I doubt AMD had any thought to pre-releasing such info this early, HWBbattle.com had either heard something in passing and speculating on what that was, or again AMD has lose-lipped executives and engineers who still haven't got the message to STFU. When you translate the Korean there's not anything substantial, it's wccftech.com that has written a mountain of text... from the basis of a lowly ant hill.

AMD P-R (although can't point to any absolute trend) would want to control the message, and this doesn't come across as that. I'd say a day-and half before, they like to send cryptic tweet or other social media to set off buzz right before the new program is to release. From the story they aren't sure it's going to even be call Omega again, it may have a new name.

If we look back at Omegas' release it was more about features; 4k Virtual Super Resolution, FreeSync, CrossFire Frame pacing, most of the driver stuff had basically carried over from Beta. It wasn't that big of a deal, and I'll bet we shouldn't buy into any "hype" for what's supposedly arriving.

 

[ZoneDymo]

Please believe me that I did read it. I mean't what I said - it still is hype about driver update.

Then surely you read the second paragraphs first sentence right?
"The 2014 release of Catalyst Omega, besides offering significant performance updates, also introduced major new features such as 4K Virtual Super Resolution (VSR), TressFX 3.0, 5K display support, and various image quality improvements."

I mean....its right there.... and no, non of this is required in driver updates, this is just extra insensitive to buy their product, we are looking forward what more we can do with our videocard.

 

[fullinfusion]

No issues with artifact problems on my FuryX , and hell yeah I cant wait for the newest Omega driver!

The last Omega kicked ass!

 

[xenocide]

this is just extra insensitive to buy their product

AMD doesn't care about Green People.

 

[thesmokingman]

At this time point it is rather annoying to have this problem, especially for people who have no idea what happened. They could end up replacing their monitor!

http://www.techpowerup.com/forums/threads/fury-x-display-corruption-under-low-load.216510/

https://community.amd.com/thread/188642

This is a really old problem. Back in 2012, we fixed it by using UOM w/o Powerplay. Today, we use RTSS to control exactly what apps get hw accel and which do not.