AMD Radeon Software Crimson 16.4.1

Running the desktop at VSR such as 3200x1800 or 3840x2160 allows for games to downsample in borderless and windowed mode which I tend to use a lot.
(Desktop itself looks pretty bad of course but the games work just fine and that's the important part.)

Also required for Unity Engine games which enforces a semi-borderless display mode.

 

Vulkan beta driver update.
https://support.amd.com/en-us/kb-articles/Pages/Radeon-Vulkan-Beta.aspx

(16.4.1 is version 16.15.2211.1001 )

EDIT: Comparing atiapfxx.blb with the one from 16.4.1 reveals the following differences.

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)

 

Was just testing it out really as i primarily run with an Ultra-widescreen which i cant have VSR run due to the 'obscure' native resolution that AMD wont support

There's probably someway to get it work, just to much effort for me.

It does look like crap but on the flip side, i was getting some weird issues when going from native 1080p desktop to higher VSR games so just switched both to the highest supported resolution on VSR and save me some issues

 

Thats something!
So does one have to edit out the spaces between the in-word chars from atiapfxx.blb manually with n++/uedit? or is there a special method to view the file in an instance.
i mean its readable... but it's a little awkward. like pseudo binary.
maybe some kind of postgre or mariadb table.

 

I'm using a method that Kn00t described in another thread a while back.
(He maintained a profile list on his website here: http://www.kn00tcn.net/site/ati-catalyst-profiles/ )

Basically run cmd.exe / commandline and then from C:\Windows\System32\ you execute this command:

atiapfxx.exe -r -sys -s test.xml

This will create test.xml (Or what you want to name it.) at C:\Windows\SysWOW64\ via the atiapfxx.blb file there.
(Might have to run cmd.exe as admin by for example right clicking on the start menu and selecting "command prompt (administrator)" for the access rights to work when dumping like that as the Windows folder is restricted / protected by default.)

You can then edit it with any text editor.

I use WinMerge or the Notepad++ compare plugin to check against earlier driver releases and see what they've changed but this method does not dump the driver profiles in the actual .dll files so those can contain even newer profile additions as generally the atiapfxx.blb file is updated later so it doesn't have everything.
(I used to use a hex editor for that but AMD changed the way profiles are sorted so new ones are no longer at the bottom and instead I believe it's sorted alphabetically so it's not as easy to check though there are probably better methods for doing this.)

Since I didn't want to install the new drivers as they're primarily for Vulkan I just copied the atiapfxx.blb file over to C:\Windows\SysWOW64\ after renaming the existing one and then after dumping the "blob" into xml format I removed it and renamed the old file back again.
(Although you should be able to just replace it if you want to without any problems and then restart or at least log in and out again to have the driver load the new profile file.)


(For this new driver I also uninstalled the runtime for Vulkan 1.0.3.1 and installed the new 1.0.8.0 version manually although the only Vulkan software I have is Talos Principle with the beta patch and I don't really know if these current 16.4.1 drivers are 100% compatible with the new Vulkan runtimes although I'd imagine it'll work fine as it's still Vulkan 1.0 but with whatever 1.0.8.0 improves on from earlier releases.)

(I'll likely wait for 16.5.x or what might come next and then update to those but these while Vulkan related primarily could have other improvements as the driver version is slightly newer, oh right I also updated CNext/CCCSlim from these drivers and the ACP component as those were newer as well but it's still the 16.4.1 core driver.)

 

Same situation here. I can't record The Division and Overwatch in 1080p. Gameplay is totally smooth but every recording is full of stutters.

However, Action! gives much better result with a negligible impact(extra 1-2 fps drop) on the performance.

I don't know the exact reason with my limited experience and knowledge, but I start to believe Plays.tv isn't very good with old cards. I am currently using 7870 - Tahiti LE.

 

New driver coming today.

https://twitter.com/CatalystMaker/status/724623506785329153

 

Nice.
Thanks for the heads up!

 

somehow every time he posts these, they get delayed ;d fingers crossed for the division preset

 

yeah, i noticed that.

lol

 

http://support.amd.com/en-us/kb-articles/Pages/AMD-Radeon-Software-Crimson-Edition-16.4.2.aspx

Out!

Resolved Issues
The Division™ may experience flickering in AMD Crossfire™ technology mode.
DOTA2™ toggling between borderless fullscreen and exclusive fullscreen can sometimes cause flickering or corruption when in AMD Crossfire™ technology mode.
Some DirectX® 9 applications cannot disable AMD Crossfire™ technology mode through Radeon Settings.
GPU clocks on some products may remain in high states after recovering from an application crash.
A small subset of AMD Radeon™ R9 380 users may be experiencing slower than expected fan speeds.
Power efficiency toggle in Radeon Settings is showing up for some unsupported products.
The check for software updates feature in Radeon Settings may not find the latest available update.
Some games may fail to show up in Radeon Settings gaming tab.
The Radeon Settings option may sometimes disappear as a shortcut from the right-click context menu on desktop after a software upgrade.
Steam®VR Performance Test may experience flickering in AMD Crossfire™ technology mode.
Stuttering or corruption observed while playing Fallout 4™ on some graphics products in AMD Crossfire™ technology mode.
Corruption in Hitman™ when using AMD Crossfire™ technology mode.
Stuttering or freezing in some loading scenes while playing Hitman™ using AMD Crossfire™ technology mode.
Negative scaling seen on Hitman™ when using AMD Crossfire™ technology mode.

 

Still broken