AMD Releases Radeon Software Adrenalin Edition 18.11.2 Beta Drivers

[VSG]

AMD today made available the latest version of their Radeon software drivers, Adrenalin Edition 18.11.2, for supported graphics solutions. This brings with it support for the hotly anticipated Battlefield V game title, as well as some fixes to issues that users have been awaiting. Driver software notifications no longer list erroneously the current installed driver version and, more importantly, the annoying bug affecting some RX Vega users of elevated memory clocks even during system idle states has been resolved.

The driver also brings with it support for a Vulkan extension, VK_AMD_memory_overallocation_behavior, that "allows controlling whether explicit overallocation beyond the device memory heap sizes is allowed or not" as AMD puts it themselves. Things are not all rosy, however, with known issues including potential crashing of Assassin's Creed: Odyssey at some locations on Windows 7 systems and possible mouse lag with multi-display setups with at least one display enabled but powered off. This is disappointing considering an older driver update from September had seemingly fixed it too. The drivers are up for download at the link below, hosted directly on TechPowerUp for your convenience, and the change log is available past the break for those interested.

DOWNLOAD: AMD Radeon Software Adrenalin 18.11.2



Support for:

• Battlefield V

Fixed Issues:

• Radeon RX Vega Series graphics products may experience elevated memory clocks during system idle.
• Radeon Software update notifications may sometimes incorrectly list the currently installed driver as an available software update.

Known Issues:

• Some systems running multiple displays may experience mouse lag when at least one display is enabled but powered off.
• Assassin's Creed : Odyssey may experience a game crash at certain locations of the game on Windows 7 enabled system configurations.

Added Vulkan Extension Support:

• VK_AMD_memory_overallocation_behavior
• This extension allows controlling whether explicit overallocation beyond the device memory heap sizes is allowed or not.

View at TechPowerUp Main Site

 

[Upgrayedd]

Guess I never noticed but has the "e" always been missing in "Adrenalin" ??

 

[MrGenius]

Guess I never noticed but has the "e" always been missing in "Adrenalin" ??

I'm pretty sure they've always spelled it that way. Which is fine. Since both spellings, with or without the "e", are acceptable.

 

[Billybobjimjoe]

Bah, humbug. There's a bug that's seems to be affecting my system with every driver version past 18.9.2 - the computer stutters every few seconds. Everything just freezes for a second or two. They had this bug in some earlier driver versions, then it got patched away, and now it's back again.

 

[INSTG8R]

Bah, humbug. There's a bug that's seems to be affecting my system with every driver version past 18.9.2 - the computer stutters every few seconds. Everything just freezes for a second or two. They had this bug in some earlier driver versions, then it got patched away, and now it's back again.

Well with out any kind of system information from you that could mean anything?

 

[PrEzi]

Bah, humbug. There's a bug that's seems to be affecting my system with every driver version past 18.9.2 - the computer stutters every few seconds. Everything just freezes for a second or two. They had this bug in some earlier driver versions, then it got patched away, and now it's back again.

This is not a bug in the drivers. Your hardware is borked.

 

[Billybobjimjoe]

Well with out any kind of system information from you that could mean anything?

I've narrowed it down to the driver and reported it, I don't actually need any help, just stating that the bug, that was previously fixed, is back.

This is not a bug in the drivers. Your hardware is borked.

Ah yes, the peculiarly broken hardware, that's only broken with specific drivers... Hmm... Yes... Very interesting.

 

[PrEzi]

I've narrowed it down to the driver and reported it, I don't actually need any help, just stating that the bug, that was previously fixed, is back.

Ah yes, the peculiarly broken hardware, that's only broken with specific drivers... Hmm... Yes... Very interesting.

Yeah. All the drivers after XYZ are bad.
For You.
Hmmm ... yeah, very interesting indeed ;-)