Hmm I just checked as I was going through the chipset drivers what feels like less than half an hour ago and nothing so that was quite some timing. Nice to see another driver out! EDIT: Ah it's not up on that page without manually altering the URL to 19.6.2 that explains it. 😀 EDIT: Oh and the VLK runtime is up to 1.1.108.0 now. https://vulkan.lunarg.com/sdk/home#windows Guessing the AMD signed VLK runtime files are still in these but either one should work really and it's just the runtime but eh I like using the latest (And official version.) and it is backwards compatible so might as well keep it up to date even if the driver VLK files are more important than some later extension support the driver might not be able to use in full anyway. 😛 Either works really. Ha ha. EDIT: Well then let's see here. amdhcp32.dll amdhcp64.dll These two are removed from 19.6.2 compared to 19.6.1 (AMD Universal Adapter for Abobe going by .DLL name info.) amdhip64.dll This is added as of 19.6.2 AMD Accelerated Parallel Processing OpenCL 2.0 runtime. INF dates these as June 13th over June 4th for 19.6.1 up to 26.20.12001.7006 from 26.20.11015.9003 Or also 19.20.01.07 from 19.10.15.09 (AMD's driver instead of the Windows driver string I think it was.) This parameter has been removed from a number of GPU devices. PP_PhmUseDummyBackEnd (R505, R506, Topaz, Picasso, Carizzo, Raven and Stoney) And for Polaris 12 these two have been added. PP_MCLKStutterModeThreshold AllowSnapshot AllowSnapshot is also added for Polaris 11 and Polaris 10 plus R7500 (Vega) For "Picasso" the following were also removed. PP_Sumo_DisableGfxPowerGatingInUVD DisableFBCSupport EnableLBPWSupport DisableGfxClockGating DisableSysClockGating DisableRlcSmuPGHandshake DisableDynamicGfxMGPowerGating DisablePowerGating DisablePCIConfigAsicReset KMD_GartCheck DisableSAMUPowerGating PP_DriverEnableNBDPM DisableCailLoadUcode PP_DisableVoltageIsland DisableStaticGfxMGPowerGating PP_SclkDeepSleepDisable DisableGfxCGPowerGating PP_GfxOffControl DisableCpPowerGating EnableswGcFwLoading EnableswSdmaFwLoading EnableVCNDPG DisableAllClockGating And then Vega20 (VII) PP_PhmUseDummyBackEnd PP_LWAC These are removed. KMD_EnableDesktopTexture This was added. And finally for the settings. [ati2mtag_RemoveDeviceSettings] PP_Sumo_DisableGfxPowerGatingInUVD PP_ThermalAutoThrottlingEnable Was added. PP_PhmUseDummyBackEnd Was removed. So two new PP (PowerPlay I assume.) properties and then one got removed. And there is no amdhip32.dll file so this is 64-bit / x64 only. EDIT: And now the Atiapfxx.blb to Atiapfxx.xml DXX profile updates. Hitman Mafia 3 Just Cause 4 Twitch Sings DXX profile additions. Sekiro Shadows Die Twice HighPerfGPUAffinity profile additions. Tekken 7 (Well PXDynamic with a HighPerfGPUAffinity flag for a specific exe name.)

Fluent Design transparency effects are working on my rig with these drivers and Windows 1903. I didn't try 19.6.1, though. Cheers!

Yeah, it's great they constantly adding Vulkan support, except that barely any game currently uses it.

Jackalito:

Fluent Design transparency effects are working on my rig with these drivers and Windows 1903. I didn't try 19.6.1, though. Cheers!

Yep, transparency is also working with latest preview version 18917.

I tried Vulkan on World War Z , the only problem is I can't get the vsync to work. It's still screen tearing when vsync is enable , no choice but to use back directx. I am still on 19.5.2 WHQL , haven't try this new 19.6.2 yet , anyone can confirm do you have screen tearing with vsync enable on 19.6.2 or its fix ? Thanks

Placebo effect or maybe not related to this driver but after i updated it bf1 seems to run a lot smoother, noticeably. Also there is an update for chipset driver. It has overhauled installer, more separated from graphics stack.

Jackalito:

Fluent Design transparency effects are working on my rig with these drivers and Windows 1903. I didn't try 19.6.1, though. Cheers!

Sorry for the stupid question but what's "Fluent Design Transparency effects" ? The Readon Settings are kinda "not fluent" for me in previous drivers. Is that what you are talking about?

EDIT.: nvm

ClockClocker:

Sorry for the stupid question but what's "Fluent Design Transparency effects" ? The Readon Settings are kinda "not fluent" for me in previous drivers. Is that what you are talking about?

Windows - Personalization - Themes - Colors - Dark/Light etc.

Transparency works with both

iArucard:

I tried Vulkan on World War Z , the only problem is I can't get the vsync to work. It's still screen tearing when vsync is enable , no choice but to use back directx. I am still on 19.5.2 WHQL , haven't try this new 19.6.2 yet , anyone can confirm do you have screen tearing with vsync enable on 19.6.2 or its fix ? Thanks

Use freesync instead.

Undying:

Transparency works with both Use freesync instead.

my monitor don't support freesync "that is why i am asking this question " do you get it ? and i am asking about 19.6.2 question , are you here troll and make people piss off ?

iArucard:

my monitor don't support freesync "that is why i am asking this question " do you get it ? and i am asking about 19.6.2 question , are you here troll and make people piss off ?

Didnt try WWZ but i tried Rage 2 also running Vulkan with these and have no tearing using freesync. Im sorry for even quoting you. Wont happen again.

There are a few games which don't 'listen' to their respective Radeon settings profile, so I'm forced to set the Global settings to whatever the game needs. Sometimes creating a new profile pointing to the executable instead of the Steam ID helps. Is this improved in the newer version? I experience it in 3D mark, Blue Isle's Valley, south park Fractured But Whole, Train Simulator 2019.

^^ Always like this: Creating a New Game profile - > pointing to the executable in Game directory. Im not having issues with Game profiles, sometimes game profile needs reset (start game - Play) and then set again to work properly (e.g. BF1 & BFV) Note: You can launch Stem game with *.exe shortcut, it will automatically launch Steam for You BTW.

This and the version 19.6.1 causes 3D Mark 11 to not work, it has some sort of DXGI error or something.

It's working fine here. Which test is failing for you?

Krteq:

It's working fine here. Which test is failing for you?

It actually straight up fails right from the start. When I DDU'ed and reinstalled 19.5.2, it all worked fine again. (Vega 56 on Windows 10 1903.)

What’s the latest driver that doesn’t freeze memory clock, except 17.1.1?

Battlefield 1 actually works fine with a custom profile. Even on first load. Maybe launching games through Settings would work indeed.

passenger:

What’s the latest driver that doesn’t freeze memory clock, except 17.1.1?

Try 19.4.3 ..still got working idle clocks for me - everything after that fails (single RX-570 here)