My version just says beta on FCU. No issues other then CRU breaks freesync with custom resolutions and monitor overclock.

Memory overclocking slider is still messed like in the previous Fall Update drivers. A setting like 2025MHz will be applied while under load, but the slider will return to the card's default 2000MHz both on wattman and MSI AB, and CPU-Z will also fail to detect the currently applied memory overclock on the Graphics Card tab (but will show it on the Sensor tab under load), and resetting to defaults won't return vram to it's default (will keep previously applied OC). Fortunately (as witht the previous Fall Update drivers) correct voltage is applied while playing video instead of the constant overvolt on 17.10.1 and a few previous drivers. I'll test it for deleting windows printers later, and update this post about it. Edit: The uninstaller still deletes my windows printers.

Seeing how this driver package is 23.20.782.0, and only a minor increment from the 10/10 drivers I linked to, I'm going to say it's a bugfix love update of the 10/10 release.

Another pointless beta driver, but nonetheless, thank you.

guess ill be needing it for Wolf2 latter this week

Somebody check FH3 😀 and Wake up Hicks 😉

I'm missing the GPU workload toggle. I also reinstalled cleaning with DDU. Will not come up. Anyone know why?

RzrTrek:

Another pointless beta driver, but nonetheless, thank you.

AMD remove Mantle support from RX Vega in 17.10.x builds since it's now showing Not Available where the driver number is at, I use the latest DDU & safe mode then install my drivers like I always do. good thing is HBCC does not turn on unlike the two 17.10.x drivers. By the way this driver is nothing, AMD is working on a big driver update like they always do by Nov ish.

NvidiaFreak650:

By the way this driver is nothing, AMD is working on a big driver update like they always do by Nov ish.

Yeah true. 🙄

The rest of the changelog. 🙂

Fixed Issues

Radeon Software may not appear in the uninstall options under "Apps and Features" on Windows® operating systems after a Radeon Software upgrade. Minor corruption may appear in PLAYERUNKNOWN'S BATTLEGROUNDS™ in some game locations when using Ultra graphics settings in game. Radeon Wattman may fail to apply user adjusted voltage values on certain configurations. AMD XConnect™ Technology enabled system configurations may not be detected when plugged in or connected to a system after being previously unplugged during system sleep or hibernation. Hearts of Iron™ IV may experience a crash or system hang during some scenario gameplay. Radeon Settings gaming tab may not automatically populate games detected on the users system.

Known Issues

A random system hang may be experienced after extended periods of use on system configurations using 12 GPU's for compute workloads. Assassin's Creed™: Origins may experience an intermittent application or system hang when playing on Windows®7 system configurations. The GPU Workload feature may cause a system hang when switching to Compute while AMD CrossFire is enabled. A workaround is to disable AMD CrossFire before switching the toggle to Compute workloads. Resizing the Radeon Settings window may cause the user interface to stutter or exhibit corruption temporarily. Corruption may be experienced in Forza Motorsport™ 7 on some HDR displays with HDR enabled in game. Radeon WattMan reset and restore factory default options may not reset graphics or memory clocks and unstable Radeon WattMan profiles may not be restored to default after a system hang. OverWatch™ may experience a random or intermittent hang on some system configurations. Disabling Radeon ReLive as a temporary workaround may resolve the issue. When recording with Radeon ReLive on Radeon RX Vega Series graphics products GPU usage and clocks may remain in high states. A workaround is to disable and then re-enable Radeon ReLive.

EDIT:

Footnotes Testing conducted by AMD Performance Labs as of October 20th, 2017 on the 8GB Radeon RX Vega56, on a test system comprising of Intel i7 7700X CPU (4.2 GHz), 16GB DDR4-3000 Mhz system memory, and Windows 10 x64 using the game Destiny 2 on the highest preset. PC manufacturers may vary configurations, yielding different results. At 2560x1440, the Radeon RX Vega56 scored 52.0 FPS with Radeon Software 17.10.1 whereas the Radeon RX Vega56 scored 74.6 FPS with Radeon Software 17.10.2. Performance may vary based on use of latest drivers. RS-184 Testing conducted by AMD Performance Labs as of October 20th, 2017 on the 8GB Radeon RX 580, on a test system comprising of Intel i7 7700X CPU (4.2 GHz), 16GB DDR4-3000 Mhz system memory, and Windows 10 x64 using the game Destiny 2 on the highest preset. PC manufacturers may vary configurations, yielding different results. At 2560x1440, the Radeon RX 580 scored 34.7 FPS with Radeon Software 17.10.1 whereas the Radeon RX 580 scored 52.2 FPS with Radeon Software 17.10.2. Performance may vary based on use of latest drivers. RS-185 Testing conducted by AMD Performance Labs as of October 20th, 2017 on the 8GB Radeon RX Vega56, on a test system comprising of Intel i7 7700X CPU (4.2 GHz), 16GB DDR4-3000 Mhz system memory, and Windows 10 x64 using the game Assassins Creed: Origins on the highest preset. PC manufacturers may vary configurations, yielding different results. At 2560x1440, the Radeon RX Vega56 scored 44 FPS with Radeon Software 17.10.1 whereas the Radeon RX Vega56 scored 51 FPS with Radeon Software 17.10.2. Performance may vary based on use of latest drivers. RS-186 Testing conducted by AMD Performance Labs as of October 20th, 2017 on the 8GB Radeon RX 580, on a test system comprising of Intel i7 7700X CPU (4.2 GHz), 16GB DDR4-3000 Mhz system memory, and Windows 10 x64 using the game Assassins Creed: Origins on the highest preset. PC manufacturers may vary configurations, yielding different results. At 1920x1080, the Radeon RX 580 scored 45 FPS with Radeon Software 17.10.1 whereas the Radeon RX 580 scored 51 FPS with Radeon Software 17.10.2. Performance may vary based on use of latest drivers. RS-187 Testing conducted by AMD Performance Labs as of October 20th, 2017 on the 8GB Radeon RX Vega56, on a test system comprising of Intel i7 7700X CPU (4.2 GHz), 16GB DDR4-3000 Mhz system memory, and Windows 10 x64 using the game Wolfenstein II on the ultra nightmare preset. PC manufacturers may vary configurations, yielding different results. At 2560x1440, the Radeon RX Vega56 scored 102.8 FPS with Radeon Software 17.10.1 whereas the Radeon RX Vega56 scored 110.7 FPS with Radeon Software 17.10.2. Performance may vary based on use of latest drivers. RS-188 Testing conducted by AMD Performance Labs as of October 20th, 2017 on the 8GB Radeon RX 580, on a test system comprising of Intel i7 7700X CPU (4.2 GHz), 16GB DDR4-3000 Mhz system memory, and Windows 10 x64 using the game Wolfenstein II on the ultra nightmare preset. PC manufacturers may vary configurations, yielding different results. At 2560x1440, the Radeon RX 580 scored 74 FPS with Radeon Software 17.10.1 whereas the Radeon RX 580 scored 77.3 FPS with Radeon Software 17.10.2. Performance may vary based on use of latest drivers. RS-189

EDIT: 17.40 preview : version-> 17.40.0 October 10th. 17.10.2 : version-> 17.40.1021 October 20th. Profiles: Deus Ex Mankind Divided - Crossfire profile updated. Player Unknown's Battlegrounds - Crossfire profile updated. Middle Earth Shadow of War - Crossfire profile updated. Destiny 2 - DXX profile updated. (At a guess these are compatibility "bits" for DX11, still unsure what they do though.) HighPerfGPUAffinity flags -> Assassin's Creed Origins - Also the DXX profile matches the 17.40.0 profile. (DXX profile differed between the October 10th preview driver on AMD's website and the October 11th WU driver.) Ashes of Singularity DOOM Project Cars 2 Sea of Thieves Star Wars Battlefront 2 But what about when compared to 17.10.1 and the driver branch 17.30 ? [spoiler] Crossfire: Deus Ex Mankind Divided - updated. Player Unknown's Battlegrounds - updated. Call of Duty World War 2 - Unchanged profile, location in the profile list moved up a bit though. DXX: Battlefield 4 - Updated. ProjectCars - Updated. Battlefield Hardline - Updated. Grand Theft Auto 5 - Updated. Dragon Age Inquisition - Updated. Fallout 4 - Updated. Player Unknown's Battlegrounds - Updated. Destiny 2 - Updated. (Also named Destiny 2 now instead of Profile.) Assassin's Creed Origins - Added. OpenGL: Metro Last Light (Linux and OS's using OGL.) audjsfrtnisw0 - Added for the OGL properties for this game, it's kinda hard to tell what these do. Solidworks GRFThdurjik8375 - Added as a OGL property. Grid Autosport audjsfrtnisw0 - Another added OGL property. PXDynamic and the HighPerfGPUAffinity flag. (Force/prefer dedicated GPU over integrated, I think.) Assassin's Creed Origins. Ashes of Singularity. Cuphead. DOOM. Fable Fortune. Nishuihan. Raiders of the Broken Planet. Longhunshike. Project Cars 2. DaVinci Resolve. Ruiner. Sea of Thieves. Star Wars Battlefront 2. The Long Dark. Tianyu. Project Cars 1, Forza 7 and Evil Within 2- Not added but it was moved down a bit in the profile list, doesn't mean much but mentioning it. [/spoiler]

RzrTrek:

Another pointless beta driver, but nonetheless, thank you.

Not one of these single Beta driver is useless. They all bring something to the table. And AMD is being very specific about the gains. Why the unnecessary skepticism? Even some of the older cards see performance uplifts, even if they aren't listed.

Cool, no Overwatch fix again! Trash company, i hope they die fast.

For one game? Granted that issue has been around since 17.7 somewhere so whatever broke it had to be something major if AMD still hasn't been able to resolve it, wonder if that's on Blizzard or AMD though, there's some conflicting info on that but you'd probably have to be more involved with either AMD or Blizzard to have some actual info on what's going on with this problem and why it hasn't been resolved. About time it got fixed but if it was easy it would probably have been resolved already owing to how popular the game is. EDIT: Ah no 17.7.x is what fixes the problem, it's the later drivers that broke the game.

COOPOD:

Cool, no Overwatch fix again! Trash company, i hope they die fast.

First of all, take care of your language. 2nd of all...its probably more like Devs of overwatch have messed something up. @JonasBeckman no analysis for this driver? 😀

I just finished adding that in a short while ago in my first post in this thread, initially compared against 17.40 from the Fall Creator preview driver but I also did a comparison with this and 17.10.1 from driver branch 17.30 driver again since the last one was against the first of the Windows Update Fast-Ring insider drivers that were leaked earlier this month. 🙂

Why is my R9 290 not 'select' enough to have the GPU Workload toggle? 🙁

RzrTrek:

Another pointless beta driver, but nonetheless, thank you.

Actually since Watch Dogs 2 crashed after start on a Geforce WHQL driver, WHQL driveres doesn't worth more than beta ones.

SpecChum:

Destiny 2™ Up to 43% faster performance on Radeon™ RX Vega56 (8GB) graphics than with Radeon Software Crimson ReLive Edition 17.10.1 at 2560x1440.(RS-184) Up to 50% faster performance on Radeon RX 580 (8GB) graphics than with Radeon Software Crimson ReLive Edition 17.10.1 at 2560x1440.(RS-185)

Was there some fps bug on 1440P with the AMD GPUs or they just get that much boost?

#JonasBeckman Q: Is there an option for us to Update just those DXX, Affinity Profiles only? I don't have a time for updates now (Testing etc. 17.9.3 working great) But i need new Updates for Radeon Engine 😀

AMD used to have a separate app profiles package but this was discontinued years ago. What you can try is to take the atiapfxx.blb file and place it in System32 and SysWoW64 though I recommend backing up the existing file first since these are flags and properties that could be dependent on the driver .dll files particularly the ones directly related to DirectX, OpenGL, Vulkan or Mantle which is then further split between 32 and 64 bit versions. It's worth a try but there's no way to just update the profile files, Crimson could do with that as a option for AMD to immediately add in profiles for new games if it doesn't require changes to any major part of the driver files directly. (GeForce Experience for Nvidia I believe has this sort of feature for updating to new profiles without needing to wait for the next full driver release.) I don't think you can use the .blb on a per game basis as to just keep it in the game folder like you can with some of the driver files though Destiny 2 here would make for a good test case since AMD did something that fixed whatever held back their GPU's for this game, chances are it's more than just a profile change though and there were something wrong in the driver code itself though with such a high framerate boost it would be immediately evident if this works or not.

THX