Random Crashing
vorpal:
Since 1.33 I've been having the same. Random crashes with Story Mode on, on two different computers, and CLA identifying them as corrupt saves. I turned StoryMode off and no crashes at all. For the whole period of patch 1.34 I had played either without any story progression or with twallan's SP and didn't crash a single time. Shortly before updating to 1.36 I tried a new game with AwesomeStoryDriver on (AM version from 06/18) and within one Simweek I had a total lockup of my machine again and had to use the power button to turn it off. I then disabled StoryDriver again an not a single crash or even hiccup after that. I haven't tried with 1.36 yet and have continued with either no SP or twallan's, crash-free, with the longest playsession probably being something around 11 hours.
My mods are in Documents, there is no chance of any remnants of the old framework in Program files, as it's a new computer and a fresh install. The only thing where the installation on the new computer differs from a default install is that both the game and the user files are not on the system drive and the page file has been relocated to that other drive, too. But the other computer has a default install and the crashes were the same. The new computer exceeds the system reqs by far with an i7 3440 clocked at 3.4 GHz, 8GB of RAM and a 570 GTX GPU and there are 1.75 TB of free space on the harddrive.
I still suspect that it's the skilling system that causes the game to crash but it's hard to narrow down on it as on reloading a crashed save many actions seem to get dropped. In the last test run I began to save whenever I got a notice of an inactive skilling and wrote its name down. Reloading the crashed save and making the Sim active only showed it as being idly standing in its home.
My uneducated guess is that there has been a change on how the game handles low detail mode on inactives as their skill record doesn't change unless one of my actives is near them and that the AM skilling systems produces a conflict then. I noticed this change especially in a test I did yesterday:
One of my Sims has an illegitimate child in another household. When this child aged up to toddler, my Sim rolled all three wishes for teaching to talk, walk and potty training. In the past I usually did not teach the toddler myself but made the other household active and ordered the mother to teach her child and switched back to my own household. This had always allowed me to control the toddler's progress because the wish was fulfilled as soon as the mother succeeded, even with both of them at the other end of the map. This time, however, it did not work. After almost the whole day the wish did not fulfill. I then sent a household animal over to fool around in the other household's front yard, hoping that this would draw the others into more high detail mode, but no dice. At the end of the day I sent my Sim and the moment he stepped over the lot's border the wish was fulfilled. This must be rather new, because, as I said, in the past this method had always worked.
J. M. Pescado:
I cannot think of any particularly logical reason why Story Mode would crash, since it is purely C# code and involves no potentially unstable MSIL codes at all. All of it is fairly generic and benign, with very few actual actions taken during it. It's distinctly possible that something about your neighborhood is choking the entire computer under the higher activity that StoryMode tends to cause, as more sims start moving about.
vorpal:
So far I've had it in two custom worlds (Setra and Grey Meadow), one Store world (Lunar Lakes) and three EA worlds (Sunset Valley, Appaloosa Plains and Starlight Shores), playing either with my own or pre-made Sims. The way it happens is always the same: first the sound stops for a split second, then it comes back for a split second then it stops completely and the game crashes. The older computer crashes to desktop with "The Sims has stopped working etc. etc." the new one locks up completely.
I can't say anything more, as I haven't tested it with 1.36 so far.
Shadownet:
I played around on Nraas story progression on a new neighborhood and it seemed to be stable after playing for an extended period of time. I checked back on one of the saves that crashed with AM SP and it seemed to be fine, but at that point I didn't have time to play it longer to see if crashes are actually gone for good. Still, I'm fairly sure the problem wasn't corruption, but rather a performance issue.
I guess Awesomemod's SP is working as intended, and I'll just have to get used to using Nraas SP. I'm just glad the bug fixes and features in AM aren't the cause of the crashes.
J. M. Pescado:
If you really believe Story Progression is responsible, the only answer I can think of is that a corrupt sim is somehow causing it: Since AwesomeStory actually performs visible actions rather than just invisible, unstoppable handwaves for everything, causing a damaged sim to become visible may result in the game seizing and dying, particularly if it has gotten to some invalid state that would ordinarily just cause it to die slowly in a puddle of its own piss in some forgotten corner of the world.
You could always thus resolve the matter by rapturing the neighborhood. Switching Story Engines/Turning off SP are just putting bandaids on a chest wound: The neighborhood still has something WRONG with it that will just bite you at some other point. When things like this happen, you have to take off and nuke the entire site from orbit. It's the only way to be sure.
Navigation
[0] Message Index
[*] Previous page