Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
01. Backwind to a previous save point. From the save slot menu:
Keyboard and Mouse: Hold down minus key (-) to display backups, tap minus once or twice to choose between two recent backups, then press Enter to select.
XBox Controller: Hold down Left Bumper (above Left Trigger), tap Left Bumper once or twice to choose between two recent backups, then press green A button to select.
If that doesn't place you back far enough in time, follow these instructions to access backups from the Documents folder:
02. Reload a previous save.
Locate your backup folder, typically found here:
Documents \ WB Games \ Batman Arkham Knight \ Steam Account Number \ SaveData \ backup
You can drop Backup saves onto a slot in the Remote folder with existing progress to overwrite them. On Windows 8.1 you can't drop Backup saves into an empty save slot in the Remote folder listed below because swapped saves need an existing save to overwrite; however, you can or should be able to if you use newer versions of Windows 10. Your main game saves will be here:
Steam / userdata / Steam User Number / 208650 / remote
Arkham Knight's save system has up to 3 .sgd files per save slot which read as follows:
First save slot: BAK1Save0x0.sgd, BAK1Save0x1.sgd, BAK1Save0x2.sgd
Second save slot: BAK1Save1x0.sgd, BAK1Save1x1.sgd, BAK1Save1x2.sgd
Third save slot: BAK1Save2x0.sgd, BAK1Save2x1.sgd, BAK1Save2x2.sgd
Fourth save slot: BAK1Save3x0.sgd, BAK1Save3x1.sgd, BAK1Save3x2.sgd
If you use the Backup saves make certain to edit the datestamps from the .sgd file names before dropping them into the Remote folder. For example, edit from this:
BAK1Save0x0.sgd_2017-08-10_13-03-11
To this:
BAK1Save0x0.sgd
Make copies of both your current Remote saves and of any Backup saves you want to swap them with, that way you won't lose any major progress.
I already found out that new game+ wont fix this either, since it uses the same data as the regular game and keep them off. It really sucks because I know this glitch has been in existance since 2015 and there has been nothing done to fix it. Perhaps you know of a debug/console mode or a mod that can fix this? I have been looking around for that too and couldnt find any. I completed everything else, so I dont even care if it messes up the gameplay at this point. I just want to finish the game with everything at 100%.
The thing is, as far as I could deduct, the reason they wont work is because at some point in the game, I accidentally must have hit one of the pressure plates while being mid-chase, which activated the bomb rioter while being inside another quest, tagging the quest as finished even though I didnt finish the objective. One of the bomb rioters is actually marked as finished, which should unlock a voice recording because the entire grid is checked off, but even the voice recording stays locked. My guess is that the issue lies there. Since I am able to take down the bomb rioters of Founders and Miagani Island, and the first bomb rioter being completed but somehow doesnt count to unlock the voice recording, I think the best way is to somehow be able to reset that objective, through hacking, mods or any other way of gameplay manipulation. Especially seeing as I did the first bomb rioter within the first 3 hours of gameplay and I am right now at about 30-40 hours in.
I am pretty sure that if they would allow a console in the Arkham games, problems like this would be solvable within seconds.
This bug was purportedly patched a long time ago. Have you guys checked to make certain the game auto-updates?
1. Select game in Steam Library, right-click Properties, then Updates to choose Automatic Updating and to Allow Background Downloads.
2. Select game in Steam Library, right-click Properties, then Local Files and Verify Integrity of Game Cache.
I keep reading it was patched, but it seems still still be a triggerable event. What's weird is that the scan bug happened and I wasn't even near where the pressure pad would be, since it is on the complete other side of that whole road, so I am doubly confused how it happened. But yeah, I downloaded the game with full blown DLC and everything in late 2018, so it should have been fully patched from when I started it.