AMD Catalyst 15.10 Beta Driver for Windows is now available!

[Warsam71]

Hello everyone,

Click here to download the driver.

Highlights of the Driver:
· Performance Optimizations:
[FONT=&quot]o [/FONT]Ashes of the Singularity™ ‐ DirectX® 12 Quality and Performance optimizations


Please refer to the Release Notesfor information regarding Known and Resolved Issues, CrossFire Profile enhancements and product compatibility.

For instructions on how to uninstall or install the AMD Catalyst Software Suite, you may refer to the following support resources:

How-To Uninstall AMD Catalyst™ Drivers From A Windows® Based System
How-To Install AMD Catalyst™ Drivers For A Windows® Based System

Please make sure to read the Known Issues sections to learn more about this version of the driver and use the Issue Reporting Form to report any bugs – Thank you!

 

[AtenRa]

thanks sam,

But i would suggest you(AMD) convince the developers of Ashes and Fable to give the benchmarks to the public for testing. Review sites are doing a bad work at this time. No review of Fable with the optimized drivers ever seen the light in the web and im sure the same will happen for Ashes with Catalyst 15.10Beta

 

[Puffnstuff]

Yes thanks for the heads up on the driver.

 

[guskline]

thanks sam,

But i would suggest you(AMD) convince the developers of Ashes and Fable to give the benchmarks to the public for testing. Review sites are doing a bad work at this time. No review of Fable with the optimized drivers ever seen the light in the web and im sure the same will happen for Ashes with Catalyst 15.10Beta

I agree AtenRa

 

[Erenhardt]

Yep,
I want to benchmark my PC aswell.

 

[tential]

thanks sam,

But i would suggest you(AMD) convince the developers of Ashes and Fable to give the benchmarks to the public for testing. Review sites are doing a bad work at this time. No review of Fable with the optimized drivers ever seen the light in the web and im sure the same will happen for Ashes with Catalyst 15.10Beta

Agreed

 

[Despoiler]

thanks sam,

But i would suggest you(AMD) convince the developers of Ashes and Fable to give the benchmarks to the public for testing. Review sites are doing a bad work at this time. No review of Fable with the optimized drivers ever seen the light in the web and im sure the same will happen for Ashes with Catalyst 15.10Beta

http://www.computerbase.de/2015-10/...eue-directx-12-benchmarks-mit-amd-und-nvidia/

 

[Puffnstuff]

I tried to install the new driver earlier and after the installer unpacked it stopped the installation process each time I ran it.

 

[thesmokingman]

Installed no problem. Looks like the flicker issue is resolved too.

 

[AtenRa]

http://www.computerbase.de/2015-10/...eue-directx-12-benchmarks-mit-amd-und-nvidia/

Thanks

If you find another one plz post the link, i would like to see higher resolutions as well.

 

[dacostafilipe]

http://www.computerbase.de/2015-10/...eue-directx-12-benchmarks-mit-amd-und-nvidia/

They disabled MSAA on Epic because of nVidia:

In the latter MSAA was switched off by hand , because the filtering according to Nvidia is not working properly .

 

[3DVagabond]

They disabled MSAA on Epic because of nVidia:

Yeah. They actually believed nVidia. Turned out they were blatantly lying to cover up their own shortcoming with the feature in DX12.

Have we heard if they've got that fixed? What about async compute? Has the driver fix they promised come for that yet?

 

[gamervivek]

One comparison I got off from overclockers.uk site.

Average FR 31.6, GPU Fury X @1100/550, Normal FR 42.5, Medium FR 30.9, Heavy FR 25.7, CPU 3770k @4.3

http://forums.overclockers.co.uk/showpost.php?p=28522910&postcount=32

Now,

Average FR 43.4, GPU Fury X @1120/560, Normal FR 49.3, Medium FR 42.1, Heavy FR 39.9, CPU 3770k @4.2

http://forums.overclockers.co.uk/showpost.php?p=28681695&postcount=250


There is a setting difference, namely time slice. Not sure if it's helping performance or degrading it.

 

[Puffnstuff]

I just tried installing it again and everything worked this time which allowed the driver to install without issue.

 

[AtenRa]

One comparison I got off from overclockers.uk site.

Average FR 31.6, GPU Fury X @1100/550, Normal FR 42.5, Medium FR 30.9, Heavy FR 25.7, CPU 3770k @4.3

http://forums.overclockers.co.uk/showpost.php?p=28522910&postcount=32

Now,

Average FR 43.4, GPU Fury X @1120/560, Normal FR 49.3, Medium FR 42.1, Heavy FR 39.9, CPU 3770k @4.2

http://forums.overclockers.co.uk/showpost.php?p=28681695&postcount=250


There is a setting difference, namely time slice. Not sure if it's helping performance or degrading it.

nice thanks,

Massive CPU performance increases.

Also GPU perf increased substantially

 

[Despoiler]

One comparison I got off from overclockers.uk site.

Average FR 31.6, GPU Fury X @1100/550, Normal FR 42.5, Medium FR 30.9, Heavy FR 25.7, CPU 3770k @4.3

http://forums.overclockers.co.uk/showpost.php?p=28522910&postcount=32

Now,

Average FR 43.4, GPU Fury X @1120/560, Normal FR 49.3, Medium FR 42.1, Heavy FR 39.9, CPU 3770k @4.2

http://forums.overclockers.co.uk/showpost.php?p=28681695&postcount=250


There is a setting difference, namely time slice. Not sure if it's helping performance or degrading it.

I love the AoTS benchmark. Those scatter plots really show just how much better 15.10 is. The driver overhead went from not bad to a more or less flat line. CPU and total score are more consistent, which translates to much better performance.

 

[tential]

We need results at more resolutions than just 1080p though.

 

[gamervivek]

That's too big of a performance increase for me to not raise suspicions. Perhaps the setting difference accounted for a bit, though the setting is higher in number in the new benchmark, so it might be possible that the 15.10 improvement is even higher still.

Perhaps AMD didn't pay much attention to this game, contrary to what the prevailing wisdom was, as the oxide dev on ocn stated a few days back,

Saying we heavily rely on async compute is a pretty big stretch. We spent a grand total of maybe 5 days on Async Shader support. It essentially entailed moving some ( a grand total of 4, IIRC) compute jobs from the graphics queue to the compute queue and setting up the dependencies.

and,

Weirdly, though there is a marketing deal on Ashes with AMD, they never did ask us to use async compute. Since it was part of D3D12, we just decided to give it a whirl.

http://www.overclock.net/t/1575638/...able-legends-dx12-benchmark/110#post_24475280

 

[Dygaza]

One comparison I got off from overclockers.uk site.

Average FR 31.6, GPU Fury X @1100/550, Normal FR 42.5, Medium FR 30.9, Heavy FR 25.7, CPU 3770k @4.3

http://forums.overclockers.co.uk/showpost.php?p=28522910&postcount=32

Now,

Average FR 43.4, GPU Fury X @1120/560, Normal FR 49.3, Medium FR 42.1, Heavy FR 39.9, CPU 3770k @4.2

http://forums.overclockers.co.uk/showpost.php?p=28681695&postcount=250


There is a setting difference, namely time slice. Not sure if it's helping performance or degrading it.

Noticed you were referring to my benchmarks done on oc.uk page. Keep in mind that there is other differences between those 2 shots, than just driver version.

Big difference when it comes to cpu performance was upgrade of ram speed, which clearly shows that DDR1600 ain't enough when you start pushing cpu to the limits. This gave huge cpu performance ugprade (from 68.8 cpu fps to 84.7).

http://forums.overclockers.co.uk/showpost.php?p=28542438&postcount=858

Even bigger difference in cpu performance was the aots patch 0.55.xxxxx which gave huge improvement for cpu. This performance uplit had nothing to do with drivers from AMD or Nvidia.

Also benchmark has evolved since first benchmarks, so direct comparision is hard to make between drivers.

(copied this post to this thread aswell just in case).

Now, there has been real performance uplifts in drivers aswell.

 

[Red Hawk]

"[59792] A black screen may be encountered on bootup on Windows® 10 systems. The system will ultimately continue to the Windows login screen"

Huh, yeah, a couple of my family members' PCs have been doing this. Not my own desktop and laptop though -- the major difference being I have SSD boot drives while they still have HDD. In any case, I hope this gets fixed.