XFX Radeon RX 5600 XT THICC 3 review
Fractal Design Define 7 XL review
Guru3D Rig of the Month - January 2020
Palit GeForce RTX 2070 SUPER GamingPro review
Team Group T-Force DarkZα 3600 MHz DDR4 review
Corsair Scimitar Elite RGB gaming mouse review
Cougar 700K Evo keyboard review
Aorus Liquid Cooler 360 review
AMD Ryzen Threadripper 3990X review
Corsair A500 CPU air cooler review
Download: AMD Radeon Adrenalin Edition 18.2.3 Drivers
AMD just released build 18.2.3 of the Radeon Adrenalin Edition drivers. This release focuses on supporting the upcoming or recently launched titles: Sea of Thieves, Brass Tactics and Final Fantasy XII: The Zodiac Age with performance improvements and quality fixes for end users.
Support For
- Sea of Thieves
- Up to 29% faster performance using Radeon Software Adrenalin Edition 18.2.3 on the Radeon RX Vega 64 (8GB) graphics card than with Radeon Software Adrenalin Edition 18.2.2 at 3840x2160.
- Up to 39% faster performance using Radeon Software Adrenalin Edition 18.2.3 on the Radeon RX 580 (8GB) graphics card than with Radeon Software Adrenalin Edition 18.2.2 at 1920x1080.
- Brass Tactics
- Final Fantasy XII The Zodiac Age
- Up to 13% faster performance using Radeon Software Adrenalin Edition 18.2.3 on the Radeon RX Vega 56 (8GB) graphics card than with Radeon Software Adrenalin Edition 18.2.2 at 2560x1440.
- Up to 20% faster performance using Radeon Software Adrenalin Edition 18.2.3 on the Radeon RX 580 (8GB) graphics card than with Radeon Software Adrenalin Edition 18.2.2 at 2560x1440p.
Fixed Issues
- Radeon FreeSync may intermittently incorrectly engage during Chrome video playback resulting in playback flicker.
- Radeon FreeSync may rapidly change between min and max range when enabled causing stutter in fullscreen games on multi display system configurations.
- Flickering may be observed on the performance metrics overlay when Enhanced Sync is enabled on some Radeon FreeSync connected displays.
- Radeon Overlay may exhibit minor flickering when enabled while playing games using the Vulkan™ API.
- Fortnite™ may experience lighting or fog corruption on some graphics quality presets.
- Radeon ReLive instant replay clips may intermittently contain small amounts of audio distortion.
- Middle-earth™: Shadow of War™ may experience an application crash when launched as a Universal Windows® Application.
- For Honor™ may experience an intermittent application crash on launch.
Download: Intel HD graphics Driver Download Version: 15.65.3.4944 - 02/14/2018 10:18 AM
Intel released a new integrated graphics driver, this batch is compatible with Apollo Lake, 6th, 7th, and 8th generation and Kindom comes with game optimizations....
Download: AMD Radeon Adrenalin Edition 18.2.2 Driver - 02/12/2018 11:54 PM
AMD just released their AMD Radeon Software Crimson ReLive Edition 18.2.2 driver. This release focuses on support for the upcoming launch of Kingdom Come: Deliverance with performance and stability o...
Download: AMD Radeon Adrenalin Edition 18.2.1 Drivers WHQL - 02/07/2018 09:27 PM
AMd released Radeon Software Crimson ReLive Edition 18.2.1 driver. Radeon Software Adrenalin Edition, designed to give gamers deeply immersive gameplay and inspired by today’s era of social...
Download: 3DMark for Windows v2.4.4254 - 02/05/2018 01:47 PM
Futuremark released 3DMark for Windows v2.4.4254 (Incl. Time Spy), which is now available. This is a minor update for 3DMark. Benchmark scores are not affected....
Download: Final Fantasy 15 benchmark - 02/01/2018 08:13 PM
Square Enix offers you a new benchmark to grab, play and test with, the all-new Final Fantasy XV benchmark offers a test suite that outputs some result scores. Technologies like Ultra HD and HDR are...
JonasBeckman
Senior Member
Posts: 16054
Joined: 2009-02-25
Senior Member
Posts: 16054
Joined: 2009-02-25
#5522165 Posted on: 02/23/2018 12:05 AM
Atiapfxx.exe -r -sys -s test.xml
Test.xml via Notepad++ and it's Compare 2.0 plugin against Test_.xml from the previous driver and the following has changed.
First of all there's the usual version number and build date.
February 19th for these, February 6th for 18.2.2
17.50.25.01 for these drivers, 17.50.17.04 for 18.2.2
OGL
p2ZE4h
Q24K1j
o6I2er
a1Sd9R
UIq32e
lD4h2H
These properties were added with this driver, impossible to say what they do from the name alone but continued OpenGL 4.6 support or extensions perhaps? Just a guess and it could be something else.
Some have names like the above other have plain text names such as FreeSync so it could be either general compatibility or they extended or added something different for this API, hard to tell from the file like this with these names.
Crossfire
Final Fantasy XII has a Crossfire profile now
Sea of Thieves had it's Crossfire profile updated.
Sea of Thieves - Updated
Final Fantasy XII (12) - Added
Again these can't really be deciphered from this file alone, the bits are visible but kinda hard to say what does what and they're really long too for some of these games.
0x23,0x00,0x00,0x01,0x00,0x00,0xFF,0xFF,0x40,0x00,0x00,0x00,0x17,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x22,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x06,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x13,0x00,0x00,0x00,0x04,0x00,0x00,0x00,0x35,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x36,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x1C,0x00,0x00,0x00,0x80,0x00,0x00,0x00,0x01,0x00,0xFF,0xFF,0xBC,0x03,0x00,0x00,0x12,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x18,0x00,0x00,0x00,0x70,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x73,0x01,0x00,0x00,0xFE,0xFF,0xFF,0x1F,0xFE,0xFF,0xFF,0x9F,0x01,0x00,0x00,0x00,0x28,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x88,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x73,0x01,0x00,0x00,0x00,0x06,0x00,0x00,0x00,0x04,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x90,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x72,0x00,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x02,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x98,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x72,0x00,0x00,0x00,0x00,0x04,0x00,0x00,0x00,0x04,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xA0,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x70,0x00,0x00,0x00,0x00,0x04,0x00,0x00,0x00,0x04,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x05,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xA8,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x71,0x00,0x00,0x00,0xFE,0xFF,0xFF,0x1F,0xFE,0xFF,0xFF,0x1F,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xB0,0x03,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x04,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x08,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xB8,0x03,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x00,0x65,0x04,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xC0,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0xA3,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xC8,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x71,0x00,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x02,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xD0,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x74,0x00,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x02,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xD8,0x03,0x00,0x00,0x04,0x00,0x00,0x00,0x8E,0x01,0x00,0x00,0x20,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xE0,0x03,0x00,0x00,0x04,0x00,0x00,0x00,0x71,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xE8,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x73,0x01,0x00,0x00,0xFE,0xFF,0xFF,0x1F,0xFE,0xFF,0xFF,0x1F,0x01,0x00,0x00,0x00,0x28,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xF0,0x03,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x00,0x00,0x02,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xF8,0x03,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x00,0x00,0x30,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x00,0x04,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x00,0x00,0xC0,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x08,0x04,0x00,0x00,0x05,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x0A,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x06,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x0D,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x0D,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x19,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x19,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x19,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x21,0x00,0x00,0x01,0x02,0x00,0xFF,0xFF,0x00,0x00,0x00,0x00,0x03,0x00,0xFF,0xFF,0x04,0x00,0x00,0x00,0x00,0x00,0x00,0x00,
True
That's 18.2.2 for Sea of Thieves.
0x24,0x00,0x00,0x01,0x00,0x00,0xFF,0xFF,0x40,0x00,0x00,0x00,0x17,0x00,0x00,0x00,0x03,0x00,0x00,0x00,0x22,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x06,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x13,0x00,0x00,0x00,0x04,0x00,0x00,0x00,0x35,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x36,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x1C,0x00,0x00,0x00,0x80,0x00,0x00,0x00,0x01,0x00,0xFF,0xFF,0x24,0x04,0x00,0x00,0x14,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x18,0x00,0x00,0x00,0xC8,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x73,0x01,0x00,0x00,0xFE,0xFF,0xFF,0x1F,0xFE,0xFF,0xFF,0x9F,0x01,0x00,0x00,0x00,0x28,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xE0,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x73,0x01,0x00,0x00,0x00,0x06,0x00,0x00,0x00,0x04,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xE8,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x72,0x00,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x02,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xF0,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x72,0x00,0x00,0x00,0x00,0x04,0x00,0x00,0x00,0x04,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xF8,0x03,0x00,0x00,0x03,0x00,0x00,0x00,0x70,0x00,0x00,0x00,0x00,0x04,0x00,0x00,0x00,0x04,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x05,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x00,0x04,0x00,0x00,0x03,0x00,0x00,0x00,0x71,0x00,0x00,0x00,0xFE,0xFF,0xFF,0x1F,0xFE,0xFF,0xFF,0x1F,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x08,0x04,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x04,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x08,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x10,0x04,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x00,0x65,0x04,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x18,0x04,0x00,0x00,0x03,0x00,0x00,0x00,0xA3,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x20,0x04,0x00,0x00,0x03,0x00,0x00,0x00,0x71,0x00,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x02,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x28,0x04,0x00,0x00,0x03,0x00,0x00,0x00,0x74,0x00,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x02,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x30,0x04,0x00,0x00,0x04,0x00,0x00,0x00,0x8E,0x01,0x00,0x00,0x20,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x38,0x04,0x00,0x00,0x04,0x00,0x00,0x00,0x71,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x40,0x04,0x00,0x00,0x03,0x00,0x00,0x00,0x73,0x01,0x00,0x00,0xFE,0xFF,0xFF,0x1F,0xFE,0xFF,0xFF,0x1F,0x01,0x00,0x00,0x00,0x28,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x48,0x04,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x00,0x00,0x02,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x50,0x04,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x00,0x00,0x30,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x58,0x04,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x00,0x00,0xC0,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x60,0x04,0x00,0x00,0x03,0x00,0x00,0x00,0x70,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x68,0x04,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x04,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x28,0x08,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x70,0x04,0x00,0x00,0x05,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x0A,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x06,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x0D,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x0D,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x19,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x19,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x19,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x21,0x00,0x00,0x01,0x02,0x00,0xFF,0xFF,0x00,0x00,0x00,0x00,0x03,0x00,0xFF,0xFF,0x04,0x00,0x00,0x00,0x00,0x00,0x00,0x00,
True
That's 18.2.3 for SoT.
DXX
Sea of Thieves - Updated.
18.2.2
0x22,0x00,0x00,0x01,0x00,0x00,0xFF,0xFF,0x10,0x00,0x00,0x00,0x13,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x55,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0xFF,0xFF,0x38,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x35,0x00,0x00,0x00,0x00,0x10,0x00,0x00,0x00,0x10,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x48,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x54,0x00,0x00,0x00,0x00,0x0A,0x00,0x40,0x28,0x00,0x00,0x00,
18.2.3
0x22,0x00,0x00,0x01,0x00,0x00,0xFF,0xFF,0x08,0x00,0x00,0x00,0x13,0x00,0x00,0x00,0x01,0x00,0x00,0x00,
Again these don't really say much, there's less of whatever these are in 18.2.3 now but if that is something like DirectX Extension or whatever it might mean that could just be that the game now requires less overrides or "hacks" for this driver though that's almost mostly a guess, in either case the release notes show a nice performance boost.
OpenGL profiles.
Catia
0xC8000023
0x00020000
These two were added.
0x00000002
This one was removed.
PXDynamic
Age of Empires Definitive Edition - Added.
Brass Tactics and Brass Tactics Arena - Added.
Sea of Thieves - Added
The Lab - Added
Crossfire exe profiles.
18.2.2
18.2.3
Sea of Thieves Test (Beta?) - SoTGameTest.exe -> SoTGame-Test.exe
Both drivers appear to have already had a profile for the full game.
Final Fantasy XII (12) Zodiac Age - Added as per the above Crossfire profile file property.
(And they got the exe name right too, they usually do though thankfully.)
Atiapfxx.exe -r -sys -s test.xml
Test.xml via Notepad++ and it's Compare 2.0 plugin against Test_.xml from the previous driver and the following has changed.
First of all there's the usual version number and build date.
February 19th for these, February 6th for 18.2.2
17.50.25.01 for these drivers, 17.50.17.04 for 18.2.2
OGL
These properties were added with this driver, impossible to say what they do from the name alone but continued OpenGL 4.6 support or extensions perhaps? Just a guess and it could be something else.
Some have names like the above other have plain text names such as FreeSync so it could be either general compatibility or they extended or added something different for this API, hard to tell from the file like this with these names.
Crossfire
Final Fantasy XII has a Crossfire profile now
Sea of Thieves had it's Crossfire profile updated.
Sea of Thieves - Updated
Final Fantasy XII (12) - Added
Again these can't really be deciphered from this file alone, the bits are visible but kinda hard to say what does what and they're really long too for some of these games.
That's 18.2.2 for Sea of Thieves.
That's 18.2.3 for SoT.
DXX
Sea of Thieves - Updated.
18.2.2
18.2.3
Again these don't really say much, there's less of whatever these are in 18.2.3 now but if that is something like DirectX Extension or whatever it might mean that could just be that the game now requires less overrides or "hacks" for this driver though that's almost mostly a guess, in either case the release notes show a nice performance boost.
OpenGL profiles.
Catia
These two were added.
This one was removed.
PXDynamic
Age of Empires Definitive Edition - Added.
Brass Tactics and Brass Tactics Arena - Added.
Sea of Thieves - Added
The Lab - Added
Crossfire exe profiles.
18.2.2
18.2.3
Sea of Thieves Test (Beta?) - SoTGameTest.exe -> SoTGame-Test.exe
Both drivers appear to have already had a profile for the full game.
Final Fantasy XII (12) Zodiac Age - Added as per the above Crossfire profile file property.
(And they got the exe name right too, they usually do though thankfully.)
RzrTrek
Senior Member
Posts: 2358
Joined: 2012-04-16
Senior Member
Posts: 2358
Joined: 2012-04-16
#5522167 Posted on: 02/23/2018 12:17 AM
That was fast, thanks, now time for the update.
That was fast, thanks, now time for the update.
NvidiaFreak650
Senior Member
Posts: 330
Joined: 2013-07-18
Senior Member
Posts: 330
Joined: 2013-07-18
#5522175 Posted on: 02/23/2018 01:19 AM
ViRGE
Member
Posts: 36
Joined: 2016-12-23
Member
Posts: 36
Joined: 2016-12-23
#5522195 Posted on: 02/23/2018 03:55 AM
Why AMD dont use the latest Vulkan API?
Why AMD dont use the latest Vulkan API?
JonasBeckman
Senior Member
Posts: 16054
Joined: 2009-02-25
Senior Member
Posts: 16054
Joined: 2009-02-25
#5522208 Posted on: 02/23/2018 06:14 AM
It usually takes a while before AMD updates to a newer SDK, I tend to just rip and use the latest runtime from the full SDK in the meantime since it's backwards compatible (For the bug fixes.) but for full functionality (Such as the new extensions.) it will take a update to the drivers for it to be fully utilized although I don't think any current Vulkan games makes use of the current SDK either and the same likely goes for many of the current software that are using Vulkan such as emulators but as I see it there's no harm to updating to a newer runtime and getting some extra bug fixes although it might still be a while before AMD's Vulkan drivers are updated to a newer SDK version for full support and functionality.
VulkanRT.rar
http://www76.zippyshare.com/v/GhGIa2h1/file.html
1.0.68.0 runtime.
https://vulkan.lunarg.com/doc/sdk/1.0.68.0/windows/release-notes-1.0.html
For those runtime (loader) fixes primarily.
(Extension wise conservative rasterization is apparently a big thing from what I've been reading.)
For NVIDIA I think they're on 1.0.67.0 for the beta Vulkan branch drivers they're maintaining and then the release branch drivers use 1.0.58.0 I think, it usually takes a driver branch update for the VLK driver additions to be merged into the release branch so they too don't update immediately.
(The Vulkan branch is pretty bleeding edge though for development use.)
It usually takes a while before AMD updates to a newer SDK, I tend to just rip and use the latest runtime from the full SDK in the meantime since it's backwards compatible (For the bug fixes.) but for full functionality (Such as the new extensions.) it will take a update to the drivers for it to be fully utilized although I don't think any current Vulkan games makes use of the current SDK either and the same likely goes for many of the current software that are using Vulkan such as emulators but as I see it there's no harm to updating to a newer runtime and getting some extra bug fixes although it might still be a while before AMD's Vulkan drivers are updated to a newer SDK version for full support and functionality.
VulkanRT.rar
http://www76.zippyshare.com/v/GhGIa2h1/file.html
1.0.68.0 runtime.
https://vulkan.lunarg.com/doc/sdk/1.0.68.0/windows/release-notes-1.0.html
For those runtime (loader) fixes primarily.
(Extension wise conservative rasterization is apparently a big thing from what I've been reading.)
For NVIDIA I think they're on 1.0.67.0 for the beta Vulkan branch drivers they're maintaining and then the release branch drivers use 1.0.58.0 I think, it usually takes a driver branch update for the VLK driver additions to be merged into the release branch so they too don't update immediately.
(The Vulkan branch is pretty bleeding edge though for development use.)
Eastcoasthandle
Senior Member
Posts: 2336
Joined: 2006-05-22
Senior Member
Posts: 2336
Joined: 2006-05-22
#5522211 Posted on: 02/23/2018 06:35 AM
anyone getting any performance uplift with these drivers?
anyone getting any performance uplift with these drivers?
ViRGE
Member
Posts: 36
Joined: 2016-12-23
Member
Posts: 36
Joined: 2016-12-23
#5522222 Posted on: 02/23/2018 07:43 AM
JonasBeckman, thank you for the response! but there is another thing that crossed my mind, Sea of Thieves it is running on DX12, how can AMD with an driver update get "Up to 39% faster" when the whole DX12/vulkan thing was about having "paper thin" drivers and leave the low level access to the game developers?
It usually takes a while before AMD updates to a newer SDK...
JonasBeckman, thank you for the response! but there is another thing that crossed my mind, Sea of Thieves it is running on DX12, how can AMD with an driver update get "Up to 39% faster" when the whole DX12/vulkan thing was about having "paper thin" drivers and leave the low level access to the game developers?
JonasBeckman
Senior Member
Posts: 16054
Joined: 2009-02-25
Senior Member
Posts: 16054
Joined: 2009-02-25
#5522224 Posted on: 02/23/2018 07:48 AM
The API allows for leveraging the full power of the GPU but it requires considerable skill and time to get the most out of and driver level optimizations and tweaks isn't entirely ruled out even if the software developer is now in control over things like multi-GPU support and specific GPU optimizations.
Even Frostbite has shown some struggles with this and their use of DX12 and they have specific paths for different GPU architectures in their engine code though that's also one of the reasons the engine is so well optimized already for it's DX11 API.
This and Sea of Thieves far as I know is actually running under DirectX 11, I will have to check though.
EDIT: Yep Sea of Thieves is actually using DX11
Other UWP games have used that API as well since both DX11 and DX12 are supported, some of the initial launch games used DirectX 12 but I think DirectX 11 is the more commonly used API now.
Developers are more familiar with it likely being one key reason, Remedy switched over to DX11 for Quantum Break for example (Stating familiarity with said API as a key reason behind that decision.) when the game was released on Steam and despite AMD's advantage with low-level API support at least early on the game actually retained the same level of performance on AMD GPU's and then NVIDIA cards saw some nice gains.
Not sure if this still holds up now with both AMD and NVIDIA having improved support even further both for newer GPU hardware and also for the software and drivers but I don't think Microsoft is pushing for DX12 quite as heavily as they did initially.
Thus games like ReCore, Killer Instinct, Age of Empires 1 Definite Edition and Sea of Thieves use DX11 but DX12 is still a thing for some titles such as Halo Wars 2 and Forza 7 and from the sounds of it some of these titles use it pretty well.
(Gears of War 4 comes to mind, NVIDIA's drivers are currently having some problems with it though which I'm not sure what that's caused by but it's been in the release notes for known issues for a few driver releases now.)
The API allows for leveraging the full power of the GPU but it requires considerable skill and time to get the most out of and driver level optimizations and tweaks isn't entirely ruled out even if the software developer is now in control over things like multi-GPU support and specific GPU optimizations.
Even Frostbite has shown some struggles with this and their use of DX12 and they have specific paths for different GPU architectures in their engine code though that's also one of the reasons the engine is so well optimized already for it's DX11 API.
This and Sea of Thieves far as I know is actually running under DirectX 11, I will have to check though.
EDIT: Yep Sea of Thieves is actually using DX11
Other UWP games have used that API as well since both DX11 and DX12 are supported, some of the initial launch games used DirectX 12 but I think DirectX 11 is the more commonly used API now.
Developers are more familiar with it likely being one key reason, Remedy switched over to DX11 for Quantum Break for example (Stating familiarity with said API as a key reason behind that decision.) when the game was released on Steam and despite AMD's advantage with low-level API support at least early on the game actually retained the same level of performance on AMD GPU's and then NVIDIA cards saw some nice gains.
Not sure if this still holds up now with both AMD and NVIDIA having improved support even further both for newer GPU hardware and also for the software and drivers but I don't think Microsoft is pushing for DX12 quite as heavily as they did initially.
Thus games like ReCore, Killer Instinct, Age of Empires 1 Definite Edition and Sea of Thieves use DX11 but DX12 is still a thing for some titles such as Halo Wars 2 and Forza 7 and from the sounds of it some of these titles use it pretty well.
(Gears of War 4 comes to mind, NVIDIA's drivers are currently having some problems with it though which I'm not sure what that's caused by but it's been in the release notes for known issues for a few driver releases now.)
LocoDiceGR
Senior Member
Posts: 2033
Joined: 2011-10-22
Senior Member
Posts: 2033
Joined: 2011-10-22
#5522234 Posted on: 02/23/2018 08:32 AM
Installed them as soon i woke up...everything went smooth, no issues!
Installed them as soon i woke up...everything went smooth, no issues!
ViRGE
Member
Posts: 36
Joined: 2016-12-23
Member
Posts: 36
Joined: 2016-12-23
#5522246 Posted on: 02/23/2018 09:09 AM
Got the info wrong about Sea of Thieves, THX for the explanation, Since I got my Fury, the difference in The Division between DX11 and DX12 and DooM Vulkan made look a lot more in this Low level APIs, but they are not getting a lot of adoption sadly.
Talking about Fury, any idea if they will alow HBM1 overclock again in the future? my Nano run nice with 550mhz without extra voltage on 16.2.2 WHQL, but I don't want to go back, 18.2.3 gave me 5 extra FPS in Mass Effect Andromeda.
The API allows for leveraging the full power of the GPU but it requires considerable skill and time to get the most out of and driver level optimizations and tweaks isn't entirely ruled out even if the software developer is now in control over things like multi-GPU support and specific GPU optimizations (...) Yep Sea of Thieves is actually using DX11
Got the info wrong about Sea of Thieves, THX for the explanation, Since I got my Fury, the difference in The Division between DX11 and DX12 and DooM Vulkan made look a lot more in this Low level APIs, but they are not getting a lot of adoption sadly.
Talking about Fury, any idea if they will alow HBM1 overclock again in the future? my Nano run nice with 550mhz without extra voltage on 16.2.2 WHQL, but I don't want to go back, 18.2.3 gave me 5 extra FPS in Mass Effect Andromeda.
LocoDiceGR
Senior Member
Posts: 2033
Joined: 2011-10-22
Senior Member
Posts: 2033
Joined: 2011-10-22
#5522247 Posted on: 02/23/2018 09:11 AM
No, dont wait for something like that.
They disable it for a reason.
Talking about Fury, any idea if they will alow HBM1 overclock again in the future?
No, dont wait for something like that.
They disable it for a reason.
JonasBeckman
Senior Member
Posts: 16054
Joined: 2009-02-25
Senior Member
Posts: 16054
Joined: 2009-02-25
#5522249 Posted on: 02/23/2018 09:41 AM
Yeah the official response is something along the lines of Wattman not supporting HBM1 overclocking and I think they mentioned the memory modules not having a dedicated sensor but from discussions in the big Fury X thread here recently and similar discussions on overclocking on forums such as Overclockers and OCUK you can still adjust memory timings via bios modding and temps aren't too problematic even if they don't have the temperature sensor and some other tech found on HBM2 with Vega, which has sometimes been said to be another reason AMD hasn't brought back Fiji overclocking for memory.
That and for Fiji and HBM1 the memory operates under for what is known about it it's at least a three step speed process which is 500 Mhz and the stock speed, 545.45 Mhz, 600 Mhz and finally 666 Mhz.
It rounds down to the closest available but most GPU's seemed capable of hitting 545 without too much problems although above that only certain GPU's handled 600 Mhz and I don't think 666 was reachable though with timing and bios editing now possible that might be doable with some tweaking to both relaxing the timings and maybe upping voltage a little bit though 600 would probably be more stable while still showing some good gains.
You do need a good core clock speed too which also affects total results, Fiji is rated for up to 512 GB/s for it's memory bandwidth but in testing under the fastest conditions it reaches around 380 GB/s and then it's down to 350 GB/s for more general usage scenarios.
I'm not sure what the conditions for the benchmark is but 400 - 450 might be reachable with some timing tweaks and a little bump in clock speed which is also holding the GPU back when it comes to total memory bandwidth.
Vega in comparison does around 480 GB/s I believe it was but compared to traditional GDDR5 (Or GDDR5X with the 1080Ti which is pretty fast too.) there's also less latency and HBM2 on Vega has some resources for cache usage with HBCC and faster storage although HBCC hasn't been entirely stable in some software though the stock 8 GB VRAM is often more than enough for most games and software though certain scenarios can see it utilized more fully.
I still have a lot of reading up to do on this subject at least trying to get a more basic understanding of the technology and surrounding information and so on, HBM has some nice advantages from what I know about it although the supply shortage and pricing makes it a bit problematic too but with some improvements and revisions this could be a replacement for GDDR5 and GDDR6 at least for high-end GPU models since pricing will likely be higher for a long while still and the shortage issue might also take a while to resolve.
Also from Reddit and regarding FreeSync:
https://www.reddit.com/r/Amd/comments/7zij3s/radeon-software-adrenalin-edition-1823-release/
AMD_Aric RTG Engineer 14 points 7 hours ago
Thanks for the update. The multimonitor Freesync issue is known. I can't recommend borderless fullscreen with Win 10 Fall Creators Update at this time.
Either disable Freesync for that game or use fullscreen exclusive. We added per-application Freesync game profiles so you can do this easily from Radeon Settings now.
(RTG or Radeon Technology Group meaning a driver engineer.)
Personally I find borderless to be incredibly useful but the flicker issue and this particular statement is problematic for FreeSync monitor owners, at least it sounds like fullscreen is now mostly fixed as is the issue with Chrome and what I assume is a hardware acceleration problem particularly for video playback often using a higher power and clock state.
(RS3 hasn't been entirely problem free even after a couple of months of cumulative updates though it sounds like RS4 going RTM next month might have resolved some issues with lag, stuttering and responsiveness in general but I don't know if it's fully resolved or if there's still some problems remaining.)
EDIT: What's the status of known issues on AMD's driver page?
Known Issues
A random system hang may be experienced after extended periods of use on system configurations using 12 GPU's for compute workloads.
Water textures may appear to be missing in World of Final Fantasy™.
Destiny 2™ may experience an application hang in the mission "Heist" on some Radeon GCN1.0 products.
Radeon Overlay may intermittently fail to enable when toggled in some games.
Radeon Chill hotkey may fail to reset when Radeon Settings is restored to defaults.
FFmpeg application may experience corrupted output for H264 video streams.
So nothing about a known issue (In the known issues section, well...) in regards to borderless mode and FreeSync at all then.
Well it's a good thing sources like Reddit and OCUK exists for picking up these things then.
(OCUK has a AMD representative that posts fairly often, often has some insight even if he's community manager and not directly part of the tech team or driver engineer or what to say.)
And I guess that while rare those few people who have a 12 GPU setup using it for compute workload smight have to wait a bit longer, then again to compare to NVIDIA's drivers they do have had a few known issues listed in the release notes for the last couple of releases now too so nothing new for either vendor I suppose.
(And for both of them these sections are probably just a highlight and not a total of known and fixed issues with these drivers.)
EDIT: References to some of the thins I posted here, this here is a Reddit AMD topic for Fiji memory overclocking and it's removal when Wattman replaced the older interface.
https://www.reddit.com/r/Amd/comments/7ghtp1/why-amd-has-removed-the-memory-overclocking-for/
And this is a benchmark which also covers memory bandwidth and the measure speed for a Fury X GPU.
https://techreport.com/review/28513/amd-radeon-r9-fury-x-graphics-card-reviewed/4
The question then becomes whether the Fury X is also bandwidth limited in this test, or if its performance is limited by the render back-end. Whatever the case, the Fury X "only" achieves 387 GB/s of throughput here, well below the 512 GB/s theoretical max of its HBM-infused memory subsystem.
(Still fast and there's other factors in play too and depending on what the GPU is doing the bottleneck could be in other areas too meaning this doesn't have a major impact on overall performance.)
Yeah the official response is something along the lines of Wattman not supporting HBM1 overclocking and I think they mentioned the memory modules not having a dedicated sensor but from discussions in the big Fury X thread here recently and similar discussions on overclocking on forums such as Overclockers and OCUK you can still adjust memory timings via bios modding and temps aren't too problematic even if they don't have the temperature sensor and some other tech found on HBM2 with Vega, which has sometimes been said to be another reason AMD hasn't brought back Fiji overclocking for memory.
That and for Fiji and HBM1 the memory operates under for what is known about it it's at least a three step speed process which is 500 Mhz and the stock speed, 545.45 Mhz, 600 Mhz and finally 666 Mhz.
It rounds down to the closest available but most GPU's seemed capable of hitting 545 without too much problems although above that only certain GPU's handled 600 Mhz and I don't think 666 was reachable though with timing and bios editing now possible that might be doable with some tweaking to both relaxing the timings and maybe upping voltage a little bit though 600 would probably be more stable while still showing some good gains.
You do need a good core clock speed too which also affects total results, Fiji is rated for up to 512 GB/s for it's memory bandwidth but in testing under the fastest conditions it reaches around 380 GB/s and then it's down to 350 GB/s for more general usage scenarios.
I'm not sure what the conditions for the benchmark is but 400 - 450 might be reachable with some timing tweaks and a little bump in clock speed which is also holding the GPU back when it comes to total memory bandwidth.
Vega in comparison does around 480 GB/s I believe it was but compared to traditional GDDR5 (Or GDDR5X with the 1080Ti which is pretty fast too.) there's also less latency and HBM2 on Vega has some resources for cache usage with HBCC and faster storage although HBCC hasn't been entirely stable in some software though the stock 8 GB VRAM is often more than enough for most games and software though certain scenarios can see it utilized more fully.
I still have a lot of reading up to do on this subject at least trying to get a more basic understanding of the technology and surrounding information and so on, HBM has some nice advantages from what I know about it although the supply shortage and pricing makes it a bit problematic too but with some improvements and revisions this could be a replacement for GDDR5 and GDDR6 at least for high-end GPU models since pricing will likely be higher for a long while still and the shortage issue might also take a while to resolve.
Also from Reddit and regarding FreeSync:
https://www.reddit.com/r/Amd/comments/7zij3s/radeon-software-adrenalin-edition-1823-release/
AMD_Aric RTG Engineer 14 points 7 hours ago
Thanks for the update. The multimonitor Freesync issue is known. I can't recommend borderless fullscreen with Win 10 Fall Creators Update at this time.
Either disable Freesync for that game or use fullscreen exclusive. We added per-application Freesync game profiles so you can do this easily from Radeon Settings now.
(RTG or Radeon Technology Group meaning a driver engineer.)
Personally I find borderless to be incredibly useful but the flicker issue and this particular statement is problematic for FreeSync monitor owners, at least it sounds like fullscreen is now mostly fixed as is the issue with Chrome and what I assume is a hardware acceleration problem particularly for video playback often using a higher power and clock state.
(RS3 hasn't been entirely problem free even after a couple of months of cumulative updates though it sounds like RS4 going RTM next month might have resolved some issues with lag, stuttering and responsiveness in general but I don't know if it's fully resolved or if there's still some problems remaining.)
EDIT: What's the status of known issues on AMD's driver page?
Known Issues
A random system hang may be experienced after extended periods of use on system configurations using 12 GPU's for compute workloads.
Water textures may appear to be missing in World of Final Fantasy™.
Destiny 2™ may experience an application hang in the mission "Heist" on some Radeon GCN1.0 products.
Radeon Overlay may intermittently fail to enable when toggled in some games.
Radeon Chill hotkey may fail to reset when Radeon Settings is restored to defaults.
FFmpeg application may experience corrupted output for H264 video streams.
So nothing about a known issue (In the known issues section, well...) in regards to borderless mode and FreeSync at all then.
Well it's a good thing sources like Reddit and OCUK exists for picking up these things then.
(OCUK has a AMD representative that posts fairly often, often has some insight even if he's community manager and not directly part of the tech team or driver engineer or what to say.)
And I guess that while rare those few people who have a 12 GPU setup using it for compute workload smight have to wait a bit longer, then again to compare to NVIDIA's drivers they do have had a few known issues listed in the release notes for the last couple of releases now too so nothing new for either vendor I suppose.
(And for both of them these sections are probably just a highlight and not a total of known and fixed issues with these drivers.)
EDIT: References to some of the thins I posted here, this here is a Reddit AMD topic for Fiji memory overclocking and it's removal when Wattman replaced the older interface.
https://www.reddit.com/r/Amd/comments/7ghtp1/why-amd-has-removed-the-memory-overclocking-for/
And this is a benchmark which also covers memory bandwidth and the measure speed for a Fury X GPU.
https://techreport.com/review/28513/amd-radeon-r9-fury-x-graphics-card-reviewed/4
The question then becomes whether the Fury X is also bandwidth limited in this test, or if its performance is limited by the render back-end. Whatever the case, the Fury X "only" achieves 387 GB/s of throughput here, well below the 512 GB/s theoretical max of its HBM-infused memory subsystem.
(Still fast and there's other factors in play too and depending on what the GPU is doing the bottleneck could be in other areas too meaning this doesn't have a major impact on overall performance.)
OnnA
Senior Member
Posts: 10280
Joined: 2014-10-25
Senior Member
Posts: 10280
Joined: 2014-10-25
#5522284 Posted on: 02/23/2018 12:02 PM
Got the info wrong about Sea of Thieves, THX for the explanation, Since I got my Fury, the difference in The Division between DX11 and DX12 and DooM Vulkan made look a lot more in this Low level APIs, but they are not getting a lot of adoption sadly.
Talking about Fury, any idea if they will alow HBM1 overclock again in the future? my Nano run nice with 550mhz without extra voltage on 16.2.2 WHQL, but I don't want to go back, 18.2.3 gave me 5 extra FPS in Mass Effect Andromeda.
Just ask Fox for Mod
(2min of his time 
)
And you'll end up with some hefty Uplift in FPS (4-9FPS depends on Game & API in 1440p)
Got the info wrong about Sea of Thieves, THX for the explanation, Since I got my Fury, the difference in The Division between DX11 and DX12 and DooM Vulkan made look a lot more in this Low level APIs, but they are not getting a lot of adoption sadly.
Talking about Fury, any idea if they will alow HBM1 overclock again in the future? my Nano run nice with 550mhz without extra voltage on 16.2.2 WHQL, but I don't want to go back, 18.2.3 gave me 5 extra FPS in Mass Effect Andromeda.
Just ask Fox for Mod
(2min of his time )And you'll end up with some hefty Uplift in FPS (4-9FPS depends on Game & API in 1440p)
SpajdrEX
AMD Vanguard
Posts: 2195
Joined: 2006-05-07
AMD Vanguard
Posts: 2195
Joined: 2006-05-07
#5522313 Posted on: 02/23/2018 01:46 PM
Any idea if AMD plan to unify adrenalin driver with driver for int. graphic as Ryzen 2200g/2400G have?
Any idea if AMD plan to unify adrenalin driver with driver for int. graphic as Ryzen 2200g/2400G have?
Click here to post a comment for this news story on the message forum.
Senior Member
Posts: 629
Joined: 2017-09-11
ok thanks for heads up downloading /updating now