Error codes 12 and 13 along with crashing.
Steele:
From my latest tests and observations, these are the common trends that is visible in my game for the errors.
ERROR 13
There is a limit for the game where there is a maximum number sims, objects and lots allowed for the world cache. Loading the game, starting positions and conditions are loaded into the cache initially so with a high number of sims and lots will reduce allowable cache space. Every additional actions/reactions of any sim in the hood will be logged into the cache. Also textures and graphic details are also recorded into the cache. In which some players reports lower error 13 instances with lower graphics detail.
My observation is that the game only purges items and unlocked wants and other stuff that's being cleaned up during 12am and 5am (perhaps there are other cleanup times that I do not know of). So basically stuff are not deleted becomes somewhat persistant until deleted and meanwhile eats up available resources. I believe saving is also recorded into the cache since my cache timestamps reflect the time where saving is in progress. It is possible that inadequate resources causes the post-save callback error (error 13)
After re-installing, I haven't tried adjusting the resoucecachebudget if it can in place store the texture and graphic detail data to lessen the load of the cache.
ERROR 12
So far, what I can determine here is a random data bug where the game randomly allows and disallows. It's very hard to guess whether there is a number of allowable bugs or there is a certain bug that the game actively screens. The bugs can range from sim descriptions, stuck object/sim bug, missing object/sim/texture (The "?" tiles in my game is a result of a failure load in textures, somehow the game forgets the textures (especially custom textures) and just replaces it with the "?" tiles.).
In all my attempts, an error 12 often couldn't be resolved except for a re-load of the game. Somewhere between the last save and the error 12 is a event that caused it. It could also be possible of an erroneous cache writing or data overlap that is related to error 13. It often did confuse me that reseting some lots replaces the error 13s to error 12s.
Aside from playing around with the resoucecachebudget, the solution seems beyond my abilities. If someone can confirm these findings and someone with better knowledge of the codes could thinker with it perhaps we can find a better and permanent solution for this problem until the next EP or update screws it up again.
bigpooh:
After reading JM and steeles posts i may have found a work around for error 13, also it could just be a fluke.
In short, you can try what i did in the same order after the error occurs:
1) delete the .bad
2) nukeimpostors (may not be necessary, but its what i did at the time see update)
3) clear all locked and unlocked wants from the active household (based on steeles observations this would make sense at to what fixed the error)
4) save again and no more 13
Now the long version: After a pretty extensive remodeling session of one of vanilla homes i got an error 13 when trying to save. Naturally, i came here to vent (see a few posts up) I figured i might as well save the household to the bin in the event that a fix is discovered so i wouldn't lose my hours worth of work.
After quitting the game, deleting the bad saves and reading steele and JMs posts i decided to vainly play again as if the 13 hadnt occurred last night. I deleted my household and replaced it with the one i saved to the bin (even though i tried this before and it doesnt fix 13s - also the definition of insanity). Still got a 13 but i played on. My sim got phonecall from his cloned self which prompted me to do as JM said and nukeimpostors. Then for whatever reason (a stroke of brilliance, divine inspiration, acid reflux, who knows) i decided to clear all my sims wants and try saving. It worked.
I havent retested any of this because now i've yet to receive another 13. I may not be as knowledgeable on the subject of caches as others but based on steeles observation, the 13 occurs do to a cache limit being exceeded. Since wants and items are the only things ever purged from the cache i figured clearing all the wants of my active household would bring my game under the limit which was previously exceeded. Does that make sense?
Update: dug up on of my old .bad error code 13 save and tried. cleared wants and saved, got a 13. Immediately after i used Nukeimpostors and "saved as" a new name and it worked, no 13.
awwboo:
You can now add me to the list of those receiving that damn Error 12 upon save. My game was fine (with the exception of a bad CC item which has been removed) and never crashed once. I've never had any problems at all. Now all of a sudden it absolutely will not let me save. I just keep receiving error 12 over and over. I'm on Windows XP, and I have the dreaded patch.
Quote from: Nin_the_Destroyer on 2009 September 11, 04:09:01
I'm fully convinced that these errors and CTD's are caused by the file's size. (Gamesave bloating??)
I believe this to be the case as well. My saved game file is now huge. I'm going to remove some things and try the compressor on all of my downloads. Maybe that will help. If I can get the save to work again, I'll also turn on the auto-save on the Awesome Mod.
EA needs to fix this damn game. This is ridiculously frustrating.
tizerist:
This is a bit odd.
The four cache files found in Documents\Electronic Arts\The Sims 3, once deleted, have generated again at only 1 kb each.
Before they had large sizes.
Steele:
Found something new on error 12. The source of the error is also found in the cache. Something during gameplay gets corrupted and it is written in the cache. So unless the corrupted data gets refreshed/reset the error will persist and will refuse to let you load a previous saved game.
The only solution I can think of right now is someone developing an in-game cache refresh/reset command.
Quote from: bigpooh on 2009 September 25, 14:08:07
3) clear all locked and unlocked wants from the active household (based on steeles observations this would make sense at to what fixed the error)
4) save again and no more 13
So far, Bigpooh's solution works for error 13. The first 2 steps can be skipped.
Navigation
[0] Message Index
[#] Next page
[*] Previous page