Batman: Arkham City Patched On PC

Tweet

Even though Rocksteady was given a month of extra time to iron out the kinks in the PC version of Batman: Arkham City, it was still delivered with a pretty major issue. When Batman: Arkham City released last month on PC, players discovered that there were some major issues when trying to run the game with DirectX 11.

So, DirectX 11 didn’t work on Batman: Arkham City. Big deal, right? Well, considering NVIDIA, Rocksteady, and Warner Bros. pimped the hell out of Batman: Arkham City‘s DirectX 11 support, I’d say it’s a pretty big deal for those who decided to wait for the PC release. Those wanting to push the game to its graphical limits have been, understandably, disappointed that they’ve had to play Arkham City with DirectX 9 since launch.

Well, Rocksteady finally released a patch for the PC version of Arkham City today, and it fixes all of those issues with DirectX 11… so long as you’re playing with a 64 bit operating system. There’s no fix for the 32 bit version of Windows 7 and Windows Vista in this patch, with Rocksteady saying that a special patch is on the way for those with a 32 bit OS. Here’s Rocksteady’s fix list in full:

• Performance / hitching issues have been greatly improved for running in DX 11.
• An issue with players running out of Video Memory or encountering a Rendering Thread Exceptions has been address. This was primarily affecting 32-bit Operating Systems.
• A progression block after defeating Ra’s Al Ghul has been fixed. This was issue occurred primarily on lower end computer setups and described as Batman not readying his Reverse Batarang.
• A crash that occurred when scrolling between the Character Bios and Arkham City Stories has been fixed.
• A crash that occurred when selecting “Press Start” immediately when available at the Title Screen has been fixed. The issue was described as crashing/hard locking around the DLC (Downloadable Content) check.

So there you go, you can finally play Batman: Arkham City with DirectX 11. I’m glad that Rocksteady finally released a fix for the issue, but like I said when the issue was initially discovered, it really makes you wonder what Rocksteady was doing for that month the PC version was delayed. Of course, my theory is that Warner Bros. delayed it simply to nab more console sales, but I suppose that borders along the lines of a video game conspiracy (if such a thing exists).

What do you think? Have you been holding off on Batman: Arkham City while you wait for Rocksteady’s DirectX 11 patch, or did you play through it with DirectX 9? Head down to the comments section and let us know!