AMD Radeon™ Software Beta for Vulkan™ Version 16.15.2401.1001 Public Vulkan Beta

JonasBeckman, thx for info about this driver.

Driver can be downloaded from here:
https://support.amd.com/en-us/kb-articles/Pages/Radeon-Vulkan-Beta.aspx

As you can see there is not much info about this release on its page.





3dmark firestrike comparison
16.4.1:
http://www.3dmark.com/fs/8165998
Vulkan Beta 16.15.2401.1001:
http://www.3dmark.com/fs/8255272

 

Thanks!
Does it fix sttutter with DS3?
Did anybody test it?

 

Score seems similiar to 16.4.1. Getting close to 10k graphics score. Quick custom run, demo off.

Spoiler

 

2D/Direct3D/OGL/OCL/Mantle/Audio have same versions, yes, they may be compiled differently, but still...
I have currently Vulkan Libraries 1.0.2.0/1.0.3.1.
Maybe it is enough to just install: ..\Packages\Apps\VulkanRT64\VulkanRT\VulkanRT.exe

Edit: seriously, who named that target extraction folder?
"64Bit-AMD-Radeon-Software-Beta-Vulkan-Win10-Win8.1-Win7-Apr19"
For real? Breaking usual naming so everyone has hard time finding this driver in few months in folder.

New Vulkan Package is 1.0.8.0.

Noticed few changes:
- custom resolution settings screen for refresh/timing is gone.
- There is Per Game Overdrive settings
- Per game display scaling is added

 

Vs 16.4.1 all these files are different.

 

Hmm I have a question, does Vulkan help at all if games don't directly support it?

 

these are audio driver components, the rest above was all application files nothing driver related.
nothing important.

 

Yeah.
That's the point.
It's the same.

 

One of the main differences, except vulkan compatibility obviously, are updated crossfire profiles for some games:
http://forums.guru3d.com/showpost.php?p=5261123&postcount=225

 

Can't find any of these profiles under crossfire... :/ Could they be optimizations only?

New profile for F1 2015, for a DX12 version of the game. ( f1_2015_dx12.exe )

Profile for Hitman (2016)

Profile for Need for Speed (2016)

Ori and the Blind Forest: Definitive Edition

Overwatch

World of Warships

(Also includes Vulkan runtime 1.0.8.0 instead of 1.0.3.1)

 

not all profiles are visible.

some of them are driver related profiles.

 

i was really wondering often enough if the compatibility bits of sli dont have a corresponding setting on red side because of "all there is to configure can be done in CCC/Radeon Settings" or because there never was an effort from amd to implement such an option where lower level settings concerning cfx apart from "AFR vs 1x1 vs default" could be made.

 

Should I install this over 16.4.1, or uninstall them, and then install these?

 

Ok, i benched Talos principle under Vulkan before and after the drivers.
And i got an increase in 10FPS.
In ultra settings, on Vulkan i used to have 30FPS, now i have 40.
Altough under DX11 i have 50 XD

 

Installed these right on top of 16.4.1 with no probs.

 

What is your CPU/GPU utilization while you have those fps?

 

Uninstall old drivers via control panel
Use DDU in safe mode : http://forums.guru3d.com/showthread.php?t=379506
Install this drivers : https://support.amd.com/en-us/kb-articles/Pages/Radeon-Vulkan-Beta.aspx

 

Need to check later, already on the bed, and MSI AB overlay don't support vulkan yet, gonna need to do with borderless tomorrow.

 

Haven't tested performance yet. There are the first drivers that didn't give me the "Power Saving" toggle. I believe they are probably the baseline for the next release. The 64bit D3D files look the same, except this one is signed with a tool more than a year newer than the 16.4.1. There might be more differences, but none other that I can see from the properties of both files.

 

Using ddu when there is no problem with regular uninstall/install process is exaggeration, like shooting to a moth with nuclear bomb. Regular install over 16.4.1 would be enough or regular uninstall/install.




Problem with 100% gpu usage while idle for short time stopped today but yesterday after this driver install i've restarted pc at least twice and problem was still remaining. Today i booted pc and problem is not present anymore. To be honest i'm still not sure what was really causing it and what really fixed it.