According to critics, Batman: Arkham Knight, the final game in Rocksteady’s trilogy is the finest of the lot, so there’s a great deal of anticipation and excitement in the air for its launch today. According to those already playing though, the PC version of the game is a bit of a mess. Steam’s player reviews are full of cautionary tales, warning players to wait it out.
Performance issues, graphical glitches and other problems persist. Thought the problem is apparently far worse for those sporting AMD hardware, players using NVidia’s top cards are also struggling Rocksteady seems to be aware of some of the issues, recently updating the game’s Steam page to say:
“We also want to note that there are some known issues with the performance of Batman: Arkham Knight for PC owners using AMD graphics cards. We are working closely with AMD to rectify these issues as quickly as possible and will provide updates here as they become available. We thank you for your patience in this matter.”
The newest “Game Ready” drivers from Nvidia don;t really help, and the latest AMD drivers aren’t increasing performance either.
Says one angry consumer:
“Yet another AAA title that fails actual playtesting and is shipped out to unsuspecting consumers who hoped it might not actually run like balls. Given this game runs on Unreal Engine 3, an engine pushing over 11 years old at this point, it has performance that makes GTA IV run like any Source game in comparison.
Rocksteady have in the past demonstrated great optimisation in previous titles. My old laptop, which ran a GT 555m graphics card could maintain 60 fps in Arkham Asylum on the highest settings. This game, on my GTX 970 (which is one of the top 10 best graphics cards currently on the market) can barely push 40 fps stationary, and between 5-30 whilst moving. Good thing we got that enhanced NVIDIA driver to improve our performance!
I think the worst part is that graphics wise, its not really much of an improvement over its predecessors. The post processing effects look really nice, and the rain effects are pretty gorgeous, but the overall texture and model quality just barely look better than Arkham Asylum, and that game came out NEARLY SIX YEARS AGO.
I cannot recommend this to anyone until they fix the performance issues. Also, you can tell its probably a shoddy console port because the left the 30 fps cap in the .ini file. Stay classy, Rocksteady.”
“OMFG this Pc port is so f***** bad. Unplayably high requirements and after the Intro 30 FPS cap, wtf?!”
Unfortunately, Steam is completely full of this sort of thing, as is NeoGAF with just about everybody confirming that the game is capped at 30fps on PC…if you can even hit those sorts of numbers. Thankfully there is a fix for the locked frame rate – and it’s as simple as editing a config file.
Go to the Batman: Arkham Knight folder and find the “Config” folder
e.g. C:\Program Files (x86)\Steam\steamapps\common\Batman Arkham Knight\BMGame\Config
Open the following file with a text editor like Notepad: BmSystemSettings.ini
Press CTRL+F to search, and paste the following line:
Now edit the 30.000000 value to set desired your desired FPS.
If you want to cap the game at 60FPS, the string should look like:
Save the file.
If you’re playing the game on PC, you may want to wait for a patch, lest you end up wallowing in self-pity and frustration. It’s odd, because previous versions of Rocksteady’s Batman games have performed rather damned well on a variety of hardware. It’s especially unusual given that the game is built on the rather mature Unreal Engine 3 – so what we’re looking at is a poor, poor port with a ton of issues that may or may not be caused by the implementation of Nvidia’s Gameworks tech, though that’s pure speculation on my part.
If you are having issues, here’s a wealth of workarounds to bring the game’s performance up to speed.
Last Updated: June 23, 2015
Blood Emperor Trevor
June 23, 2015 at 07:39
lol. I’m Ba..t..m..an!
June 23, 2015 at 07:44
Typical of our current industry. It’s as if not a single soul tested this game on a PC and just assumed it would work like they suspected.
Where is the QA lately?