The saves stop loading

[foxxxy]

Greetings to all. There was a puzzling problem (I mean, already broke my head), can anyone help?The bottom line is that up to a certain time of passing the game - in my case, 70d 13 h for a save-there are no problems with saves, they load normally.As soon as I pass this damned time, saves stop loading (there is an infinite loading). All earlier saves are still loaded normally.Two times I rolled back to earlier saves, on 69d and on 70d 3 hours, everything went great until the ill-fated time of 70d 13h, then the saves stop loading, while I do not put any new mods,I even took a few suspicious ones. Save 70d 12h 53m is loaded normally, and 70d 13h 10m and all subsequent ones are no longer there.What the hell, I'm sick of it. Please, if anyone can help, help!! SOS!!!

[LucidLady]

I don't think I can be much help here, but i'll go ahead and suggest that you try loading your save twice.

What I mean is, when you start the game and load up whatever save file you're gonna load up - load that save up again.

The reasoning behind this is that, if your character has a bad script stuck on it, loading the save twice will help shake it off.

I personally have started loading saves every time I make a new save. Only takes a sec, doesn't hurt anything as far as I can tell.

 

Also, I suggest you install the CTD-log tool Buffout 4.

Here's the link - https://www.nexusmods.com/fallout4/mods/47359

It gives you a crash log whenever your game CTDs.

Once you generate a crash log, post it on that page or in this thread, i'll take a look-see.

- - - - Also, post your load order (IN A SPOILER BOX) for good measure. And tell me what mod organizer you're using. Do you use LOOT?

It's not too hard to figure out what the problematic plugin might be using the crash log.

Just earlier tonight, I was having a terrible CTD-on-load issue that i've never had before.

I looked at the log, saw that it kept mentioning the Crafting Framework mod.

I've had Crafting Framework installed for... a year? Haven't changed it. Hadn't altered it in any way since the last time I played. So why was I suddenly CTDing because of it?

I just re-installed that mod and voila - problem solved. It would have taken absolutely AGES to figure that out without the crash log. Dunno why it was suddenly borked, but it doesn't matter. Everything's back to bein' groovy now.

One of your mods might be acting up in a similar way. Something you've probably had installed for ages, suddenly borked for no apparent reason.

 

Now, you say that you're getting an infinite loading screen. That means you won't actually get a Crash Log from Buffout4, because it's not a CTD.

But, Buffout4 does come with code that helps prevent CTDs and other engine flaws, so it won't hurt to install regardless.

I've been getting some infinite load screen problems lately too, actually. Something I never ever had a problem with before this last week. But for me it's centered on very specific locations. Only 2 that i've found so far. Both of which are mod-added locations.

 

Another thing you can do is download ReSaver.

Load your problematic save up into it, and tell me how many Unattached Instances there are.

It's super easy to do, the program is very light. Just look at the buttons at the top of the ReSaver screen, click "Clean", and then click "Unattached Instances" and it'll show you only that.

It's normal to have a few. But if you have anywhere near 1oo, then something has gone horribly wrong.

Just knowing if you have a ton of unattached instances could help narrow the problem down.

Another thing that ReSaver will do is tell you how many Active Scripts are running on the save. To see that just look at the list of expandable items that get shown when you load the save up into ReSaver. One says "Active Scripts".

If your problem is a bad script, look at that list, and disable all the mods that are responsible for each one. That'll narrow down whether it is a script problem or not.

I wouldn't recommend actually cleaning your save with ReSaver. It tends to break the save rather than fix it. It is simply a good diagnostic tool.

Same goes for LOOT - terrible at organizing your load order if you've got anywhere near 1oo mods installed, but still very handy at diagnosing dirty mods that need cleaning.

If you've got FO4Edit Quick Auto Clean setup, cleaning any dirty mods that appear in LOOT is as easy as loading the plugin up, waiting for the program to clean it automatically, and then closing the program. That's it lol.

[LarannKiar]

It's called the "Infinite Loading Screen" issue..

 

What's the size of your Save file? Above 40MB?

 

How often do you uninstall mods? Do you use a lot of mods? Especially "big mods" (like Sim Settlements?)

 

You can try "Load Accelerator".. (Especially if you're using an SSD).

[Drivinghard]

It's called the "Infinite Loading Screen" issue..

 

What's the size of your Save file? Above 40MB?

 

How often do you uninstall mods? Do you use a lot of mods? Especially "big mods" (like Sim Settlements?)

 

You can try "Load Accelerator".. (Especially if you're using an SSD).

Is there allegedly, or factually a Save File Size limit? you mention 40 mb .. but I can't imagine anyone with a 2 or 3 year old paythrough NOT having a save file higher than that... with a save file size teetering just under 60 megabytes right now going onto my 3rd year of this paythrough.. once the game save file loads there is relatively zero performance differences or playing differences .. the exceptions being of course if you have done lots of building in a heavily built up and/or modded loacation or area..

[LarannKiar]

 

It's called the "Infinite Loading Screen" issue..

 

What's the size of your Save file? Above 40MB?

 

How often do you uninstall mods? Do you use a lot of mods? Especially "big mods" (like Sim Settlements?)

 

You can try "Load Accelerator".. (Especially if you're using an SSD).

Is there allegedly, or factually a Save File Size limit? you mention 40 mb .. but I can't imagine anyone with a 2 or 3 year old paythrough NOT having a save file higher than that... with a save file size teetering just under 60 megabytes right now going onto my 3rd year of this paythrough.. once the game save file loads there is relatively zero performance differences or playing differences .. the exceptions being of course if you have done lots of building in a heavily built up and/or modded loacation or area..

 

None that I know of. A save game's file size alone can't indicate problems (except absurdly large save sizes like 150MB+) but it depends on the player's mod and DLC lists. After 70 days of playing a 40MB save isn't considered to be large.

 

As far as I know, corrupted saves can cause infinite loading screen.