Read more.Games affected include The Witcher EE, various C&C games, and Battle for Middle Earth 1-2.
Read more.Games affected include The Witcher EE, various C&C games, and Battle for Middle Earth 1-2.
Really does not help their cause.
Main PC: Asus Rampage IV Extreme / 3960X@4.5GHz / Antec H1200 Pro / 32GB DDR3-1866 Quad Channel / Sapphire Fury X / Areca 1680 / 850W EVGA SuperNOVA Gold 2 / Corsair 600T / 2x Dell 3007 / 4 x 250GB SSD + 2 x 80GB SSD / 4 x 1TB HDD (RAID 10) / Windows 10 Pro, Yosemite & Ubuntu
HTPC: AsRock Z77 Pro 4 / 3770K@4.2GHz / 24GB / GTX 1080 / SST-LC20 / Antec TP-550 / Hisense 65k5510 4K TV / HTC Vive / 2 x 240GB SSD + 12TB HDD Space / Race Seat / Logitech G29 / Win 10 Pro
HTPC2: Asus AM1I-A / 5150 / 4GB / Corsair Force 3 240GB / Silverstone SST-ML05B + ST30SF / Samsung UE60H6200 TV / Windows 10 Pro
Spare/Loaner: Gigabyte EX58-UD5 / i950 / 12GB / HD7870 / Corsair 300R / Silverpower 700W modular
NAS 1: HP N40L / 12GB ECC RAM / 2 x 3TB Arrays || NAS 2: Dell PowerEdge T110 II / 24GB ECC RAM / 2 x 3TB Hybrid arrays || Network:Buffalo WZR-1166DHP w/DD-WRT + HP ProCurve 1800-24G
Laptop: Dell Precision 5510 Printer: HP CP1515n || Phone: Huawei P30 || Other: Samsung Galaxy Tab 4 Pro 10.1 CM14 / Playstation 4 + G29 + 2TB Hybrid drive
Bad decision by AMD
Given that "response" from Ray M was on December 21st (that's what, 12 days ago?) and a much wider set of faulting DX9 games have now come to light, I rather suspect a more robust response will be coming from AMD. If an engineer sees one thread reporting a fault in one particular game/game series, they're not going to look into it. When it's a huge range of games across multiple developers, it's clearly a bigger issue.
Emergency patch incoming in 3 ... 2 ... 1 ...?
Just because a game came out in 2007 doesn't mean you can just ignore customers who have bought said game and want to run it on your hardware, these customers may also well be trying to play these older games for the first time and are only just purchasing them now. You can still purchase them from digital stores, we are not complaining over some old abandoned DOS games here, we are literally looking at last gen with games like the witcher at least, so when the competition has full compatibility you better sit up and take note of these issues and fix them or face losses.
This. Especially as this will have now escalated way above the paygrade of a lone engineer, PR and senior management will be involved. I'd expect a statement ASAP stating they're looking into it and it will be resolved soon followed by a release in a few days/weeks depending on how hard the problem is to solve.
Skyrim. Thats me not upgrading then anytime soon![]()
While this is true, there's always a tipping point at which the customers lost/bad PR is worth less than the effort to fix something. As I said, the comment quoted in this article was made 12 days ago in response to a specific game issue. If it was one game/series affected then it might not be worth the engineering effort to fix that one game. Now it's clear that it's many games, we're far more likely to see something being done.
I think it's worth remembering that the effort here isn't just "fixing" the driver - before you can even work out how much effort/resource fixing it will take, you have to devote significant effort/resource to working out why the issue has arisen, then working out how to fix it. And all of that effort/resource has to be diverted away from planned activities, which means you end up with late or bad releases of something else ... so yes, sometimes taking the PR hit is worth it in the long term.
Would it not be also potentially the game producers responsibility to provide a hotfix update?
I mean, in 2-5 years time as Graphics Technology leaps ahead, are we still going to expect older technologies to be supported? Should we still be supporting 8-bit, 16-bit and in turn (when we get to 128/64 bit computing xD) 64-bit?
However, I do feel that this is more of Microsoft Problem not setting up the emulation of DX9 on newer hardware. But I don't disagree that it is a bad cop out by AMD.
Why would it? These are all games that worked under the latest hardware on the previous driver. The only change is the driver update. Why would it be up to a game dev to patch their game because a GPU driver stopped it working?
The whole point of high level APIs like DX9 is so that game devs don't need to update their games for new hardware. You use the high level API, and as long as the driver implements it properly your game continues to work regardless.
The only possible way this isn't just AMDs fault is if all these games use the same engine, and that engine has an incorrectly implemented API call. But even in that case, it worked under AMD's previous driver, so AMD must have changed the way something works in the driver, and presumably they did it without testing games under DX9.
However you want to spin this, it's the driver update that broke the games, which puts the onus on AMD to sort it.
That would explain how come my son has been playing it solidly for the last few days without issue then.
Adding to Scaryjim's comment about it sometimes not being worth fixing something, it is usual to lower a bug's importance if there is a usable workaround (downgrade the driver). Don't think that will wash for long here though.
I'm no fan of Microsoft, but I fail to see how this can be their fault? Nothing within their software prevents DX9 from working on newer hardware, AMD have introduced this issue with the latest version of their drivers for their hardware. It's their problem to fix or ignore as they see fit.
This is actually one factor that could let me side more with nvidia for my next gpu even though nvidia aren't the perfect company. I'm still open to AMD cpu's though.
people are still running DX9?
There are currently 1 users browsing this thread. (0 members and 1 guests)