Jump to content

False "save corruption" during gameplay


Ramagast

Recommended Posts

  • Replies 1.3k
  • Created
  • Last Reply

Top Posters In This Topic

I'm not even going to bother holding my breath for Bugthesda to have even been bothered about this issue, as I contacted lethielnyrond's Bethesda forum manager and sent him a link to my save game via dropbox and never heard back from him. I don't think he even responded to lethielnyrond after a while ... So for this issue for those of us that have it, it's never going to be fixed because that's how Bugthesda rolls. I have even seen this brought up by various console users over on the Bugthesda forums but not enough people were making a song and dance about it for any official notice from them.

Link to comment
Share on other sites

Ok, so I read through this entire thread and I only have one thing to add to the pool of knowledge atm that may or may not be useful. I have 141 mods installed with a total of 198 active esps. I have experienced zero issues. However, my friend has and identical install to mine. Exact same mods, exact same versions, exact same load order, etc. He is experiencing the save corruption issue. Wondering if that means it is (Or at least partially) a hardware thing. Also, we are both using fresh installs from mid September. Edited by HunterSike
Link to comment
Share on other sites

Hunter, are you and your friends game both installed in the default directory?

 

I have my copy of Skyrim SE installed to C:\Steam\steamapps\common\Skyrim Special Edition, I can't see why installing to a different directory would make a blind bit of a difference. If it is hardware related though why then are some Xbone and PS4 users getting the same issue!

Edited by walshy71
Link to comment
Share on other sites

Yes we are both installed to the default directory through steam. As far as the xbone and ps4 users having the issue, yeah I have no clue there. I'll keep digging though and see if I can find any differences between our games/systems. We are literally using the exact mods copied from one pc to the other.

 

Actually there is one difference in terms of our installs. He installs his steam games to a classic HD that also contains his OS. I install all of my steam games to an SSD that does not contain an OS. So perhaps there is an issue between the game and OS or I would think more likely maybe the issue is less likely to occur on SSD? It is writing a save after all so the HD diff may be a clue.

Edited by HunterSike
Link to comment
Share on other sites

Yes we are both installed to the default directory through steam. As far as the xbone and ps4 users having the issue, yeah I have no clue there. I'll keep digging though and see if I can find any differences between our games/systems. We are literally using the exact mods copied from one pc to the other.

 

Actually there is one difference in terms of our installs. He installs his steam games to a classic HD that also contains his OS. I install all of my steam games to an SSD that does not contain an OS. So perhaps there is an issue between the game and OS or I would think more likely maybe the issue is less likely to occur on SSD? It is writing a save after all so the HD diff may be a clue.

 

I was using MO2 in the past on a different HDD from my OS and I got the corruption, I now have NMM and have Steam on the same HDD as the OS and I'm still getting the issue, like I also said earlier I gave the official Bugthesda forums rep my save game, load order and DxDiag info and heard diddly squat back. This has me stumped as to what is the cause for some people and not others, when we have two sets of people on the same closed systems with the exact same hardware (PS4/XBone) reporting that they are getting the same issues as we are? For me now it isn't as much of an issue as it used to be with MO2, with MO2 I would get an hours play tops with the corruption setting in without being near a smithy/smelter/tanning rack. Now I can play for as long as I like but as soon as I start dithering about in the crafting menu for too long ... bam save file corruption.

Link to comment
Share on other sites

I am seriously at my wits end. This is by far the weirdest game bug I have ever encountered. I've read through this entire thread (made a few posts as well) and no common factor can so far be isolated to everyone who's had this issue, apart from the fact that we all use mods, naturally.

I started a new game a few days ago. Played for hours without getting the issue, hoping I was finally rid of it. Then today: bang, it hit me, and now I can only play for about one hour, if even that, before it hits. What boggles my mind so much is I have not made any changes mid game to my mods. I have changed literally nothing and yet this issue suddenly hits me on a save that has been fine for several days. How does this even work? If it's about saves being bloated, how come some people who have more mods than I do installed never get it? I just don't get this...it's like a f*#@ing curse. :sad:

Link to comment
Share on other sites

Can I ask what kind off hard drives people with the bug are writing save files too (spinning vs SSD)? What I'm thinking is perhaps with allot of mods save files get bloated then take longer to write to disk. Perhaps the standard spinning HD can't write fast enough to keep the game happy. Most PS4s and XBones seem to come standard with spinning drives, so maybe that is our common factor?
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...