Error codes 12 and 13 along with crashing.
J. M. Pescado:
resetworld is for emergencies ONLY. If I catch people using it as a panacea for things rather than reporting issues, I will take it away, and this is why we can't have nice things. As for sacrificing continuity, well, you give up local microcontinuity, but the macro-continuity of the neighborhood is retained (people keep relations, skills, etc., they just lose their current place in the neighborhood). As far as I can tell, though, error-12 typically indicates that
Heli:
Pescado,
I have 4 GB RAM, I have error 12 or 13 or crash to desktop.
Steele:
Quote from: Heli on 2009 October 09, 04:29:25
I have 4 GB RAM, I have error 12 or 13 or crash to desktop.
From what I gathered the game limits the allowable for each neighborhood cache at 1GB. So with more RAM you're still be limited to 1GB to play around with.
I've been thinking of copying the Sunset Valley.ObjectCache file and renaming the copy to Riverview.ObjectCache and probably also try again to bloat the dynamic caches to around 1GB then replace back the objectCache files and overstuff the whole town and see if the passive + dynamic cache stack or not.
Oh I forgot to mention, testing Jordi's resourcecachebudget setting of 90000 have improved lessening error 13s and textures and graphic details loads more faster. Just guessing that the textures and details may have been allocated to another cache.
Lorea:
Error 12 just drives me crazy! I get this error every day. I hate it!
I was looking over the net about this problem, tried everything what I could find but nothing worked.
Sometimes I get error 13, but I can solve it with nuekimpostors or Clean up all Vagrants.
But error 12 is insolvable for me.
I found these about error 12 and 13, maybe somebody can find the solution:
Quote
Error 12s are game corruptions that unfortunately writes into the cache.
Deleting the world cache files will result to a slow game start up as a new cache is being written. The game will lag and freeze as the cache is being re-written. But deleting it will only temporarily resolve Error 13s not Error 12.
It's not very clear what sort of game corruption results to Error 12. My guesses are bad sim descriptions, bugged interactions, mod incompatibilities and missing sims, bugged aging states and there are some more unidentified ones. One solution is just to continue playing and pray hard that the corruption gets overwritten. Awesomemod has an exprimental debug command that helped a player resolve the error, but personally, I have not yet tried it so I cannot recommend it for now. Quitting the game and reloading a previous save game is the most safest way right now, just save frequently every 15 minutes.
For those experiencing Error 13s it is caused by the cache being over stuffed with textures and game objects loaded. The more sims, textures and objects in your game world the more faster the cache gets overloaded and resulting to Error 13s. Turning off reflections, reducing graphics quality and removing wants on the current household or deleting unneeded lots/objects can help resolve Error 13s.
For Sunset Valley: It is located in the main folder under caches filename: Sunset Valley.objectCache (Do not delete unless you really know what to do, this cache does not regenerate once deleted. You'll have to re-install the whole game if you do)
For Riverview: It is in the save folder, World Cache, Riverview_sim.package & Riverview_object.package (Deleting this will result to game slow downs and lagging while it is being re-written back, Do not freak out when textures are all dark gray, it will eventually return to normal depending on your computer's specs.)
Error 13 is a memory problem. The game limits the cache to 1GB. So far whatever settings you do with the game it will still be at maximum of 1GB. However, if you are using Riverview, there are some reports that it can go a little bit over 1GB but not much maybe a few Mb at the most.
If your neighborhood is overpopulated with sims, very high graphics settings or lots of overstuffed, over decorated houses error 13 will not be far behind.
Every actions of sims are written in the world cache. Every texture, every object as well is written there.
Guessing by the description of Error 13 = Post Save Callback failure, it may probably mean that after saving, the game rechecks stability of the save and fails due to insufficient cache space to load the save or it's a bad save.
If you do multiple save games, you'll notice that if you have error 12 the *.bad save file will be around 40-60% of the good save file size, but if you have error 13 you'll have around 90-95% of the size of a good save file.
Steele:
Quote from: Lorea on 2009 October 09, 07:09:22
Error 12 just drives me crazy! I get this error every day. I hate it!
I was looking over the net about this problem, tried everything what I could find but nothing worked.
Sometimes I get error 13, but I can solve it with nuekimpostors or Clean up all Vagrants.
But error 12 is insolvable for me.
I found these about error 12 and 13, maybe somebody can find the solution:
Quote
Error 12s are game corruptions that unfortunately writes into the cache.
Deleting the world cache files will result to a slow game start up as a new cache is being written. The game will lag and freeze as the cache is being re-written. But deleting it will only temporarily resolve Error 13s not Error 12.
It's not very clear what sort of game corruption results to Error 12. My guesses are bad sim descriptions, bugged interactions, mod incompatibilities and missing sims, bugged aging states and there are some more unidentified ones. One solution is just to continue playing and pray hard that the corruption gets overwritten. Awesomemod has an exprimental debug command that helped a player resolve the error, but personally, I have not yet tried it so I cannot recommend it for now. Quitting the game and reloading a previous save game is the most safest way right now, just save frequently every 15 minutes.
For those experiencing Error 13s it is caused by the cache being over stuffed with textures and game objects loaded. The more sims, textures and objects in your game world the more faster the cache gets overloaded and resulting to Error 13s. Turning off reflections, reducing graphics quality and removing wants on the current household or deleting unneeded lots/objects can help resolve Error 13s.
For Sunset Valley: It is located in the main folder under caches filename: Sunset Valley.objectCache (Do not delete unless you really know what to do, this cache does not regenerate once deleted. You'll have to re-install the whole game if you do)
For Riverview: It is in the save folder, World Cache, Riverview_sim.package & Riverview_object.package (Deleting this will result to game slow downs and lagging while it is being re-written back, Do not freak out when textures are all dark gray, it will eventually return to normal depending on your computer's specs.)
Error 13 is a memory problem. The game limits the cache to 1GB. So far whatever settings you do with the game it will still be at maximum of 1GB. However, if you are using Riverview, there are some reports that it can go a little bit over 1GB but not much maybe a few Mb at the most.
If your neighborhood is overpopulated with sims, very high graphics settings or lots of overstuffed, over decorated houses error 13 will not be far behind.
Every actions of sims are written in the world cache. Every texture, every object as well is written there.
Guessing by the description of Error 13 = Post Save Callback failure, it may probably mean that after saving, the game rechecks stability of the save and fails due to insufficient cache space to load the save or it's a bad save.
If you do multiple save games, you'll notice that if you have error 12 the *.bad save file will be around 40-60% of the good save file size, but if you have error 13 you'll have around 90-95% of the size of a good save file.
Actually, that's my post over at the Sims 3 site, it's basically a summary of what I posted before. I'm still working on the error 12 and 13 problem.
My updates are a bit slow these days, I get rare error occurances after performing the debug commands I listed above. It would be helpful if you can help observe what weird and not-normal things that happen on your game. Sometimes seemingly unrelated stuff and minor bugs starts all these mess.
What I can identify right now is excessive cheating also causes the game to have this error. Setting all motives to static for a extended period causes some sim problems especially on the dreams, promises and wants department. I also found that it also affects some sim / lot description errors. Forcing the wrong opportunities via the debug interactions will also make bugged sims. Some mods and hacks when removed will also contribute. Moveobjects on unmovable graves caused many problems for me, that whenever a ghost gets spawned, I'll get error 12. (Maybe I'm just unlucky, or there is something else happening to the grave when I moved it, cannot tell right now.)
Navigation
[0] Message Index
[#] Next page
[*] Previous page