Deus Ex: Mankind Divided PC GPU performance review updated with DirectX 12 results

That's rather sobering. I know it's a beta build, but why even release it in this state.



Those frametimes are terrible for the radeons, which pretty much nullifies the 480's higher fps average over the 1060. That AMD is parading average fps graphs, making them appear to be the dx12 champions while under the hood frametimes are a complete mess is pretty crappy tbh.

 

Perhaps things are a bit more complex than thought? Chill a bit and relax, at least this works better than DX11 in Arkham City, which never left the beta stage.

 

Time and time again it's been shown you can't trust beta software, this game is no exception. All results should be taken with a grain of salt. No-one should be happy for either side with the results we're seeing. Wait for fixes.

 

lol

What used to be a crossfire exclusive feature is now being presented to single Radeon users. Behold microstutter exclusive to Radeon.




Calm you tits it's just a joke.

Best advice don't buy the game. If you still buy this dumpster fire of a release you are telling the game developers that releasing a game in this shape is fine.

 

The game isn't in bad shape at all. The DX11 version is relatively fine. The performance on Ultra is a little low for the image quality, but turning a few settings to high significantly increases performance and it essentially looks the same.The DX12 version is basically experimental at this point -- all DX12 implementations are.

 

I fail to see why we even need DX12 for this game, it does absolutely nothing that DX11 doesn't do. The only reason I'm interested is that it takes the first steps for DX12 but it likely takes a year or two to mature and by that time MS will talk about DX13 anyway.

 

The frametimes in this is game are pretty bad, also the constant stutter doesn't help either.
I've found that using RTSS to cap my framerate to my refresh rate (60), helps a lot with frametimes.
Also if using crossfire disable frame pacing, it also helps smoothing things out.
Also it's sad that and external program (rtss) working better than AMD own framerate limiter.

 

Feynman - so much for reducing cpu overhead then. :banana:

 

That is kind of a huge problem. In DX12 it looks like it would be CPU bottlenecked even at 4K... lol

 

DX12 only helps for game not being cpu bound on rendering part, It can be cpu bound by physics or AI etc however.

 

Not in console games, Jaguar is sooo weak.

 

...

 

Even you PR can see the current DX12 implementation isn't ready for prime-time for this game. It literally is a joke as it stands today.

 

Perhaps games that were designed with DX12 from the ground up (instead of adding it afterwards) will get the job done better as well.

 

ding ding ding..

mvp..

 

The performance is a joke. Who has the hardware to run that thing at a constant 60 fps? 0.1% of players? If even that many. It's obviously unbelievably poorly coded.

 

Different story how? Game is running better on AMD anyhow you turn it. Newest gamehardware benchmark :

Spoiler

Maxwell cards are not doing so well.

 

You do realize thats an old build(game) with 16.8.3 not 16.9.1 drivers for AMD? That benchmarks are not regit and people had been already said that in couple of last pages.

 

Only results that make AMD look good are legit....

Is this the new AMD? Dodgy frametimes and ingame benchmarks.

 

Just because there is a disparity between the benchmark and in game performance doesn't mean it's some malicious action by AMD. There can be a dozen other explanations.

It is kind of frustrating that it's misleading though.