That stupid "game freezes but effects and sounds keep going" problem, again.
cassblonde:
I've had the game lock up on me as well and actually searched and found the "exit stage left" thread - next time it happens I will try to see if a quick pause and resetworld will help. Otherwise I just set Awesome Mod to autosave for me so I don't lose a lot of game play. Next time it freezes I will give it a bit more time as I thought that the program hung and I was SOL.
J. M. Pescado:
Quote from: Claeric on 2010 April 27, 20:15:02
Well, I have a sim I suspect may cause it (after I used resetworld, it told me a sim from a previously played household had an error and his "work and school crap" supreme commander interaction needed to be re-queued. Re-queueing it didn't make it freeze again, but that may have been it.
That's just the message you get anytime the game detects that the command got aborted due to a world reset, and gives you a little popup so you can click it to requeue it. It's not the cause. It's useful for when a heavily commandered neighborhood gets reset as a result of a patch.
lordrichter:
Uh. If you have Sims running Supreme Commander in the background, I think they are running in high resolution mode.
It seems to me that could contribute to a lag or freeze problem.
cannedsarcasm:
I've experienced this some time in the past, but I've also experienced this recently in my own game - a freshly started game in Sunset Valley after 2 months of not playing.
On two occasions it's frozen on me, once upon arriving at the Graveyard (one sim household) and once before a toddler's birthday. It is a permanent freeze, the game does not pick up again. The trees still rustle, the water and fish still animate, but the sims, puck and all controls are dead.
It's in a neighbourhood that has not yet had Supreme Commander applied, or even a switch to a new active household, so lordrichter: I don't think there's a correlation there at all. I suspect the sim herself is corrupted somehow.
I've also had a similar kind of permanent freeze occur in that family midway through teaching a toddler how to talk. The parent and toddler become completely frozen, though the surrounding world is still active and alive. I cannot recall whether it affected all members of the household, I don't believe that it did. This freeze has occurred at least twice previously in other families on different save files. I quit without saving, so no suggested fix from me. I did try switching to a different household and evicting the frozen ones. They were then moved back into that lot. The mother sim and the frozen toddler were both there, but the toddler's twin had vanished from the family. Still on the family tree, but otherwise gone. Really fracking annoying, since it was a ghost toddler and I wanted to keep it. I've had other sims drop from families before (again, in other files), so I don't think it's by virtue of being a ghost or otherwise related to one.
lordrichter:
The only correlation between the freeze and Supreme Commander is that SC is often a victim of this same bug. SC does not cause this. Finding a Sim using SC that is blocked or looping is merely a means to check for an easily identified condition that can be easily corrected. Unless the underlying situation that caused the problem is identified and fixed, something that is not always easy to do, it will likely happen again. A freeze not caused because SC is looping is merely harder to find.
I also want to be clear that SC looping does not seem to cause a freeze unless the attempted action is one that will cause an actual long delay in the game. If SC is blocked because a Gnome has moved to block Sim access to the refrigerator, the game does not freeze. Instead, the symptom is jerky Sims animation that is best described as "on and off" action by the Sims, who behave in a move, stop, move, stop manner.
Because blocked routes can cause game lags, it is not unreasonable to theorize that routing calculations that get out of hand can cause more serious performance issues, like freezes.
Not all freezes need to be caused by the same thing. A freeze of any noticeable length is merely a symptom of something going wrong, namely some part of the game going off to do some work and never returning, or taking an extreme amount of time to return. There is no rule of programming that says that this can only happen in one place or for one reason.
Navigation
[0] Message Index
[*] Previous page