Regarding AMD and the lack of DirectX 9 support - a simple viewpoint (AMD, please listen!) self.Amd
eingereicht vor 8 Tagen * von delphiprogrammer
Edit: An alpha driver is now available, please give it a try and let us know if it works for you. I have received feedback saying it fixes "The Witcher: Enhanced Edition" already!
https://support.amd.com/en-us/kb-art...ase-Notes.aspx
What's going on?
I'm sure you have all read about AMD's latest mistake, breaking DirectX 9 support for many games in the latest Adrenalin drivers for Radeon cards on Windows 10, Windows 7 and probably also Windows 8 (please confirm!) and basically not caring about it until now, new drivers are in the pipeline:
https://community.amd.com/message/28...omment-2839053
"This title is from 2007, so we are unlikely to devote any valuable engineering resources to this issue, which is most likely caused by outdated API modules."
This is a problem that affects many DirectX 9 games.
A few newer games also appear to be broken by this driver, but the issues are mainly with DirectX 9 titles. I'll list some popular older and newer games confirmed broken by the Adrenalin drivers that work if you roll back to Crimson drivers:
- The Witcher: Enhanced Edition
- The Witcher 2 (some users)
- Guild Wars 2 (some users)
- Command & Conquer Red Alert 3
- Command & Conquer Red Alert 3 Uprising
- Command & Conquer 3 (all expansions/versions)
- Command & Conquer 4 - Tiberian Twilight
- Skyrim
- The Elder Scrolls IV: Oblivion (broken with enhanced sync enabled; worked previously with Crimson)
- StarCraft 2 (some users)
- League of Legends (some users / RX4xx - "display driver has stopped responding and has recovered")
- CSO (some users)
- Battle for Middle Earth 1 - 2
- Tales of Berseria
- Ms. Splosion Man
- S.T.A.L.K.E.R. Lost Alpha (in DirectX 9 mode)
- Painkiller: Black Edition
- PES 2017
- Payday 2 (works, but unstable)
- Source engine games (unstable)
- INJUSTICE: Gods among us (crashes after a short while, works fine with Crimson)
- Recettear: An Item Shop's Tale
- Spellforce 2
- Mini Ninjas
- Crysis (in DirectX 9 mode)
- Heroes of the storm (some users)
- Sin Episodes: Emergence (crashes after a short while, uses Source engine)
- Split/Second (crashes when you start a race)
- Halo Online (removing contrails entirely prevents the crash, looks like a shader issue)
- EDTracker (open source head tracking software, crash in atiumdag.dll)
The list is not exhaustive. I'll add to it occasionally as I hear about more popular games being broken. Games without (something in brackets) are completely broken for the vast majority.
Some people can get these games running regardless with Adrenalin drivers. This does not mean that there is not a problem! We don't currently know why it works for some and not for others.
Games previously listed but removed
What exactly is the issue?
The games may refuse to start, start and crash with various errors (e.g. "Fatal error: Exception in exception handler", "<game name> stopped working") and in many cases the crashes point to an AMD driver DLL named
atiumdag.dll (check Windows event viewer).
Driver versions affected include
17.12.1 and
17.12.2.
Known good driver version without these issues:
17.11.4
Workarounds?
Please help out!
If you are affected by this, please let us know:
The game, which version and any mods you feel may be relevant
Your Windows version, driver version and GPU model
Are you using crossfire?
Do you use more than 1 monitor?
If possible, try rolling back to an earlier driver and let us know if that fixed the problem for you.
Comments
How this slipped past QA is beyond me. It affects a large number of high profile games, often played by streamers.
I have a simple stance on this issue, one that I think AMD must follow to remain relevant in the GPU industry.
You must support all APIs the operating system vendor still provides working support for.
Example:
If you release a driver for Windows 10, you must support all graphics APIs that Microsoft still allow to function (so, DX7+ I think) - but you can drop support for DirectDraw.
If you release a driver for XP, of course you must support DirectDraw (and the latest allowed drivers for XP do include DirectDraw support)
This means going forward, as the OS vendor drops the API completely there is no problem even if AMD also drop it. Why? At that time, developers will create wrappers to allow games relying on those older APIs to function. Look at 3dfx glide and directdraw - both now dropped and both have excellent wrappers.
DirectX 9 is still
highly relevant and even used by indie developers. I listed a couple of wrappers you can try in the workarounds section, but please consider them a temporary workaround for now as they hurt performance and do not have perfect compatibility.
Interestingly, DirectX 9 is still not deprecated by Microsoft, but openGL is! https://msdn.microsoft.com/en-ca/lib.../ff818516.aspx
Edit: This is now hitting various news sources:
https://www.techpowerup.com/240103/a...renalin-driver
https://www.guru3d.com/news-story/am...dx9-games.html
https://www.oneangrygamer.net/2018/0...support/48094/
https://www.notebookcheck.net/Users-....275810.0.html