Corrupt (?) Savegame upon entering specific map region

[matortheeternal]

Sounds to me like you just have a corrupt save. There probably isn't an easy fix.

[Metazolid]

I'll be playing the game as usual now, avoiding this area, or rather the whole island altogether. Maybe some bad code snuck in while saving at some point and hopefully it'll be overwritten/removed on its own at some point.

[AeonsLegend]

Quicksaves are never an issue. I use them all the time, and never ever have issues.

[HeyYou]

Quicksaves are never an issue. I use them all the time, and never ever have issues.

A fair bit of it is luck of the draw. Some folks never have issues with them. I have seen others that even loading ONE quicksave, and their game is toast. I learned not to trust them playing Morrowind...... and old habits die hard. :D

[AeonsLegend]

 

Quicksaves are never an issue. I use them all the time, and never ever have issues.

A fair bit of it is luck of the draw. Some folks never have issues with them. I have seen others that even loading ONE quicksave, and their game is toast. I learned not to trust them playing Morrowind...... and old habits die hard. :D

 

Makes no sense as a quicksave is exactly the same as a regular save. The only thing it does is overwrite. If you got a bonky computer/harddrive then yea that might cause issues. In terms of what the quicksave is. There's litterally no difference with a normal save.

[HeyYou]

 

 

Quicksaves are never an issue. I use them all the time, and never ever have issues.

A fair bit of it is luck of the draw. Some folks never have issues with them. I have seen others that even loading ONE quicksave, and their game is toast. I learned not to trust them playing Morrowind...... and old habits die hard. :D

 

Makes no sense as a quicksave is exactly the same as a regular save. The only thing it does is overwrite. If you got a bonky computer/harddrive then yea that might cause issues. In terms of what the quicksave is. There's litterally no difference with a normal save.

 

Exactly. Theoretically, there shouldn't be a problem. In reality, a significant percentage of folks reported problems. Did they all have 'wonky' computers/hdds? Odds of that are pretty low. That's where the luck comes into it. If yours isn't good, you end up with problems, same as overwriting the same save file over and over again. Every previous beth game has suffered from the same problem. (well, all of them using the gamebryo engine......)

[AeonsLegend]

 

 

 

Quicksaves are never an issue. I use them all the time, and never ever have issues.

A fair bit of it is luck of the draw. Some folks never have issues with them. I have seen others that even loading ONE quicksave, and their game is toast. I learned not to trust them playing Morrowind...... and old habits die hard. :D

 

Makes no sense as a quicksave is exactly the same as a regular save. The only thing it does is overwrite. If you got a bonky computer/harddrive then yea that might cause issues. In terms of what the quicksave is. There's litterally no difference with a normal save.

 

Exactly. Theoretically, there shouldn't be a problem. In reality, a significant percentage of folks reported problems. Did they all have 'wonky' computers/hdds? Odds of that are pretty low. That's where the luck comes into it. If yours isn't good, you end up with problems, same as overwriting the same save file over and over again. Every previous beth game has suffered from the same problem. (well, all of them using the gamebryo engine......)

 

You know you're throwing inaccurate numbers at me. A significant percentage? I've never even heard of this issue until you told me about it and the topics on this bug only have a few people complaining about it. All we can do is assume, but from what I find online is that yes, it's an issue that existed witht he engine since the start, but it's not very widely spread. So that does lead me to believe that this occurs in combination with something else. This something else could be anything. From a faulty installation, to conflicting hard or software. It's definitely not really an issue from Bethesda's side if not everyone has this issue. Can they fix it? Probably yes. Are they the sole cause? Definitely not.

[Metazolid]

I'm fine with you two throwing down, but don't do that in my thread. Thanks.

[HeyYou]

I'm fine with you two throwing down, but don't do that in my thread. Thanks.

Sorry. :) We'll stop now.

 

In your case, I think about the only choice you have, is to go back to a save that actually works, and alter your save habits a bit.

 

So far as I know, there aren't any tools to "fix" savegames. There is Resaver, but, all it does is remove orphaned scripts. (I think....) You could try it, if you haven't already, not like it can make things any worse for you.

[Metazolid]

Just a small update for anyone who might run into the same issue and reads this;

I've not modified or tried to fix the bug in any way, though made sure to have a backup of my most recent dozen saves or so, just in case there is corruption that carries over to the others for some odd reason.

I kept on playing as usual, avoiding the area, I came back to it some dozen hours later and it seems to be working fine, though I must say I've played on a new PC in the meantime as well where I checked in on it.

 

tl;dr.:

 

Solution 1:

• If you notice this happening, backup your recent savegames located in Users\(YourUsername)\Documents\My Games\Fallout4 just in case.
• Avoid running into the general area for the forseeable time, I know it could suck if its a settlement or a place you frequently visit, but that's what it is.
• Check back if the game has (I guess overwritten) fixed what ever caused the issue on its own after a dozen hours of playtime.

 

Solution 2: (Not sure if that works and I doubt this will be an applicable fix for anybody but whatever)

• Build a new PC