• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

3DMark API Overhead Test 1.2 Scores Thread.

cageymaru

cageymaru

Fully [H]
2FA
Joined
Apr 10, 2003
Messages
23,513
API Overhead Test 1.2
http://www.3dmark.com/3dm/7944553?

AMD Radeon R9 290(1x) and AMD FX-9370

DX11 Multi-threaded draw calls per second
922 615

DX11 Single-threaded draw calls per second
901 188

DX12 draw calls per second
14 429 443

Mantle draw calls per second
10 237 302


Did the simple upgrade to Win 10; not a fresh install. Will do that at a later date as I didn't have the time to do it properly at this time due to real life duties. Of course every program known to man running in the background. Feel free to post your scores!

Primetime:
You should state in the op just how the everyone's scores are not comparable to each other. Its just a very basic comparison of your own system from one driver or api to another. People might try to make comparisons to each others scores, and i don't believe the test was intended that way....just saying cause its easy to get the wrong idea
 
Last edited:
Last I checked with my CF 7970s, I was getting around 23M in DX12 and 22M in Mantle.

DX12 is going to rock when games start coming out for it.
 
You should state in the op just how the everyone's scores are not comparable to each other. Its just a very basic comparison of your own system from one driver or api to another. People might try to make comparisons to each others scores, and i don't believe the test was intended that way....just saying cause its easy to get the wrong idea
 
primetime said:
You should state in the op just how the everyone's scores are not comparable to each other. Its just a very basic comparison of your own system from one driver or api to another. People might try to make comparisons to each others scores, and i don't believe the test was intended that way....just saying cause its easy to get the wrong idea
Click to expand...

+1000... API overhead shouldn't be used as a performance comparison between different machines..
 
DX11 Single Thread:
1,291,426

DX11 Multi-Thread:
1,242,067

Mantle:
26,544,544

DX12:
18,107,012

Rig in sig below...Just upgraded to Windows 10 an hour ago.
 
HEADS UP

The 353.62 driver, the one installed during the Windows 10 rollout, has an issue with DX12, if you enable MFAA, it will disable DX12 and revert to DX11.3 (and you will be unable to run the API test). I couldn't figure out why I did not have DirectX 12 support, and was unable to run 3DMark's API test for DX12. Did multiple clean reinstalls. Finally pinpointed the culprit to MFAA. If you enable MFAA in the NVIDIA CONTROL PANEL, 3D SETTINGS, and then open DXDIAG, it will have reverted back to DirectX 11.3 (and thus unable to run the 3DMark API test). Disabling MFAA and then opening DXDIAG will show DirectX 12 once again.
 
Capture_zpsinvyqyx6.png

well everything works.....next time new driver comes out well see if it changes
 
Maybe He felt that some people should know how one company's drivers seemed to be running behind the other...nothing more. If my card still did not have working drivers for dx12 api, i might be bothered as well. I am more surprised he owns a card that old:D But maybe its in one his older backup systems? But yea i get the humor about 3dmark and [H]
 
Hardly much choice, it is the only thing that is DX12 right now, and I want to run something DX12.

Besdies, it is a good tool to test tweaks and changes to your own machine, and see if they make an impact. It is useless however as a comparison tool to compare cards.

http://hardforum.com/showthread.php?t=1870820
 
Last edited:
AMD Radeon HD 7950(1x) and AMD Phenom X4 Processor 9750
http://www.3dmark.com/3dm/8011343?

DX11 Multi-threaded draw calls per second
431 404

DX11 Single-threaded draw calls per second
438 599

DX12 draw calls per second
5 435 555

Mantle draw calls per second
4 775 104
 
Ran this the other day and forgot to post it. This is a regular Fury, 3Dmark identifies them all as Fury X.


AMD Radeon R9 Fury X(1x) and Intel Core i5-4690K

DX11 Multi-threaded draw calls per second:
1 049 069

DX11 Single-threaded draw calls per second:
1 121 113

DX12 draw calls per second:
14 554 928

Mantle draw calls per second:
13 202 046
 
primetime said:
Im not sure thats accurate either, cause if that were true, how are we running the feature test just fine?;)
Click to expand...

I posted this in the other thread about the feature levels but since its confusing:

http://www.extremetech.com/extreme/...what-amd-intel-and-nvidia-do-and-dont-deliver

CP6tMch.png


One common concern from gamers is that if their cards only support DirectX 12 11_1 or 12_0, they’ll miss out on what DirectX 12 has to offer. It’s important to remember that the multi-threading and multi-GPU capabilities of DirectX 12 that we’ve seen previewed to-date (and demonstrated via Mantle) are still completely available to every feature level. Kepler and older GCN GPUs will absolutely benefit from the new capabilities DirectX 12 delivers. With that said, there are some specific capabilities baked into DirectX 12_0 and 12_1 that gamers with older cards won’t have access to — but as the charts above show, this isn’t a problem unique to AMD, Nvidia, or Intel. No current Intel IGP supports DirectX 12_0, while only Nvidia’s Maxwell hardware supports 12_0 or 12_1.
Click to expand...
 
You must log in or register to reply here.
Back
Top