AWESOMEMOD & SCRIPT HACKS: CRASH ISSUES THREAD
Billmonaghan:
Quote from: redwards on 2009 June 13, 04:39:14
(I don't have the errorscript package installed right now, FYI).
I was having to delete all the cache files also, until I install the enablescripterror package.
Now I don't need to delete anything, other than to remove the script cache file each time I install a new version of the mod.
mildlydisguised:
Just adding my report. No crashes on load with any previous awesomemod but with this version I got seven crashes in a row despite deleting caches. After the seventh crash I added the enablescripterror and was able to load the game.
J. M. Pescado:
Yeah, it's basically voodoo. One of the things you can try is simply rebooting the computer.
Fikcija:
Rebooting also doesn't always work. I find it more useful to remove the awesomemod, load the game (don't play, just let it load to and quit without loading any neighborhood), then install the awesomemod again and it works. To me this worked everytime, while other things seemed random. But it looks like it's different for everyone.
Edit - this seems to work too, perfectly, every time:
Quote from: redwards on 2009 June 13, 04:39:14
So, I've been having the on-load crash more often recently (wasn't getting it at all before). I think I've found a solution that works every time, for me, at least.
1. delete the cache files
2. start the game. It crashes. The cache files are regenerated, but they're all, like, 1k
3. don't touch the new cache files, start the game again. Everything works.
So far, that method is 3 for 3, but any other method seems to fail.
(I don't have the errorscript package installed right now, FYI).
If this persists, I may just make a copy of those fresh cache files and write a little batch file that overwrites the existing ones with the fresh ones before starting the game.
redwards:
Quote from: Fikcija on 2009 June 13, 08:55:06
Rebooting also doesn't always work. I find it more useful to remove the awesomemod, load the game (don't play, just let it load to and quit without loading any neighborhood), then install the awesomemod again and it works. To me this worked everytime, while other things seemed random. But it looks like it's different for everyone.
Edit - this seems to work too, perfectly, every time:
Quote from: redwards on 2009 June 13, 04:39:14
So, I've been having the on-load crash more often recently (wasn't getting it at all before). I think I've found a solution that works every time, for me, at least.
1. delete the cache files
2. start the game. It crashes. The cache files are regenerated, but they're all, like, 1k
3. don't touch the new cache files, start the game again. Everything works.
So far, that method is 3 for 3, but any other method seems to fail.
(I don't have the errorscript package installed right now, FYI).
If this persists, I may just make a copy of those fresh cache files and write a little batch file that overwrites the existing ones with the fresh ones before starting the game.
Added the errorscript package back in, but also updated awesomemod. Behavior seems consistent. I'm working on a theory, but I bet this works for everyone:
1. If you don't have errorscript.package, you'll need to clear out the cache files every time you start the game. Run the game once to regenerate them (it will crash), and then the game will work, but you'll have to repeat this process every time you start the game.
2. If you DO have errorscript.package, the above is only true if you have updated awesomemod. As long as you don't update awesomemod, the game will start fine. When you update, you'll need to clear out the cache files, run the game once (crash), and then it will work fine and continue to work until you update awesomemod again.
So far the above is consistent for me.
Navigation
[0] Message Index
[#] Next page
[*] Previous page