AWESOMEMOD & SCRIPT HACKS: CRASH ISSUES THREAD

[joshiejack]

I also did not have any issues before the current version and am facing the crash error.
Gonna go and play without awesomemod now . (Temporarily of course )

Lilith same for me too

[Lissa]

I can confirm that the latest version "build 6/11/09 11:16 AM", crashes the game at loading screen for me.

Ditto

[Lorea]

I tried the newest one too, I could play with it for 1 hour and it managed with two saving and it crashed during the third saving.

[Plu]

See, he gets us all hooked, gives us some half-assed excuses about older versions being evil, and then screws up one update and leaves us in the lurch like this. One is almost tempted to wonder if he enjoys causing anguish...

Yeah mine crashes also.

[wknplaya]

If you're experiencing crashes with the new version, clear the cache file and remove "enablescripterror.package". That seemed to have stopped the on-load crashing for me.

Cheers.

[J. M. Pescado]

Does the game always crash when you're on the second "ray" of the loading star? That's the "Random Crash". It seems to be fixed simply by randomly kicking the game and is not directly associated with AwesomeMod.

[wknplaya]

Does the game always crash when you're on the second "ray" of the loading star? That's the "Random Crash". It seems to be fixed simply by randomly kicking the game and is not directly associated with AwesomeMod.

It happened that way when I had the scripterror package in, it seems to load just fine now. In addition to that the game never crashed before the awesome mod or with the previous version.
 

[J. M. Pescado]

It is a random behavior and not affected by anything you specifically did or didn't do, it's just Old Car Syndrome.

[farmersimmer]

See, he gets us all hooked, gives us some half-assed excuses about older versions being evil, and then screws up one update and leaves us in the lurch like this. One is almost tempted to wonder if he enjoys causing anguish...

Yeah mine crashes also.

Mine also CTD -during loading on the second time going to play using AwsomeMod?
I haven't yet tried by deleting caches.But I did take Awemod out and game loads ok,there is still a lone sim in that world,but can start a new game
which has all the population ungassed?
Im thankful and don't care how much änguish is caused.
 Pescado ïs a genius getting this far,so soon!
Heed the warning "Your computer may blow up" we are only the pesantry in the grand scheme to Mod Awesomeness.

[Antiscient]

Right now, completely reliably, the newest version of AwesomeMod crashes my game on the second ray of the loading screen. Removal of AwesomeMod results in a successful load. However.. it's not AwesomeMod, it's my aweconf file, which I updated along with the mod. Removal of that also lets the game load. I'm about to make another aweconf package using the configuration tool and see if just remaking it works. My custom options were turning the good sliders on and turning off the anti-age-up-swarm.

Edit2: Removed invalid conclusion.

[J. M. Pescado]

It's not really that, either. It's some kind of bizarre disk race condition built into the core of the program. Doing anything from thumping the computer to deleting random files or rebooting can make it go away.

[Kralore]

Removing aweconf.package fixed the crash problem for me. This was a newly generated copy when newest awesomemod was installed.  This is the only time I've had the game crash with awesomemod in.

Edit:  I should also mention that I can leave aweconf.package in, but I need to delete the cache files before starting the game each time.

[Antiscient]

Isn't it usually inconsistent, though? It was consistently crashing for me, over 30 times and regardless of caches. And I found a definite on/off switch for my case in the 4x slider option. I don't see why that would have changed between releases though, in the mod or in the config tool.

I'm not saying it's anyone else's problem, but it does appear to be my problem.

Edit: I take it back. That wasn't the problem. Whatever it was, what fixed it was actually running it without the aweconf file and then running it with the aweconf file. ...Whatever. It's running now.

[IAmTheRad]

Technicallly if it crashes at the same place all the time it's no longer random. It's a mystery crash then.

[rosenshyne]

aweconf.package with the latest version of awesomemod caused my game to crash at the loading screen, removing it fixed the problem.

[Kralore]

I originally started to post this to report that my game was crashing no matter what I did. But I decided to try one more thing, and this may be a solution.   I removed the mod setup completely. Deleted the mods folder, resource.cfg, and the d3dx9_31.dll. I then loaded my game up, saved it, quit, then put the mod setup all back in again.  If a new build of awesomemod hasn't been posted in the last hour then this worked for me with the current build available.

I do have a question though. Will this have any detrimental effect with an ongoing game to remove the mod completely, save, then put the mod back in?

Edit:  No crashing first time I loaded after putting awesomemod back in. But the game is still crashing. It seems to be random now though.  Sometimes it will load without crashing whether I delete the cache files or not. Other times it won't load until I delete the cache files.

[J. M. Pescado]

Try the magic of rebooting Windoze if it doesn't work.

[Cheencheela]

Blasted... I installed the most recent version of Awesomemod, and I too am getting the Crash-to-desktop on load.


I'm going to try and reinstall the Framework. I'll give you an update if it worked or not.

[Riez Forester]

The most recent version with aweconf.package crashes on me as well. Doesnt without it.

The reason that I 'upgrade' to this version is because the old ones keep making Mortimer and Bella changing chairs when they are idle. As if theres nothing else they should do.

They'll sit on chair A. Then they'll stand up, and change to chair B. Then back to chair A. Back to chair B. Sometimes, go to chair C. Then back to A. It goes on...
(All the chair are same models or promotes same comfort.)

[Cheencheela]

Okay, no soupage here.

Reinstalling the Framework didn't work. I'll experiment some moar.

Edit
THERE ARE FUCKING GHOSTS IN THIS GAME.
I reinstalled, followed instructions (Once again) and it worked.


I am scared...



Crashing? Are you non-awesome? READ THIS!

I believe most of you aren't following the instructions.
Hell, I didn't do that either. But then I actually proof read the readme, and found that you have to delete the ScriptCache in your My Documents/Electronic Arts/The Sims 3/
(Or something)

Try deleting it, reinstall BOTH the AwesomeMod and the AwesomeConfig at the same time. Don't run them individually, or else you'll have to remove the ScriptCache again.


If this doesn't work, then I guess I'm just a lucky son of a bitch.

[Fikcija]

You are lucky. Doesn't work.
The game worked fine yesterday. Today it crashes. I delete all the files that include "cache" in them. Works. I played. Had to quit. Deleted all the files that include "cache" in the name. Crash... Check - they didn't re-appear. Read this post. Reinstalled the awesomemod and the config file. Crash. Not working.

[Pythia]

I'm having no issues and no crashes with this version.
A quick suggestion for those that are would be to try this method of installation that someone mentioned either in this thread or in the main Awesome mod thread.

Take the mod and the config file, if present, out.
Delete all 4 caches.
Load the game. Load a family.
Play, just for a few seconds. Just let some time elapse.
Save and quit.
Put mod and config back in.
Delete caches again.
Now your game *should* load hassle free.

I bear no responsibility or liability if this doesn't work for you. It's worked for me for the last 2 versions and loaded every time.

[joshiejack]

Installing the enablescripterror.package fixed the problem for me, I didn't even notice it saying that there when I read the post the first time, silly me  

[Billmonaghan]

I've relaunched the game three or four times since installing the latest (as of yesterday afternoon) version of the mod with no crashes or other apparent problems.

I don't even have to delete the cache files before re-launching each time, which is a relief because His Excellency's instructions have always indicated it is only necessary to delete the scriptcache package once after installing the mod and before launching the game. I've only had the enablescripterror package installed since yesterday, so I think that's been instrumental in getting the mod to work as the instructions and other users' experience indicate it should work.

As a squirming little n00b, I've found you really have to pore through all the threads in the Armoire, make sure you download all the .zips referenced in His Excellency's instructions, and make sure you install all the contents of those .zips where they belong.

[Bass Junkie]

As a squirming little n00b, I've found you really have to pore through all the threads in the Armoire, make sure you download all the .zips referenced in His Excellency's instructions, and make sure you install all the contents of those .zips where they belong.

Surely you don't mean that you have to read the instructions and follow them? THE HORROR!