Latest AMD GPU drivers are forcing the game to crash on startup. Since rolling back is not an option, I wanted to ask if anyone else is experiencing this problem or has some soft of solution. Witcher is an old game thus I believe AMD is not going to bother, plus it is impossible to report an issue to them.

I have the same problem, my game crash on startup and i have latest amd gpu drivers 17.12.2.
i have black screen with a hand and error message witcher cessed functionning

And I have the same -> AMD Crimson 17.12.2, black screen and same error :/

Same issue here. Latest AMD graphic drivers 17.12.2

Same problem here with, R9 390 driver v.17.12.2

I got tired of waiting for AMD to fix this issue, so I rolled back my driver to 17.11.1. Game launches without any problems

Same here, rolled back and it starts right up proper. Now, what should I do now? Just play through the game with old driver or is there something I can do where The Witcher: EE alone plays with the old driver?

I encourage those affected to also complain to AMD here:

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

This is a complete deal breaker. I just built a Ryzen system and was on the look out for a new AMD GPU. Not anymore - sticking firmly with nVidia if this is how we are going to be treated by AMD.

This is what AMD have to say about it:

https://community.amd.com/message/2839053#comment-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 screws over ALL OF US at GOG. We need to let AMD know we wont stand for it.

I started a reddit thread to discuss the issue:
https://www.reddit.com/r/Amd/comments/7ncr3y/regarding_amd_and_the_lack_of_directx_9_support_a/

Wow, that's an extremely shitty attitude that i didn't expect from AMD.

New drivers are always expected to break some old game, they can't test everything, i am not unreasonable, NVIDIA had released drivers couple of months ago that broke the sniper elite games (2&3) it was reported by the community and got fixed,they way it should happen.

The Witcher (2007) is not THAT old of a game and if you consider how famous the series is, its extremely stupid of AMD to not try and fix it.

I play a lot of old games and new so i can't stay with old drivers forever, i have been an AMD "underdog" supporter the same way i support GOG for their better attitude with customers and support, but if they keep f'up old games like this, i am seriously considering switching to team green next time, no matter how i feel about that company as whole.

Hopefully they change their mindset.

Edit: on another note, i dislike the "radeon overlay" feature they crammed in their new drivers "alt+R" i have a feeling this "feature" might be the cause of a lot of problems, anyone knows if there is a way to disable it?

Agreed, that reply from the AMD community rep was tonedeaf and stupid. People like that should not be community reps.

It's absolutely unacceptable that AMD GPU drivers break support for games such as the Witcher.

This is a game still sold today on Steam, Origin and gog.com.

I expect AMD to fix this and I expect this community rep to get relocated to a position more suited to his talents within the company.

I'm having the same problem on the latest drivers, also don't take the word of one forum representative that lacks full knowlege has the final AMD word on this, i'm pretty sure that if CD Project asks them to solve the problem they will do it.

Also you can send a twitte to Terry Makedon he is a real representative of AMD and is on the driver team, if enoug people send him a twitt i'm sure he will not ignore it.

Best solution is to go back to the old drivers until this gets fixed, This is what i just did.

As a temporary work around, please try this openGL wrapper which fixed it for another forum member (with minimal glitches when the game is paused):

https://fdossena.com/?p=wined3d/index.frag

"Terry Makedon (Director of AMD software strategy and user experience) confirmed that they are already working on a fix for the bug which will be available soon"