The home world file is now 162MB and TravelDB.package is now 154MB. This is the savegame after they came back home. Most noticeably, the TravelDB.package is now 106MB This is the savegame after they arrived in Shang Simla. Notice the home world file is 89.7MB and TravelDB.package is 56.2MB. This is the savegame before I sent my sims to Shang Simla. This causes their memory snapshots, camera photos, still life and portrait paintings within their inventories, to be copied. The original sims will be replaced by these clones. When you send them back home, the arrivals will be 'clones of clones'. So my theory is, if you send your sims travelling, when they arrive they are not the original sims from their home world but clones of them. As for the old ones, the game will not delete them but will keep them in the savegame. The game will use the new copies as the resources to display on your screen. Also, if you've ever sent your Sims travelling, not only are memory snapshots copied but camera photos, still life and portrait paintings within their inventories, are copied as well. As for those unused snapshots, the game will keep them in the savegame as garbage. Sometimes, it takes multiple snapshots for a single event but only one of these snapshots is used. I found out this new feature and EA's stupid savegame mechanism to be the cause of this madness.ĭuring my experiment, the coding for taking the memory snapshot, seemed a bit buggy. More seriously, some players' games are starting to Crash To Desktop (CTD) due to insufficient RAM. At the same time, a lot of players are starting to have Error 12's while saving. For active sims, if they are on the currently active lot while something happens, the game will take a snapshot of the memory.

Since The Sims 3 Generations, base game patch 1.22, memories returned as part of this patch.

Sims 3 taking forever to save