Separate names with a comma.
Discussion in 'AMD Flavor' started by erek, Jan 1, 2018.
That is a huge list of games, I was thinking just a few, not that many!
This is the problem with having companies that don't go through their regulatory departments able to speak to the public lol. You think Raja will ever be able to speak the way he did about AMD products with Intel products? I don't think you will ever hear a word out of his mouth from now on........
LOL Raja, forgot about that guy. Wonder what he's up to these days. I miss him.
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.
Is this really a fiasco? I would call Vega a fiasco that sours the mood, damages their reputation. I wouldn't call this a fiasco. Maybe a misstep, but a small one considering the span of time between the misstep and PR fix.
lol that's a bit of an over reaction. one guy that wasn't the official person to be making comments fucked up and was corrected. seems everyone jumping to conclusions without going to the source. seem familiar?
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, 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.
that was Terry's first response as nobody thought to ask him directly. people just ran with the bad news....
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?
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.
True but TM is the man, if he can't fix it no one can?
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.
99% of the games that I play are either DX9 or DX11.
Breaking popular games like Skyrim and LoL is inexcusable....
Games in the past few years even DX9 games need more than 3 GB of system ram, and today's graphics card even to install them and to use in games REQUIRES more than 4 GB of system ram, 1 GB of system ram is allocated to the OS and system needs, that leaves 3 GB which in a 32 bit system is the max..... If you have a 4 gb card which is pretty much the lowest add in boards of this gen unless you are looking at 3 gb 1060 (this is exactly why I stated a 3gb card when nV released the lower end 1060 is kind of a waste card it becomes a low end card even though its got the horsepower for more), or low end desktop parts, can't do it without more than 4 gb of system ram
So the drop of 32 bit drivers for nV, Even AMD has done this, is warranted, the software they are targeting, needs more memory than what 32 bit OS's can support.
Also one game here or there is not a big deal, we aren't talking one or two games here, that list is only a Partial list, there is no way that many games were not know to work before they released those drivers, they knew it, they didn't have time to fix what ever they needed to, so it is what it is. If they have been working on the interim to fix it (another words they were already actively trying to do this and that first PR response was bogus), the fix will come out shortly, if not we will see it take a month to a few months.
Yep, 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.
Don't worry we'll just re-brand our drivers again, and again, and again and again. Instead of doing a good job!
yeah the 2 fury x I bought sure did deliver, but this is a shit show for sure
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.
I have seen reports that it doesn't affect all cards. I think it is more pre Vega release cards. I certainly have seen mention of 290 series affected.
If I was AMD I wouldn't worry. Most gamers are mature enough not to rage quit a platform over a single fubar. As for the ones that do, in a year or three it'll be Nvidia's turn to shoot themselves in the foot and the idiots will forget about this bit of ancient history in their rush to histrionically rage quit Nvidia and return to AMDs embrace (until the next AMD screwup anyway ).
has anybody here even tried these new drivers? both thread went silent as soon as they were released....
I dont think anyone really cared, like I said if I got a bad driver I would just revert it and wait for a newer driver that fixed it.
thanks tips. not the point...
Quick skim, no one else seems to have checked.
And yet they did not break Skyrim support, not on my computer and therefore, in that game, there is nothing to excuse.
If threads like this go silent once a driver is released, you can be pretty sure everything is now working. (No reason to....... anymore.)
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\
The game was installed in "d:\Games" and the folders in question are located under %APPDATA% - meaning the "c:\users\(user profile name)\appdata\roaming" path. They are not set READ ONLY nor do access to these folders trigger UAC.