Save function not retaining game progress
Soltis:
I haven't ever marked anything as 'read only', although I just looked and saw all the save *folders* are marked read-only. The files inside them are not, though. Since this is true of every save I have going back several weeks, I can't imagine it being related; presumably TS3 does this when it creates the folder.
PA:
Did you have the Sims 3 documents folder open on the desktop when you were trying to save? Not sure that would have allowed for a new time-stamp on a save without new information being created, but it does occasionally cause errors with saves loading. Stands to reason it might cause errors in saves saving.
Soltis:
I don't think I did; however, I used to keep an explorer window pointed at the TS3 documents folder all the time while testing mods and never had any issues saving or loading.
Anyway, if that were the case, then the save C wouldn't have the sims in their 'reset' positions. If all three saves were identical, I'd simply chalk it up to some weird save-copying glitch, but since the sims actually did reset, that makes this a whole lot weirder -- since the game somehow reset the sims & objects in the game, but managed to drop all new objects and changes to crafting tallies, etc. at the same time.
Whatever this problem is, it's relatively new -- I played quite a lot of TS3 around the time LN came out, and again shortly after Pets, but it never happened then. Now it's happened to me at LEAST twice inside a week.
wizard_merlin:
Are you trying new games/saves or an old save/game? It is possible that the game could be corrupt, therefore the problem with saving.
Soltis:
Quote from: wizard_merlin on 2012 December 21, 16:51:39
Are you trying new games/saves or an old save/game? It is possible that the game could be corrupt, therefore the problem with saving.
The issue isn't consistently repeatable; it happened once, and again around a week later, which means that failing to observe it happen, after reinstalling or starting a new game, wouldn't immediately be any proof that the issue was corrected. I'll go ahead and do a full wipe/reinstall, just to get started, but it would take upwards of a month of continuous playing without a repeat of the incident, before I would be satisfied that the issue was 'fixed'.
In the mean time, I would like to know what kind of testing, etc. can be done to determine what in the world is going on, assuming that it continues to happen after the reinstall.
Navigation
[0] Message Index
[*] Previous page