A first of what will no doubt be quite a few patches for the PC version of Batman: Arkham Knight has been released today, apparently adding the missing Ambient Occlusion and rain effects.
The patch is detailed on the WB Games community site, along with an outline for future patches. Quite a few of these plans involve variations on the theme of ‘We’ll actually give you a graphics menu option to toggle this on and off, sorry.’
But before we get into future hypotheticals, here’s what’s actually in this Batman: Arkham Knight patch:
– Fixed a crash that was happening for some users when exiting the game.
– Fixed a bug which disabled rain effects and ambient occlusion. We are actively looking into fixing other bugs to improve this further.
– Corrected an issue that was causing Steam to re-download the game when verifying the integrity of the game cache through the Steam client.
– Fixed a bug that caused the game to crash when turning off Motion Blur in BmSystemSettings.ini. A future patch will enable this in the graphics settings menu.
Some pretty solid fixes there, if they are indeed fixed. Especially the absurd cache verification thing. So, what of the future? Well, here’s what they say they’re working on next:
– Support for frame rates above 30FPS in the graphics settings menu.
– Fix for low resolution texture bug.
– Improve overall performance and framerate hitches.
– Add more options to the graphics settings menu.
– Improvements to hard drive streaming and hitches.
– Address full screen rendering bug on gaming laptop.
– Improvements to system memory and VRAM usage.
– NVIDIA SLI bug fixes.
– Enabling AMD Crossfire.
– NVIDIA and AMD updated drivers.
The rest of the major problems, basically. Though no timeline is given for these other fixes, it sounds like they could potentially take a while: “The work is significant and while we are making good progress on improving performance, it will take some time to ensure that we get the right fixes in place.”
Maybe this could’ve been sorted out for release day instead of weeks afterwards, eh?