Error codes 12 and 13 along with crashing.
Slymenstra:
I got an error 12 yesterday and was able to save around it. However as I continued to play it was very apparent my town blew up. I don't recommend trying to save around the error. The way the game saves vacations and things = major problems.
I also totally notice that I have 2 things in common when the error occurs.
1. My sim broke up with someone
2. My ram is all used up.
Sometimes it's just one or the other. I'm not going to allow an break ups for a while and I will be watching my ram and rebooting accordingly to see if that helps at all.
Anonym:
Quote from: GnatGoSplat on 2009 November 29, 20:08:04
Moral of the story is you're taking a HUGE risk trying to get past E12/13 by sending them on vacation and saving there. It may work, or it may irreparably grenade your town.
Actually, there's no huge risk if you minimize the risk by using "Save As" and changing the file name. That way, if it doesn't save properly, you can always go back to your previous save-- which is what you'd have to do anyway if you just quit after failing to save it.
Nin_the_Destroyer:
I've been playing World Adventures for about three weeks for many hours and I only got one error code 16. It just wouldn't save. So I used the "Save As" and, viola, it saved. Hopefully that's a temporary fix.
And as for the crashes. I got an fpslimiter and haven't received one crash. Don't know if the fpslimiter really fixed it though. My computer is good and I don't it was over-heating.
sewinglady:
error code 16 was fixed by an EA update...so you're playing a non-updated game...
Error code 12 continues to plague my game...generally I can have 3 saves and on the 4th save, I get error code 12...I suspect it's a memory leak (don't know whether to blame the game or windows as they both leak like sieves).
The only good I can tell you that has come from this is that I play for a much shorter period of time now - which has made my hubby extremely happy...dinner's on the table when it ought to be, etc.
chann:
I've recently gone back to playing my old save which was previously afflicted with Error 13. After installing WA to the latest version and updating my mods, I did some 'resetworld' and game-flushing voodoo, and played for a while. Eventually I found that I got an E13 only when story progression was turned on (I was using AwesomeStoryDriver). If I turned it off, I got no errors and even the save times were considerably shorter.
At first I thought Awesome was the culprit, so I tried disabling it and saving with the default story progression on, and then saving with twallan's mod active. Both error-free. I then went back to Awesome, and for some curious reason I get no E12s or E13s anymore. I'm guessing that because I clean-saved without any story progression mod active in between, I cleaned out whatever glitchiness was causing the errors. But don't take my word for it; I seriously I have no clue why my game is now working.
Navigation
[0] Message Index
[#] Next page
[*] Previous page