Save bug (could be related to build item bug)
Product: The Sims 4 Platform:PC Which language are you playing the game in? English How often does the bug occur? Every time (100%) What is your current game version number? 1.98.158.1020 What e...
Forum Discussion
I just now had a new thing where I had saves that ended up being named "Scratch" even after I had originally named it. 😕
Which got me curious about what would happen if I just rename the save. Even without loading it, if I just rename it from anywhere in the game, I realized the game generates it as a new save as if I just simply loaded and used Save As. Consequently, the original save with the original name is kept, but bumped down as a recovery save, rather than just renaming the same file in the same slot.
But a rather more bizarre circumstance was going on with that.
At one point a copy of the original save I was using was roughly 122 MB in size. However, when renaming it so it does what is described above, the "new" save is now a whopping 221MB-ish!
I have archived the saves I had when I had this problem to compare, which a majority of my saves now elsewhere and not affected by the game could be looked at. Including my own save, it was typical for saves to be at +200MB, even for the backups in the same slot. I'm not sure what changed now.
Despite what should essentially be duplicates of the same save with the only difference ideally being in name, it makes no sense for it to produce this much of a discrepancy of save size.
All in all, as far as I can tell, basically the game is giving me the groundhog day effect every time I load my saves, and it appears it's because it was saving my saves that way. It's not a noticeable effect unless you know where to look. Again, newly-created, vanilla saves being loaded with mods running after the fact would produce one of the particular mods I'm fortunate to have telling me there is a problem with the save data. So I guarantee it was not infested by mods. I don't have any mods that have any special save features. As far as I'm concerned, I'm using the game's own UI, and the game is not properly saving my saves.
With that in mind, this appears to be the main source of the build item bug from my perspective.
Update:
Given the game was updated at this time that repaired the build item problem, my issue still persists in spite of it. Someone suggested to me that one of my mods, MCCC, should have it's cfg files deleted so it refreshes the settings as it helped them before, given it seems to be a clock issue (initially this made sense to me, as I deliberate turn off aging and slow down time for a more realistic gameplay). I tried this, but it was still not successful. Yes, before you ask, all related mods were updated through this whole time (I would get warnings screaming at me if I don't, so this is as current as it gets). Whatever caused the issue is still unfixed in this state as it were since the beginning of this issue.
Basically, again, my saves still somehow set me back in time (and in some respects, some objects overlap due to my progression), as well as having the original error I had from another mod along with it. I have a temporary solution for the mod error, but my main gripe is how I'm not loading the save in the state I saved it in, or that the saving process is broken in which I load it in that condition.
This may be all too familiar to people, but there are no warning alerts through either saving or loading, so the only way I can tell there's an issue is how progression is mismatched from the last time I played it. All the relevant solutions addressing the problem that I know about, or all the things that should've patched it, appear to have no effect. This leaves me wondering what specifically would be causing the issue, whether it's a file conflict or bad code. All I can tell is that no matter how many times I would try to replace the install, refresh my mods and files, I'm still having a bad time. It would be nice to know specifically what part of this is disrupting the saving or loading process instead of wasting time trying to 50/50 and refresh everything when it doesn't work.
