just_some_guy
New Member
- Messages
- 1
I have run up to this bug recently but this isn't really a "oh mah gawd help me plox" tech support thread. I was wondering what you guys think about this bug. I have heard all sorts of different opinions, from both users and modders. Some say too many mods cause it, while others have experienced it playing the game purely vanilla.
In Skyrim, a much older game, despite filling up my game with GBs upon GBs of new content, including script heavy mods, I have never experienced this. Sure, that game has its own issues such as instability, and your save can indeed become corrupted, but despite modding that game for eight years, installing all kinds of 'bad mods' (before I became more experienced), I have never encountered an issue such as the one I'm having right now with Fallout 4, which is that after 25h or so, I just cannot save anymore (regardless of method) because the game just CTDs. I can go back to my 20h saves, but as soon as I progress far enough, regardless of the path I take in the game, the same thing starts happening. I've tried a lot of different things but honestly I don't think anything can fix your save after that's happened. Deleting older saves, not using Steam cloud, unchecking Read Only in my saves folder, and generally using common sense when modding, such as not installing bad mods, not installing too many script heavy mods, not removing mods mid playthrough, cleaning your masters, changing your load order manually (in my case, when I was using LOOT, my game was CTDing every 20 minutes, and as soon as I arranged it manually, the CTDing practically went away, but I digress) and so on.
This issue is honestly baffling to me, because going back to Skyrim, it doesn't matter how much I screwed up, I never ran up to this sort of issue. Even going as far as uninstalling a mod as script heavy as Frostfall mid playthrough, I could just use resaver and play for another 30h with no issues, provided I took some precautions first. And that game is nearly a decade old.
Since this forum has many modders, I was wondering what you guys have to say about this issue. Is it something with the engine?
In Skyrim, a much older game, despite filling up my game with GBs upon GBs of new content, including script heavy mods, I have never experienced this. Sure, that game has its own issues such as instability, and your save can indeed become corrupted, but despite modding that game for eight years, installing all kinds of 'bad mods' (before I became more experienced), I have never encountered an issue such as the one I'm having right now with Fallout 4, which is that after 25h or so, I just cannot save anymore (regardless of method) because the game just CTDs. I can go back to my 20h saves, but as soon as I progress far enough, regardless of the path I take in the game, the same thing starts happening. I've tried a lot of different things but honestly I don't think anything can fix your save after that's happened. Deleting older saves, not using Steam cloud, unchecking Read Only in my saves folder, and generally using common sense when modding, such as not installing bad mods, not installing too many script heavy mods, not removing mods mid playthrough, cleaning your masters, changing your load order manually (in my case, when I was using LOOT, my game was CTDing every 20 minutes, and as soon as I arranged it manually, the CTDing practically went away, but I digress) and so on.
This issue is honestly baffling to me, because going back to Skyrim, it doesn't matter how much I screwed up, I never ran up to this sort of issue. Even going as far as uninstalling a mod as script heavy as Frostfall mid playthrough, I could just use resaver and play for another 30h with no issues, provided I took some precautions first. And that game is nearly a decade old.
Since this forum has many modders, I was wondering what you guys have to say about this issue. Is it something with the engine?