|
Post by Mat HD on Apr 29, 2017 12:16:01 GMT
The following changes are included... - Inclusion for support of RX400 and RX500 series cards in Windows 7 package.
- AMD still haven't fixed the battleye driver blocking issue so the workaround has been applied to all packages.
- AMD are slowly phasing out Windows 8.1 support (the new RX500 series doesn't support Windows 8.1), therefore this will be the last updated driver for Windows 8.1
Why are you not making more updates to the Windows 8.1 driver after 17.4.4?Apart from AMD slowly phasing out support for this version of Windows, 80% of traffic to this website is from users running Windows 10. Another 15% is from users running Windows 7. The last 5% is a mix of Linux users and Windows 8.1. Most computers that can run Windows 8.1 can also run Windows 10, and people are realising that Windows 10 is a more efficient operating system than Windows 8/8.1. This is especially true with regards to gaming as Windows 10 has full support for DirectX 12 which offers performance improvements as well as graphical improvements over DirectX 11. So, whilst I will keep version 17.4.4 available to download for Windows 8.1 users in the future, it will be the last Bootcamp driver update. If you are still running Windows 8.1, I STRONGLY recommend upgrading to Windows 10. Windows 7 driver packages will still be continually updated as the demand is still significant.
|
|
|
Post by angeloarch on May 4, 2017 20:57:45 GMT
Mat,
Have you tested to see if this driver is stable with the Windows 10 Creators Update? iMac 5k AMD 395X.
Thanks!
Angelo
|
|
|
Post by Mat HD on May 4, 2017 21:27:50 GMT
Yes it's stable.
|
|
|
Post by geofftaylor on May 5, 2017 21:44:47 GMT
Did you roll the edits you made with the v2 releases into your 17.4.4 XG release? I ask because I upgraded from your 17.4.3v1 XG to your 17.4.4 XG and I'm getting flickering graphics in Elder Scrolls Online like all players with AMD cards had with the 17.3.x releases. Going back to your 17.4.3v1 XG solves the flickering issues.
|
|
|
Post by Mat HD on May 5, 2017 21:54:18 GMT
I rolled 17.3.3.instead of 17.3.2 into it. So maybe that is the cause. Not entirely sure
|
|
|
Post by geofftaylor on May 6, 2017 3:57:51 GMT
Okay. It took me a while to figure that out. At first I thought the bug that all ESO players dealt with in 17.3.x was back.
|
|