I had this error today if its any help:
![]()
I had this error today if its any help:
![]()

Unlike the "super helpful" SE support, AMD support has been nothing but helpful. Earlier today user amdmatt has posted a reply that they have managed to recreate the issue with their internal engineer team, and will start working on a fix. So hang in there guys, it's coming (hopefully).
For the nVidia product users I highly recommend posting this on their support boards as well. You never know, they might fix it as well.
It's still sad that game bugs have to be patched out by the graphics drivers engineers, not the original developers of the game...
Oh wow that's awesome. Honestly even if they don't fix it I just want confirmation that it definitely isn't something I can fix. I put in a support ticket with AMD last week and included as much information as possible so I'm hoping they just finally hit enough complaints for it to be worth looking into. Haven't heard back yet though. Was this just a response to your ticket or was it posted anywhere?Unlike the "super helpful" SE support, AMD support has been nothing but helpful. Earlier today user amdmatt has posted a reply that they have managed to recreate the issue with their internal engineer team, and will start working on a fix. So hang in there guys, it's coming (hopefully).
For the nVidia product users I highly recommend posting this on their support boards as well. You never know, they might fix it as well.
It's still sad that game bugs have to be patched out by the graphics drivers engineers, not the original developers of the game...

anything new from the amd support ?Unlike the "super helpful" SE support, AMD support has been nothing but helpful. Earlier today user amdmatt has posted a reply that they have managed to recreate the issue with their internal engineer team, and will start working on a fix. So hang in there guys, it's coming (hopefully).
For the nVidia product users I highly recommend posting this on their support boards as well. You never know, they might fix it as well.
It's still sad that game bugs have to be patched out by the graphics drivers engineers, not the original developers of the game...
no but what they said last time, they recreated the issue and are trying to fix it while saying: "Please check the Resolved Issues section of the release notes of a future driver release for confirmation that the issue has been resolved."
so yeah. personally i upgraded from 380 to 1080 and has been stable ever since
Wow really? I posted my issue on the amd tech support and they say just to use dx9 and I told them dx9 isn't going to be supported in the future and I bought a dx11 card to use dx11 on. I didn't get a response after that lolUnlike the "super helpful" SE support, AMD support has been nothing but helpful. Earlier today user amdmatt has posted a reply that they have managed to recreate the issue with their internal engineer team, and will start working on a fix. So hang in there guys, it's coming (hopefully).
For the nVidia product users I highly recommend posting this on their support boards as well. You never know, they might fix it as well.
It's still sad that game bugs have to be patched out by the graphics drivers engineers, not the original developers of the game...
Do you have a link to what they say to you?
Here's the link to the current thread on AMD https://community.amd.com/thread/196446
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.
Reply With Quote



