Download AMD Radeon Software Crimson Edition 16.4.2

#5262880

velocityx

2016-04-25 21:02

testing the division asap!

#5262883

TheGivingTree

2016-04-25 21:08

This, or the latest Vulcan release, which has the newest drivers?

#5262886

realmadrid

2016-04-25 21:15

what Vulkan is love! <3 ???? there is not even demo to test vulkan

#5262887

vejn

2016-04-25 21:16

Dark souls 3 sttutering fixed ?

#5262890

spectatorx

2016-04-25 21:27

what Vulkan is love! <3 ???? there is not even demo to test vulkan

Did you sleep under rock for last few months? Demos are available since first day of published v1.0 of specification of that API. On the driver... installation went fine which is normal to me, just tested in 3dmark, just for you guys. 16.4.2: http://www.3dmark.com/3dm/11786208 last vulkan beta driver score: http://www.3dmark.com/fs/8255272 Since some time something odd is happening with 3dmark firestrike. Second half of demo is working slow, with extremely low framerate like it never did before but tests work fine as they usually did.

#5262892

velocityx

2016-04-25 21:29

the division still broken on my setup. negative scaling, flickering is gone but now everything is out of sync, has this jumpy/shaky effect of frames not being rendered equally so its just headache inducing in 5 seconds. . its worse than it was. "The Division™ may experience flickering in AMD Crossfire™ technology mode." "We changed it to be shaky/blury/vomit inducing while flicker free!"

#5262901

Rich_Guy

2016-04-25 21:48

AMD Radeon Software Crimson 16.4.2 - DirectX 12 Performance Boosted http://www.overclock3d.net/reviews/gpu_displays/amd_radeon_software_crimson_16_4_2_-_directx_12_performance_boosted/1

#5262902

Chastity

2016-04-25 21:48

This driver package uses Vulkan 1.0.3.1 vs 1.0.8.0 from Vulkan beta. If you install 16.4.2 over Vulkan beta, the vid driver remains from the vulkan beta, and you will have both Vulkan runtimes installed.

#5262914

Undying

2016-04-25 22:01

Thanks. Gonna be testing them soon.

#5262915

TonyTurbo

2016-04-25 22:03

The Division crossfire profile is **** poor. Flickering gone but I get worse fps on 2 cards than on 1 card, and the scaling is a joke. Plus, there's a constant stutter to the game now. Bravo everyone involved, you did great at teasing us with a half baked fix. https://c2.staticflickr.com/2/1490/26040038113_dbbb4ee740_b.jpg

#5262941

Blackfyre

2016-04-25 22:43

I'll test these later today.

#5262973

heroxoot

2016-04-25 23:53

I actually got the corruption in FO4 without crossfire, so hopefully it's fixed for me too. Since there are not DS3 fixes, I will assume the frame rate issues people are experiencing are at the game's fault.

#5262995

Spartan

2016-04-26 01:01

+200k drawcalls in dx 12 with this driver. AOTS dx 12 benchmark same fps as before, ROTTR dx 12 benchmark became a stuttery mess.

#5263005

Xzess

2016-04-26 01:23

For me vs 16.4.1: Ashes of the singularity better CPU utilization in Dx12. Much better framerrate from 23 to 30 on same test. Rest of games i tested are smoother less frametime I think, not too much... Clocks are estable when gaming now, bit less driver overhead I see here. Temps are 2º-4º higher on idle.

#5263007

Spartan

2016-04-26 01:28

For me vs 16.4.1: Ashes of the singularity better CPU utilization in Dx12. Much better framerrate from 23 to 30 on same test. Rest of games i tested are smoother less frametime I think, not too much... Clocks are estable when gaming now, bit less driver overhead I see here. Temps are 2º-4º higher on idle.

Good to know amd is improving performance for everyone, except for fx owners. I'm glad I only have to keep this thing for 2 more weeks max.

#5263013

the9quad

2016-04-26 01:55

Yeah The Divisions CFX profile is useless. At least AMD tried, so I won't complain. I will be using just one card though.

#5263022

janos666

2016-04-26 02:33

I think this driver might fixed some DVI/HDMI audio related issues. Although the HDMI Audio drivers have the same version numbers and build dates (both the codec and system device), so may be it was simply the re-installation process (I also used DDU this time, I don't always do that).

#5263023