Hitman 2 PC Performance Review

Hitman 2 PC Performance Review

Introduction – A Return to the World of Assassination

The release of Hitman in 2016 was a controversial one, moving away from traditional monetization models to make way for an episodic format, a move which would ultimately prove to be a misstep for the franchise.

While I won’t deny that I enjoyed my time with Hitman 2016, I cannot deny how disappointed I was that the game’s content was delivered in such small chunks, preventing potential binge sessions by locking down players to what was often single levels at a time. 

As a game, Hitman had its issues, but its PC version was a strong offering, complete with plenty of graphical options and a respectable DirectX 12 implementation, but with Hitman 2 a lot of things have changed, the biggest of which being the game’s publisher. IO Interactive has moved away from Square Enix and has fought tooth and nail to retain the Hitman IP, a change that has left the studio with a lower budget. 

On PC Hitman 2 has had to make a few sacrifices to make it to market, with the came lacking the benchmarking mode that the 2016 version championed while also offering a more restrictive graphical options menu, dropping DirectX 12 entirely to go all-in on DirectX 11. 

In this overview, we will look at how Hitman 2 performs and see how easy (or difficult) it is to get this game running at high framerates. Will Hitman 2 be a stellar sequel or has Agent 47’s bald head lost its high-performance shine? 
   

Hitman 2 PC Performance Review  

Uh-oh! It looks like you're using an ad blocker.

OC3D relies on ads to provide free content and sustain our operations. By white listing us on your ad blocker, you help support us and ensure we can continue offering valuable content without any cost to you. We only run our own hand picked ads from Industry brands like MSI, BeQuiet, Sapphire and PC-Specialist - meaning they are all relevent to the content you are reading.

We truly appreciate your understanding and support. Thank you for considering whitelisting OC3D