Random Crashing
Neon:
I did some testing now with the Awesome Mod as well as without it.
Luckily I somehow managed to reproduce the crash. It seems to be not a story(making) problem, but to be triggered by user input.
I reproduced it while running with Awesome mode two times by moving around quickly, e.g. with the scroll to house or to sim (Enter and Shift + Enter) feature or by swithing the current level, and stressing the game with many left clicks (to open the pie menues).
My interpretation is that the crash occurs if some objects around are or probably rather the object at the click position itself is not yet completely loaded.
This assumption is supported by the fact that the game always lags when the crash occurs. It's like the game freezes and one or two seconds after the freeze began the game crashes.
I was not able to reproduce the crash when Aweseme Mod was disabled (i.e. no framework, no Mods dir). I tried hard for around 10 minutes in two different households. With Awesome Mod running I needed less than 5 minutes respectively.
I used the same configuration that I posted above and cleared the cache files in the user documents each time before starting the game.
The ADDRESS_VIOLATION exception mentioned in all the crash logs could somehow fit to this behavior. Are there maybe click events that access already deallocated memory when the target object is not yet or not anymore loaded?
So why does it not occur for you?
Maybe your computer needs less time for loading than mine (although I can't tell my computer is bad, it just may be that my graphics card is slightly flawed and thus needs a tad longer sometimes) or there is a different behavior because I don't have newer expansion packs like Generations or Pets.
I hope these results help you more. I'd really like to continue using the Awesome mod as it adds some fixes I don't wanna miss.
jezzer:
If Awesomemod works for everyone else but only crashes for you, then obviously there is something you have in your game that the others don't. When you said you tried taking out other "mods," did you take out ALL the custom content, or just what you considered a "mod"? Because even things like custom clothing and hair can fuck up a game and cause it to behave in unexpected ways, especially if it's something that came out before an EP changed core game behavior or was created by someone who has no idea what the fuck they are doing, or who gets sloppy with details (Rose and Peggy are both notorious for this, and yet are constantly being downloaded).
Neon:
I've no other mods, no custom content, nothing. All I did is install Sims 3 and the named expansion packs, the 1.33 patch and Awesome Mod (plus the required framework).
And if you didn't notice it yet: I'm not the thread starter so there are already two with this issue. I also found some other threads where similar problems are described.
The thing is many users here probably have much more experience with both Sims 3 in general and mods or rather the Awesome Mod in particular. I'm fine with any solution and it's not important whether it's my fault or the Mod's, I'm just trying to find out what causes the crashes so anything can be done.
It could've been e.g. that there are options of the Mod that might cause such an issue when the ingame objects stream in slowly or whatever.
I'm not here to insult any of the Mod's developers or whine about how badly it's programmed. Just looking for help and maybe it's really a bug in the Mod that occurs under rather rare conditions and if we'd find it out here the Mod could be even more improved.
Eeyore:
Quote from: Neon on 2012 June 03, 13:58:34
My interpretation is that the crash occurs if some objects around are or probably rather the object at the click position itself is not yet completely loaded.
This assumption is supported by the fact that the game always lags when the crash occurs. It's like the game freezes and one or two seconds after the freeze began the game crashes.
Perhaps this is no more than a performance issue. If you try to run the game with parameters that exceed your computer's capability then all kinds of things can get hinky. Try turning the game graphics settings all the way down, start a fresh EA neighborhood, and see what happens.
Neon:
Quote from: Eeyore on 2012 June 03, 19:46:46
Perhaps this is no more than a performance issue. If you try to run the game with parameters that exceed your computer's capability then all kinds of things can get hinky. Try turning the game graphics settings all the way down, start a fresh EA neighborhood, and see what happens.
This is not only very unlikely to be the case because I've quite good hardware, but also because the crash didn't occur before I started using the Awesome Mod again.
And since I started playing again I played more without the Awesome Mod than with it and, as I said, before I installed it there was no single crash at all and after I installed it they started happening.
I'm getting a new graphics card this week, a Geforce GTX 570, and am going to see if the crash still happens with the new graphics card. And I strongly doubt this gc isn't able to handle Sims 3 at full graphics quality settings. I even doubt my current (GTX 260) isn't as I always used to play Sims 3 at maximum and this crash never occured before.
But I'm also going to look for any driver updates (for all the hardware).
Navigation
[0] Message Index
[#] Next page
[*] Previous page