Tuesday, March 26th 2019

Hitman 2 to Get DirectX 12 Renderer Through a Patch Later Today

IO Interactive announced that "Hitman 2" will receive a new DirectX 12 renderer through a patch scheduled for later today. The game launched with only DirectX 11 support unlike the 2016 reboot of the franchise that was one of the posterboys of DirectX 12, and let you choose between the two APIs. The DirectX 12 renderer is expected to be better optimized for multi-core CPUs. Hitman 2 is published by WB Games, which likely emphasized on getting all of the base game out instead of the piecemeal episodic approach of the 2016 "Hitman," making IOI focus on content over technical advancements. The DirectX 12 renderer is now being retrofitted through a 1.8-gigabyte patch. Besides DirectX 12, the March 2019 update (v2.20) includes a new location, Hantu Port (Singapore), which will unlock as a DLC, with Sniper Assassin missions. The DirectX 12 renderer can be enabled through the Advanced Settings in the game's launcher.
The change-log follows.

Game Update 2.20: What's New?
  • Hantu Port Location (Expansion Pass): The first major content drop for our Expansion Pass is a brand new Sniper Assassin map in Hantu Port, Singapore.
  • Hantu Port: We've added 7 new trophies/ achievements for the Hantu Port Sniper Assassin map.
  • Hantu Support: We've updated the menu flow for the Game Modes section, including new artwork and backgrounds for single player and multiplayer selection. Hantu Port has also been added to the Career Page.
  • Sniper Career: We've added the Himmelstein and Hantu Port locations to the Career/Statistics menu. The progression of each of the 3 rifles will be displayed (47, Stone and Knight).
Game Update 2.20: What's Changing?
  • Nul Point: We've fixed an issue that could result in a successful playthrough ending with a '0' score.
  • Static Rico: We've fixed an issue that could cause Rico Delgado to suspend his routine after the tattoo was finished.
  • Texture Fix: We've fixed an issue that could cause textures to flicker during the Three-Headed Serpent mission in Santa Fortuna.
  • Backpacker Bug: We've fixed an issue that could fail the 'Backpacker' Mission Story after placing the souvenir.
  • Shashka A33 Audio: We've fixed an issue that could cause the Shashka A33 rifle to have barely audible SFX when used by an NPC.
  • Brief Case: We've fixed an issue where 47 getting frisked with the briefcase could result in an animation where the briefcase clips through 47's legs.
  • Wrench Stash: We've fixed an issue that prevented the Handyman Wrench from being used in a 'Hidden Stash'.
  • Disco Crush: We've fixed an issue that was preventing unconscious NPC's from dying when a disco ball was dropped on them.
  • Environment Sweep: We've fixed multiple minor issues across all locations (including Legacy) relating to Environment Art.
  • Ambient Array: We've fixed various examples of ambient sound either being muted or not changing smoothly.
  • Wrench Hit: We've fixed an issue that was preventing sound effects from triggering when pacifying an NPC with a wrench.
  • Arrived: We've removed the Arrival 'location' from the Statistics page.
PC-Specific Improvements
  • DX 12: We've enabled DX 12 support for all PC players using AMD and Intel DX12 GPUs and on NVIDIA GeForce 900 series or better. This option can be toggled in the Launcher.
  • Motion Blur: We've fixed an issue where the Motion Blur setting was not working as intended.
  • Benchmark Stats: We've fixed an issue that could prevent the results of the Benchmark being generated.
  • Multiple Monitors: We've fixed an issue that could cause out-of-world environments to be visible for players using multiple monitors, or a single ultra-wide monitor.
  • Taser Shot: We've fixed an issue where the ICA Proximity Taser would not react when being shot. Now, it will trigger as expected.
  • Stretched Outfits: We've fixed an issue where outfits could become stretched on certain machines running Windows 8.1 with AMD graphics cards.
  • PiP: We've fixed an issue where the PiP camera would sometimes display shadows erratically when the 'Screenspace Shadows' option is turned on.
Add your own comment

36 Comments on Hitman 2 to Get DirectX 12 Renderer Through a Patch Later Today

#26
cucker tarlson
TheGuruStudI just meant as an nvidia sponsored game, it's obviously casualty of their "optimization". Hitman 1 was poor perf all around (I had to turn stuff down to get 60 stable on my OCed 980ti).
I still think this is mostly the in game benchmark problem.
Posted on Reply
#27
Zubasa
TheGuruStudI just meant as an nvidia sponsored game, it's obviously a casualty of their "optimization". Hitman 1 was poor perf all around (I had to turn stuff down to get 60 stable on my OCed 980ti).

This chart makes much more sense, though. Polaris does well, but Vega seems to be gimped by whatever (kinda looks like heavy throttling).
Hitman 2 is just a train wreck in terms of optimization.
Hitman 1 is actually not too bad in terms of optimizations, as for 980ti having issues in DX12, that is pretty much a Maxwell issue.
Pascal does not lose performance in DX12 and Turing actually gains performance as much as AMD does in some case.
Posted on Reply
#28
londiste
Hitman 1 was definitely a train wreck in optimizations. Hitman 1 is an AMD title, based on Hitman: Absolution engine (Dawn engine for Deus Ex: Mankind Divided was forked from the same thing) and was/is a DX12 showcase. It was patched and improved and optimized throughout its life, both on the game and drivers side of things. It took a long while to get its DX12 renderer stable and then performance was hit and miss. Early on, AMD had better DX12 performance, Nvidia had better DX11 performance. Now, both are about even - this is a heavily benchmarked game after all.

Hitman 2 did not start from scratch, it is the same engine as previous one, although obviously improved.
Vya DomusPretty sure that wasn't the case, Hitman ran faster on wide variety of hardware on DX12.
Eventually, yes. It is one of very few games where DX12 is almost universally better.

The argument that keeps being made is that a DX12 engine needs to be substantially different and incompatible with DX11 implementation. I do not see why this would have to be the case. DX12 allows some different types of things on API level and considerably lower level optimization but it does not have to change how a renderer works, just the implementation.
Posted on Reply
#29
MatGrow
Love that character. the best one.
Posted on Reply
#31
Imsochobo
cucker tarlsongreat,except there are locations where vega 64 drops below 1070 performance,under 50 fps.

lol I'm joking,I don't like hitman for more reasons than just that.
There is some rare occurrences that I have no clue why would occur, I'd say 98% of the time I'm well above 80
It's perform below what I'd expect but I love the game though.
Running undervolt, 15% pwr limit, water and 1100 mhz hbm2.

Edit: I more reacted to absymal, lower than expected is more correct I'd say :)
Posted on Reply
#33
kastriot
XuperDX12 : Vega 64 + 2700X vs 9900K+Vega 64 = 9% slower
DX11 : Vega 64 + 2700X vs 9900K+Vega 64 = 43% slower

unbelievable !
We are not talking about "A"vs"B" here just about boost in ryzen cpu with DX12 in comparision with DX11 yes?
Posted on Reply
#34
cucker tarlson
gtx 1080 dx11 beats amd's v64 dx12 by 10%.
what is amazing is how inconsistent v64 perfromance is.
in all honesty,it should already have left gtx1080 in the dust,it's been almost 2 years since launch.
hard to assess 2700x vs 9900k performance here,though 2700x is where it should be,pushing a V64 card nicely at 1080p.
but V64 is lower than 1080 here,and 1080 is 2060 by today's standards.
Posted on Reply
#35
Xuper
kastriotWe are not talking about "A"vs"B" here just about boost in ryzen cpu with DX12 in comparision with DX11 yes?
DX 11 : GTX 1080 + Ryzen 2700 vs GTX 1080 + 9900K : 45%
DX 12 : GTX 1080 + Ryzen 2700 vs GTX 1080 + 9900K : 8%

See pattern ?
Intel + nvidia = DX11
Ryzen + nvidia = DX12
Now next Ryzen 3000 should fix it.
I find it funny when you look at GTX 1080 + 9900K in both DX12,11 ( 99th test) , different is 48% with 7% different fps.

Edit: Both CPU test not GPU Test
Posted on Reply
#36
Vayra86
FordGT90ConceptD3D11 and D3D12 are effectively forks. To do D3D12 right, the D3D11 code is pretty much worthless. The D3D12 implementation in these cases (like The Division) is often underwhelming. I don't know that we've actually seen a pure-bred D3D12 game yet.
An API is a means, not a goal. I think its a simple matter of economy. There is too little profit in spending dev time on it, at least at launch, and also at a basic level.

When MS launched DX12 my main point about it actually was that its purpose was to drive new types of content on smaller/mobile devices and for example things like VR. It offers great support for efficient use of many core CPUs, that can run at lower clocks to compete. Thát is an economical incentive. You want to lower the bar in terms of hardware requirements.
Posted on Reply
Add your own comment
Nov 19th, 2026 12:04 CST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts