AWESOMEMOD & SCRIPT HACKS: CRASH ISSUES THREAD
deroger:
Cool mod folks!
I also had the CTD problems, but found out that it was obviously a hack conflict to GORRE's "Faster Writing More Money" Hack. Since I removed that package my S3 boots up EVERY time.
Thx
Tom aka der oger
Simius:
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.
Okay... I gave that a try. It CTD after I ran my bat file which copied the backup cache files over. So I played around with it and just have it delete the cache files for me then launch the game... and it seems to work. I'll have to wait for a few more builds to see if it continues to work or if it is entirely just voodoo.
Since I was already making .bat files... I also made one to automatically install any packages that are in my downloads folder. The monkey installation utility won't overwrite mods... So I used to have to go in and delete them first then double click on them to install the updates. Now I can just run my .bat file and it does it for me.
Lobster:
OK, my game ran fine the FIRST time, but then the first time I went to save it hung on the save screen for about 10 minutes. The progress circle wasn't animated but I could move my cursor. Eventually I terminated the process. The next time I went to load, I got the same problems described here. Removing Awesome.package lets me load and I see that the save was successful. I'm in the process of trying the many suggestions here. When I say "first," I mean the first time I've run the game with ANY version of the mod.
In the error report, I found this line:
[Instruction data]
004df15b => DasmX86Dll.dll not found.
Might be worth looking in to?
With all due respect J. M. Pescado, and I mean that sincerely since your mod is really, well, awesome, I've found your claims of voodoo magic being the cause to be disheartening. I understand that you don't see where the problem is, and that different people get different results from trying different things. To me, this says there are multiple, different problems occurring that just all happen to have the same symptoms. I know you must be looking for the problems and looking to fix them, but when you say, "this shouldn't be happening, it must be magic," it gives the impression that you aren't trying to fix the code because you don't perceive any problem with it. If I had to wager a totally wild guess, there's a process you're using or added in to record necessary that's a bit "fragile." For some people it works fine. For others, it occasionally produces corrupt data that causes the game to crash. So you may be right, it could be that there isn't anything in your code causing these crashes, but it also might be that it could stand to be a bit more robust.
But again, I'm sorry to criticize and I thank you for all your work. I had a great time with your mod till I began to encounter problems with it. Since these crashing problems appear to be new to this version, do you think you could make the previous version available as well?
EDIT: Clearing the cache files did it.
Simius:
Quote from: Lobster on 2009 June 13, 17:52:00
OK, my game ran fine the FIRST time, but then the first time I went to save it hung on the save screen for about 10 minutes. The progress circle wasn't animated but I could move my cursor. Eventually I terminated the process. The next time I went to load, I got the same problems described here. Removing Awesome.package lets me load and I see that the save was successful. I'm in the process of trying the many suggestions here. When I say "first," I mean the first time I've run the game with ANY version of the mod.
In the error report, I found this line:
[Instruction data]
004df15b => DasmX86Dll.dll not found.
Might be worth looking in to?
With all due respect J. M. Pescado, and I mean that sincerely since your mod is really, well, awesome, I've found your claims of voodoo magic being the cause to be disheartening. I understand that you don't see where the problem is, and that different people get different results from trying different things. To me, this says there are multiple, different problems occurring that just all happen to have the same symptoms. I know you must be looking for the problems and looking to fix them, but when you say, "this shouldn't be happening, it must be magic," it gives the impression that you aren't trying to fix the code because you don't perceive any problem with it. If I had to wager a totally wild guess, there's a process you're using or added in to record necessary that's a bit "fragile." For some people it works fine. For others, it occasionally produces corrupt data that causes the game to crash. So you may be right, it could be that there isn't anything in your code causing these crashes, but it also might be that it could stand to be a bit more robust.
But again, I'm sorry to criticize and I thank you for all your work. I had a great time with your mod till I began to encounter problems with it. Since these crashing problems appear to be new to this version, do you think you could make the previous version available as well?
EDIT: Clearing the cache files did it.
I think that the problem is that the game ISN'T supposed to be modded. But in all their glory they were able to do it anyway. The downside of that is that the code for the game gets confused when a a previous mod is changed.... Which causes it to CTD during bootup. (it is looking for a file that says XYZ when the new file says XYZA and it crashes). Clearing the cache seems to be a work around for that... although sometimes it takes a few tries (of clearing the cache or not doing so or whatever and continually restarting the game) to get the game to look for XYZA and actually be able to start. I'm of the opinion it isn't anything really in the mod doing it... it is the fact there is a mod and it had been changed and the game can't handle that.
Your mileage may vary though.
Roflganger:
I fully believe it IS Voodoo magic simply because all I have to do is keep reloading the game and eventually it works. I don't delete cache files, I don't change anything. I just keep reloading it, and on the 2nd or 3rd try, it loads successfully. If nothing at all is changing, yet the game randomly works or doesn't, well I don't see how that can be anything but weird voodoo magic. How do you fix a bug that randomly fixes and unfixes itself, and occurs at a point where the mod isn't even in play yet?
Navigation
[0] Message Index
[#] Next page
[*] Previous page