AMD Catalyst 15.7.1

Alright i know most of you are really interested in the Drawcall benchies, but seriously how is that being helpful?
Test real games, games like farcry 4, witcher 3, assassins creed unity, shadow of mordor, bf4 online, gta v, watch dogs where performance really matters and not some benchmarks that hardly show anything. I don't give a rats ass about some 10k increase in the draw call benchmark.

The OS is out already, and i can hardly find a review that shows ingame performance.

 

It's a single benchmark we run to compare drivers. If you don't think it's useful then don't look at it and do the benchmarks yourself.

 

While i still like you, synthetic benchmarks don't reflect in real games performance. Fury x wins firestrike and loses to the gtx 980ti in nearly every game.

So running the API bench, doesn't really much and doesn't help much in showing how the new os is doing against the older one.

 

I know the API overhead test is synthetic, but it's one of those things AMD are far behind NVIDIA in, CPU overhead. It might not show that a game runs better but it shows they are optimizing the driver thread to allow more draw calls. It should improve every DX11 game.

 

Performance in games is very, very good.

 

so this f...ing vsr option doesn't work for many users.... it's normal ???

 

API Overhead
1st launch driver for 8.1, no DX12.
2nd 15.200.1040.0 Tonga code path.
3rd 15.200.1040.0 Tahiti code path.
4th 15.200.1023.10 Fiji code path. (quite best in everything. On DX11 just a little bit)
5th 15.200.1046.0 (15.7 WHQL)
6th 15.200.1055.0 (original does not have code path for Fiji, but inf config added by asder00. So not fully Fiji aware.); While it does best in draw calls, its gaming performance is under 1023.10/1046.0 and crashes firefox in case you have game open and then open new tab.
7th 15.200.1046.2 Seems like it has improvements from 15.200.1055 but does not cause crashes.
8th 15.200.1062.1002 (15.7.1 W10 release driver)
Overhead test is basically same for last 3 drivers listed.

 

What feature level is the R9 285 supposed to have?

GPU-z and dxdiag are reporting 11.1, is this correct?

 

API Overhead with these
http://www.3dmark.com/3dm/7945594?

 

It seems the AMD display driver doesn't activate that feature level right now. Your GPU does supprt feature level 12.0 though.

 

Not here. 1046.2 is still the leader in the API overhead test by quite a bit.

http://forums.guru3d.com/showpost.php?p=5131558&postcount=1058

 

Margin of error... 3~4.5% .
If you want to see something funny, what's not margin of error, go to registry find there dword "StutterMode", change its value to 2001 (decimal 8193).
Kill mom & ccc, restart ccc & mom by entering catalyst on desktop, retest A
pi overhead for all APIs.

 

All that did was prevent my display from being shown and caused bootloops. Thanks

 

When I run dx12 api overhead test I get

Direct x12 -API not supported

Anybody ?


DDU used in safe mode and then 15.7.1 installed (win10)

 

Default for Fury is 2002 (on left), 2001 on right:
http://www.3dmark.com/compare/aot/48482/aot/48536
With previous drivers DX12 went even over 15M and mantle did catch up a bit.
For older cards there was max StutterMode 1 or 2 based on card. That 200x code path is apparently not for older cards.
Here it is with 15.200.1023.10:
Left 2002 right 2001
http://www.3dmark.com/compare/aot/45562/aot/45568
AMD is apparently doing a lot of code changes.

 

Latest 3DMark?

 

I wanted to see what that does to my gpu and my minimum fps in tomb raider went up by 4 which it never had done before

 

Yeh all other benchmarks are v1.1 but api test is v1.0

System gui version v4.36.512.0
gui version v1.5893(64bit)

also :
Futuremark 3DMark Professional 1.5.893

 

You need to update to a later 3DMark.

 

Is this newer/better than the latest Win10 driver that came over win update?