Page 1 of 1
Still getting some program crashes after I die in 4.0.2
Posted: Thu Aug 12, 2004 3:45 am
by HowardWi
It doesn't happen as often, about 1 in 4 times.
Attached is log.
RE: Still getting some program crashes after I die in 4.0.2
Posted: Thu Aug 12, 2004 6:04 am
by Antic
Have you tried to totaly uninstall the game, delete every file in the folders etc. Then reinstall it and patch it up with 4.0.2 directly without patching with 4.0.1 before that?
I did and i havent had a CTD since. But my previous install where i replaced the 4.0.1 patch with 4.0.2 directly i had CTDs the way you describe.
Not saying this will solve it but it did for me.
RE: Still getting some program crashes after I die in 4.0.2
Posted: Thu Aug 12, 2004 10:54 am
by Burzmali
I've had a similiar problem on occasion, and I never installed the 4.0.1 patch. I'm guessing that a memory leak of some kind is to blame as the CTD usually happens after I have been playing for a while.
RE: Still getting some program crashes after I die in 4.0.2
Posted: Thu Aug 12, 2004 1:20 pm
by HowardWi
No I haven't. Can I save my game files or do I have to start over?
RE: Still getting some program crashes after I die in 4.0.2
Posted: Thu Aug 12, 2004 5:04 pm
by Pheagey
save any file ending in .cfg and anything in the Mods folder. Everything get deleted.
Worse than before
Posted: Fri Aug 13, 2004 5:35 am
by HowardWi
I did what you said kept all the config files and also kept the saved games folder.
Reinstalled the game and only patch 4.0.2.
First time I played, I finished the mission, landed safely and crash. Attached is the error log.
I will go back to the old way. At least that only crashed once in a while.
RE: Worse than before
Posted: Fri Aug 13, 2004 9:02 am
by John DiCamillo
I think I understand the bug in the first error log you posted. It is present in both 4.0.1 and 4.0.2 unfortunately, although it is more likely to occur in 4.0.2 due to the improved starbase AI in that release. It looks like the game will probably crash if you end a mission while any fighter is on a ground side runway. I have implemented a potential fix, but it is going to need some testing.
The second error log has no stack trace, so it is impossible for me to guess what exactly went wrong.