So, I've already explained this a bit, but basically, the issue this guide hopes to resolve for most people is the issue with key bindings always resetting. I'm not sure how widespread this is, but I've seen a lot of complaints about it, so I thought I'd share my solution.

Understanding why this happens:
The reason this happens is that as part of the patch, the developers had to add some new entries to the key bindings list for the new wingsuit etc. This is fine, except that they entered one entry into the keymap the game creates, but not into the keymap the game checks on startup. This leads to our problem. Because the game checks with a different version of the keymap, it thinks the current one is corrupt and replaces it with a fresh copy. Since the fresh copy isn't what it expects, it resets the key bindings.

So, for this step, what you'll want to do is go into Just Cause 3 and set up all of your key bindings once more. Make sure to set all of them to the ones you want to use, because it is a bit more difficult to change them afterwards. Leave your Just Cause 3 game running if you can. I don't think it is necessary, but I haven't tried, so I can't confirm it.

Once you've set up the key bindings you want, open up the save file for Just Cause 3 and open the file "kepmap.txt" without quotes. Notepad will work fine. The save folder should be located in "Documents\Square Enix\Just Cause 3\Saves\(SteamUserID)\". You might want to back up the file before the next step in case you screw something up, but it isn't required.

Now that you've opened up the kepmap.txt file, press Ctrl + F to open up the Find window. Search for "REELED_IN_RELEASE_ACTION" without the quotes. Once you've found it, delete the ENTIRE 4 lines of that entry, curly brackets and all.

Now that you have fixed the file, you can simply reload your Just Cause 3 game and you should now have working key bindings. However, do not edit your key bindings through the game, otherwise it will reset the kepmap.txt file.

In finding the entry that ruins the file, I was comparing it to the working copies of the kepmap.txt's that nestoi1-dampf03 created in this discussion thread[https//shttps].

Thank you for reading, and I hope that this guide has helped. If there is anything you think I've missed, let me know in the comments.

Honestly though, I think that it is kinda sad that the developers didn't have the courtesy to patch this when they found out about it. It's not like it is difficult, and especially for something as annoying and frustrating as this, I would think it would be a higher priority than setting up collaborations with other companies. As a hobbyist game developer, I find it astounding that they didn't rush to fix this issue when they found out about it, especially when they charge $60 for the game.

Anyways, thank you again, and I hope this has helped you!