Palit GeForce GTX 1630 4GB Dual review
FSP Dagger Pro (850W PSU) review
Razer Leviathan V2 gaming soundbar review
Guru3D NVMe Thermal Test - the heatsink vs. performance
EnGenius ECW220S 2x2 Cloud Access Point review
Alphacool Eisbaer Aurora HPE 360 LCS cooler review
Noctua NH-D12L CPU Cooler Review
Silicon Power XPOWER XS70 1TB NVMe SSD Review
Hyte Y60 chassis review
ASUS ROG Thor 1000W Platinum II (1000W PSU) review
Review: Hitman 2016: PC graphics performance benchmarks
We peek at the all new Hitman (2016) in our usual ways. We have a look at performance with the newest graphics cards and technologies. We'll test the game on the PC platform relative towards graphics card performance with the latest AMD/NVIDIA graphics card drivers. Multiple graphics cards are being tested and benchmarked.
Read the article right here.
« Unreal Engine Sizzle Reel 2016 GDC Video · Review: Hitman 2016: PC graphics performance benchmarks
· FSP Adds Hydro Series 80 Plus Bronze Power Supplies »
kinggavin
Senior Member
Posts: 297
Joined: 2014-11-06
Senior Member
Posts: 297
Joined: 2014-11-06
#5245976 Posted on: 03/16/2016 11:24 AM
console parity, windows 10, windows store,dx12 none of it seems to be working very well at the moment , im happy staying on windows 7 gta 5 online runs and looks great , i wait until they fix everything and theres a big boost in graphics and performance
console parity, windows 10, windows store,dx12 none of it seems to be working very well at the moment , im happy staying on windows 7 gta 5 online runs and looks great , i wait until they fix everything and theres a big boost in graphics and performance
Noisiv
Senior Member
Posts: 8186
Joined: 2010-11-16
Senior Member
Posts: 8186
Joined: 2010-11-16
#5245978 Posted on: 03/16/2016 11:28 AM
So much for DX12 being an easy and obvious win.
HW requirements, engineering time and developer skill level has gone up, but FPS has remained the same
DirectX 12 is for those who want to achieve maximum GPU and CPU performance,
but there’s a significant requirement in engineering time, as it demands developers to write code at a driver level that DirectX 11 takes care of automatically.
For that reason, it’s not for everyone.
Since it’s “closer to the metal” than DirectX 11, it requires different settings on certain things for Nvidia and AMD cards.
Developers can’t mix and match DirectX 11 and DirectX 12. Either they commit to DirectX 12 entirely, or they shouldn’t use it.
Translation: If you're torn between DX11 and DX12, you should stick with the former
So much for DX12 being an easy and obvious win.
HW requirements, engineering time and developer skill level has gone up, but FPS has remained the same

DirectX 12 is for those who want to achieve maximum GPU and CPU performance,
but there’s a significant requirement in engineering time, as it demands developers to write code at a driver level that DirectX 11 takes care of automatically.
For that reason, it’s not for everyone.
Since it’s “closer to the metal” than DirectX 11, it requires different settings on certain things for Nvidia and AMD cards.
Developers can’t mix and match DirectX 11 and DirectX 12. Either they commit to DirectX 12 entirely, or they shouldn’t use it.
Translation: If you're torn between DX11 and DX12, you should stick with the former

Noisiv
Senior Member
Posts: 8186
Joined: 2010-11-16
Senior Member
Posts: 8186
Joined: 2010-11-16
#5245980 Posted on: 03/16/2016 11:32 AM
^^
Oh I see that Hilbert has come to the same conclusion:
I find Hitman to be a fun title, but they probably should have stuck at DX11.
The many DX12 related issues we stumbled into might be fascinating for a technology editor, but for an end-user a darn shameful experience.
I mean active framelocks that we can only disable by using 2 monitors and varying refresh rates etc ... come on.
The DX12 implementation feels rushed, for Nvidia it doesn't do even anything.
^^

I find Hitman to be a fun title, but they probably should have stuck at DX11.
The many DX12 related issues we stumbled into might be fascinating for a technology editor, but for an end-user a darn shameful experience.
I mean active framelocks that we can only disable by using 2 monitors and varying refresh rates etc ... come on.
The DX12 implementation feels rushed, for Nvidia it doesn't do even anything.
Ven0m
Senior Member
Posts: 1821
Joined: 2005-08-12
Senior Member
Posts: 1821
Joined: 2005-08-12
#5245984 Posted on: 03/16/2016 11:42 AM
First of all, thanks for the review.
I don't really get it - you can see that they recommend either 290 or 770, and 290 has 76 fps in FullHD, while 770 has 25.
Something is not right.
First of all, thanks for the review.
I don't really get it - you can see that they recommend either 290 or 770, and 290 has 76 fps in FullHD, while 770 has 25.
Something is not right.
Click here to post a comment for this news story on the message forum.
Senior Member
Posts: 2796
Joined: 2006-02-23
Well, that was expected from first crop title on a new API. I have a sense that async compute in DX12 will be abused for the same nefarious reasons, as tessellation was abused with DX11, but this time on the opposite side of the fence.
DX12 also puts many PC game developers in very untested waters, where the responsibility for the resource management now lies on their side, without the traditional "babysitting" from the device driver. Some will find it more challenging than others and it will take time and effort to master the new API. Meanwhile, DX11 will stick around for a good few years. Games can still use some of the new features in DX12 under the intermediate D3D 11_3 feature level specification, without porting to the actual DX12.
I really don't like that game developers have more control when they had less they were producing some terribly un optimised games. I see some really bad DX12 implementations ahead. I am so pleased refunds can now be had for botched DX12 only games. I agree DX11 is not going away anytime soon
My other worry is a game will be DX12 only so you cant compare how it would have played in DX11