Despite the rusting Batmobile at some points, the Rocksteady developers managed to say Batman’s goodbye to Batman flawlessly. All thanks to the powerful story moments that work better than in the previous attempts. [Issue#255]

Aside from a few sputters during the animation when entering the Batmobile and the FPS cap at 30, I didn’t experience any of the problems many PC players were experiencing with the game. If any dark, rainy, dirty and downtrodden city could be beautiful, it’s Gotham in Arkham Knight.

After four months of work, Batman: Arkham Knight comes as the masterpiece it should have been from day one.

Every positive–the twisting storyline, the iconic villains, and the superb combat–are undermined by other factors. Mediocre acting, rough dialogue, and overuse of the Batmobile, leave Batman: Arkham Knight that much less cohesive than its predecessors.

Playing as Batman? Awesome. Playing as Batman through repetitive, empty missions? Less awesome. Playing as the Batmobile? Awful.

Porting issues aside, Batman: Arkham Knight is a decent enough game. It's not the spectacular swansong we hoped for from Rocksteady, but it's another solid - if predictable - slice of Arkham gameplay, with a couple of great sections along the way.

Arkham Knight is the latest, most improved and seemingly last installment in the Arkham series. The whole, justified controversy over its failed launch on PC doesn't do this excellent game justice. We would urge any gamer to refrain from purchasing this game (retail), as there are massive performance issues, which are currently being worked on. For the time being, although the story and gameplay mechanics are splendid, we are forced to cap our rating up to 30. Just like the game's framerate.