Radeon Settings Version - 2017.0612.1651.28496 (Old from 17.6.2) Driver Packaging Version - 17.10.3251.1003-170627a-315756C-ATI Provider - Advanced Micro Devices, Inc. 2D Driver Version - 8.1.1.1599 Direct3D® Version - 9.14.10.01261 OpenGL® Version - 6.14.10.13476 OpenCL™ Version - 22.19.172.769 AMD Mantle Version - 9.1.10.0189 AMD Mantle API Version - 102400 AMD Audio Driver Version - 10.0.1.1 Vulkan™ Driver Version - 1.5.0 Vulkan™ API Version - 1.0.39 Driver version from Device Manager: 22.19.172.769 (27/6/2017) Download (Win 10 x64 ONLY): http://download.windowsupdate.com/c..._996c5231ae517525ca74764e93b9b5e06a84063d.cab Thanks to 22JHP for the heads up. Just tested one game only. Forza Horizon 3 and the is performance better but not on par with 17.2.1
Radeon Settings Version - 2017.0612.1651.28496 (Old from 17.6.2) Driver Packaging Version - 17.10.3251.1003-170627a-315756C-ATI Provider - Advanced Micro Devices, Inc. 2D Driver Version - 8.1.1.1599 (Old from 17.6.2) Direct3D® Version - 9.14.10.01261 (Old from 17.6.2) OpenGL® Version - 6.14.10.13476 (Old from 17.6.2) OpenCL™ Version - 22.19.172.769 AMD Mantle Version - 9.1.10.0189 (Old from 17.6.2) AMD Mantle API Version - 102400 (Old from 17.6.2) AMD Audio Driver Version - 10.0.1.1 (Old from 17.6.2) Vulkan™ Driver Version - 1.5.0 (Old from 17.6.2) Vulkan™ API Version - 1.0.39 (Old from 17.6.2)
Even though the versions might be the same, the files could be different. This has been the case with previous drivers. If you think of projects on git/svn/bitbucket etc, they could well have code committed without a build version bump. The version number does not reflect each individual commit.
I don't know why amd insists on using 5+ month old vulkan drivers when nVidia has the latest version.
The actual files: All files in 17.6.2 that have 22.19.171.257 version number, this includes the support dll's, and main driver files, have version 22.19.172.769 in 17.7. The 17.7 package though contains only the driver files and the old CCC install (radeon additional settings), it does not include the Vulkan runtime etc. It does have the AMD side Vulkan files though (API files), which although are still 1.0.39 have different files sizes due to different commits no doubt. This does not matter if you have 17.6.2 installed, as anything that 17.7 doesn't have will come from 17.6.2. You can also install the runtime separately which is at version 1.0.51.0, but probably not worth installing separately at this stage if you have 17.6.2 installed.
Yeah I get what you are saying, but if they don't reflect the change, then wth is the point of version numbers using gazillion digits Whatever is the case, the version numbers are clearly not aimed at regular user, so instead of flaunting them in UI, AMD should just hide them.
Yeah there's like three version numbers. First you have the user oriented year-month specification such as 17.6 though for a while now AMD has been using three numbers since they've frequently released multiple drivers per month thus 17.6.1 and 17.6.2 This one's easy to keep track of and users know when a new driver is released just from the simple incremental version number. After that there's the actual driver version number which is incremented to indicate new builds and also tends to include the build or sign dates for the driver. 17.10.3211.1011_20170612_1630 For the full version string for 17.6.2 for example. Minor updates tend to just see the third build version being incremented whereas major changes also tend to change the second value which is usually seen as a branch update and a cause for more major changes or additional features. And then there's the last version number for the driver .dll components for things such as the D3D, OGL, VLK parts of the driver, I'm not really sure how these are updated since newer drivers can still have tweaks to these while retaining the same version number. I guess the Crimson or CNext software might warrant a mention too since it feels like it's on a almost daily build schedule but AMD rarely posts changes for this software unless it's more major enhancements and overall Crimson doesn't feel like it's changed all that much since it's introduction though the code is probably pretty different under the hood but it still lags behind a bit requiring that legacy setting software for a few options and changes such as Wattman could have been tested a bit more against older GPU models before they were switched over. Well hopefully the full actual 17.7.x driver release will see some additional enhancements, focus is probably going to be on Vega for a little while though and going by the currently separate Frontier driver it's going to need it to work out some of those known issues but that's nothing new for a new GPU model release I suppose. I wonder how long they can retain GCN 1.1 compatibility as well, though depending on how that architecture is set up I guess keeping it might not be as big of a problem so if that's so then there's little reason to drop support.
Early GCN support could be around for a while before being shafted like VLIW cards. Really sucks when you have a card whose generation suggests one arch but is actually the previous. Nvidia is really evil with this. Vulkan was like a shot in the arm to older GCN cards.