Search results

Updated result for me 3770k @ 4.1GHz Fury X @ 1150/545MHz Drivers16.12.1 Score 5434 Graphics score: 5732 CPU score: 4200 http://www.3dmark.com/3dm/16654998

And if the drivers really were Fiji drivers that had just been quickly tuned to even work on Vega, no wonder you don't get full performance out. There's things in Vega that Fury X don't have, and they would also need drivers, like Primitive discard accelerator from Polaris. Also remember...

These drivers are first WDDM 2.1 drivers from AMD. Might be a reason why there is some boost in DX11 drawcall throughput aswell. Additions in WDDM 2.1: -Shader Model 6.0 -DXGI 1.5 which supports HDR10 and variable refresh rates.

DX11 and DX12 are nothing alike. So that's not a good reason.

Exactly, though DX12 is supposed to spread load better on rendering tasks. It doesn't help for AI, Physics or other stuff. What this one big thread does is beyond us to determine. Here is how threading looks in the game under DX12 for those interestested: We see one thread being more...

Should work very well on 1070 with mixed high and ultra settings to reach that 60 fps marker.

So you say they should punish AMD users by postponing release only because nvidia users don't get boost. Both parties can still keep using DX11 path is they have worse performance.

I got quite massive minimum fps inceases overall. Average and Max fps didn't really raise at all. Overall , a lot better perforamnce under DX12. Also stutters have "gone" (need more gametime to be sure) on my Fury X, and could even increase details. Well DX12 certainly fixes all overhead...

Actually my problems running deus ex was with new afterburner version. If I have it enabled when I start the game, it crashes during gaming evolved title. But I can enable it during game no problem. Edit: Having afterburner running when starting game under DX12 doesn't seem to be the problem...

Well I can select DX12 with Fury X. But game crashes when Gaming Evolved log should pop in, and it crashes steam aswell. Nm, got it running. Dunno which made the trick, disabling afterburner during launch, or simply setting graphics settings again from prelaunch menu.

Just out of curiousity , what cpu are you running deus ex with. Game already takes a lot of cpu when running a single gpu config, so finding extra cpu resources for 2nd card might take or need 12 thread cpu.

It is worth it. Good story so far and gameplay itself works. Also game does run pretty well despite all the salty comments based on benchmark. Then again this is graphics forum so it's natural most comments are biased towards performance and looks instead of gameplay.

You shouldn't really look overall cpu usage that much compared to single threads. Especially main DX thread and AMD driver thread. Not much AMD can do with their driver though for cpu usage. It has been their problem for a long time. What they can do for us Fury X users though, is enable...

Performance is quite decent on my Fury X in game. I would say average on 1080p @ ultra is somewhere around 75. Lowest I've noticed have been around 60-65 fps. I do get cpu bound though in city. Game actually has pretty good cpu threading even under DX11. Ofc for AMD users driver overhead does...

I could never understand why people always moan if game doesn't perform greatly on maxed out settings on cards. That's why we have different settings to choose from. If the developers can't raise amount of effects on ultra settings, we never get better looking games. Though I gotta admit that...

That minimun fps is a bit stupid in this test, as it happens during loading of the scene.

Fury X@ 1135/545Mhz I7-3770k @ 4.1GHz Drivers 16.8.2 DX11 1080p

Given how small cpu usage actual graphics tests have, you will run in cpu problems on very unbalanced setups or SLI / CF configurations with high end cards.

I wonder if this 3dmark time spy bench is ran with AIB board: http://www.3dmark.com/compare/spy/16288/spy/17096/spy/15835# 1530MHz core

Quad SLI is what he means :P Kaap still got that quad F-X setup? Haven't seen any runs with it yet.