It's the holidays, we got a reply in the affirmative to them fixing this, can we wait a few weeks before the pitchforks?
Edit: List of potential impacted games:
That is a huge list of games, I was thinking just a few, not that many!
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
It's the holidays, we got a reply in the affirmative to them fixing this, can we wait a few weeks before the pitchforks?
Edit: List of potential impacted games:
It looks like the original AMD poster on reddit has since edited his post to remove the original response, which was quoted in the top post of this thread and also on Reddit. An AMD representative posted that they weren't going to fix it and now they have said they will.
Not fanboys at play, just AMD being AMD and then realizing they'd rendered a foot where a mouth should be.
It sounds to me like they initially decided to "do not" and now they are going to "try".
Nothing like public outcry and news spotlights to light fires.
It sounds to me like they initially decided to "do not" and now they are going to "try".
I often wonder who runs AMD's PR department. They don't know what they're doing. The damage has been done to their reputation now. I'm sure a lot of gamers will never run AMD hardware again after this fiasco.
It sounds to me like they initially decided to "do not" and now they are going to "try".
I often wonder who runs AMD's PR department. They don't know what they're doing. The damage has been done to their reputation now. I'm sure a lot of gamers will never run AMD hardware again after this fiasco.
that was Terry's first response as nobody thought to ask him directly. people just ran with the bad news....Well, I wouldn't say that we should disregard what the first guy said, for all we know that could have been AMD's original response/intent. What matters is they heard the feedback afterwards and adjusted quickly with a minimum of delay between the outcry and the 2nd response from Terry Makedon.
Oh please... My eyes are rolling so far back they might get stuck...
AMD forum tech may have jumped the gun. Media wanted a juicy story for the holidays.. By Tuesday AMD seemed to have all hands on deck to get this fixed. There are several other ways to get an official response from AMD, and no one bothered.
Well we will find out soon enough won't we? i mean its not like they didn't have DX9 drivers that were working before right? IF it takes more than one driver release to fix this problem, you better be fully aware, they weren't ready to fix this problem...... And it better come out in the next couple of weeks.
The OP in reddit is absolutely right, this SHOULD NOT have gotten past QA, unless they already knew it was there. Having so many issues they should have known it would bring bad press....
What is so great of having press saying New Driver but its Crap headlines?
What they didn't get enough flack for Vega, Polaris already this past year, they need everyone in RTG screwing up and going out with a bang?
Nothing like public outcry and news spotlights to light fires.
What happened to just using a older driver if the new one borks a old game? This shit used to happen a lot back in the day and that was almost always the standard fix. I dont think AMD does a ton of DX9 testing since thats pretty darn old these days.
Yeah what happens with new cards then cause older drivers don't work on new cards?
These problems have to be fixed till Windows drops support of DX9 and that won't happen anytime soon.
Also I refuse to believe this is incompetence of developers when its happening across many multiple titles.
This has never happened, not like this across multiple titles. This is not common at all. If you are talking about new API's I could agree with that, or even old API that are no longer supported via drivers and are emulated though HAL, this is not the case with DX9
So since Nvidia is dropping support of 32bit drivers are you ok with that since Microsoft still supports 32bit systems? DX9 is ancient and using the newest card to play a old game is not likely. I still love playing Masters of Orion 2 and it was a pain in the ass to make it work with the OS and the video card, I really dont expect those companies to go out of their way on such a old game to make it work. I figured out the solution on my own and I play it every now and again. If I was AMD I would just drop official support of DX9 in this driver set and be done with it since it's well over a decade old standard that no one uses for games anymore. The solution is simple, use the older driver that is the last official support for DX9. Like really old games you make a dedicated simple rig for it with older cheap hardware and your all set.
yeah the 2 fury x I bought sure did deliver, but this is a shit show for sureYep, pretty sure that 290 I bought some years ago is the last AMD card I will ever buy, I would say honestly at this point they're just fucking themselves stupid. It shouldn't take customers bitching a fit to fix something they knew they broke.
It is a huge deal for me personally. I upgraded to the 17.12 series drivers because I cryptomine on my PC when I am not using it. Prior to the release of the Adrinlin drivers, I was stuck on the Beta Blockchain driver from August. Being stuck on that driver ment I couldn't startup games like Wolfenstein 2 without it bitching about the driver being too old, and I wasn't getting full performance while playing Prey on my Vega 64's. I went and bought NiGHTS into Dreams on Steam during the Steam winter sale and it is a game that is having this issue.I dont even understand why this is a issue, one can always use a older driver to fix such a issue.
See that is the issue, some games is not a driver problem per se. When the game doesn't work for anyone, then yes it is a driver problem.It is a huge deal for me personally. I upgraded to the 17.12 series drivers because I cryptomine on my PC when I am not using it. Prior to the release of the Adrinlin drivers, I was stuck on the Beta Blockchain driver from August. Being stuck on that driver ment I couldn't startup games like Wolfenstein 2 without it bitching about the driver being too old, and I wasn't getting full performance while playing Prey on my Vega 64's. I went and bought NiGHTS into Dreams on Steam during the Steam winter sale and it is a game that is having this issue.
On a side note, AMD should add that to the list of affected games: http://steamcommunity.com/app/219950/discussions/0/1621724915779535459/ (list of people, all with 17.12 drivers having this problem). I was trying to find out how to contact AMD to let them know, but I'll just tweet @CatalystMaker.
Also, after reading the list of games in this thread I fired up Recettear: An Item Shop's Tale and that worked fine for me with 17.12.1 and my Vega 64. ;
See that is the issue, some games is not a driver problem per se. When the game doesn't work for anyone, then yes it is a driver problem.
It sounds to me like they initially decided to "do not" and now they are going to "try".
I often wonder who runs AMD's PR department. They don't know what they're doing. The damage has been done to their reputation now. I'm sure a lot of gamers will never run AMD hardware again after this fiasco.
has anybody here even tried these new drivers? both thread went silent as soon as they were released....
has anybody here even tried these new drivers? both thread went silent as soon as they were released....
99% of the games that I play are either DX9 or DX11.
Breaking popular games like Skyrim and LoL is inexcusable....
has anybody here even tried these new drivers? both thread went silent as soon as they were released....
not entirely true. the folder it created might have become read only. I've had this happen when it defaults to c:\program files (x86)\. so to avoid this I install to c:\games\Actually I went out of my way to install BFME2 and test it with these drivers, and it works fine. Interesting is that I did not realize that the BFME games are quite rare now, due to Tolkein estate BS. The games are still very pretty today as well. EA put a LOT of graphical attention into these.
The only issue I ran into while using Windows 10 with it is that for whatever reason, the game was unable to create it's OPTIONS.INI file, and I had to manually make one for it (without it, the game would sit on it's loading screen forever). It's REALLY interesting that the game did not create this file for whatever reason, because it had no problem creating the FOLDER PATH that the file belongs in - if it was a permissions thing it wouldn't be able to do that either...
not entirely true. the folder it created might have become read only. I've had this happen when it defaults to c:\program files (x86)\. so to avoid this I install to c:\games\