My perfectly fine working fix for game crashes

... on my comp, at least.
So I had a lot of trouble with this game (campaign). Constant crashes, every few turns. After ruling out hardware or driver troubles it turned out the game worked JUST GREAT with the first standard game (not campaign) I started. Seriously, I played for about 14 hours without crash! And without sleep. Until I had to restart the game and reload the saved game later. Yep, and the world of pain was back! Argh. Crashes, lockups, sound loops, you name it ...

I found out it makes a HUGE difference whether I load a saved game from the main menu, or from an already running game! If I load from the main menu, the game always crashes, sooner or later. Rather sooner. However, if I just start a "new game" and THEN load my saved game, I can play on for HOURS without being riddled by crashes! It's like magic

There also seems to be "old data" from the newly started game carried over into the game I loaded. Like my Empire's name. If I enter a different name in the newly started game, I keep this name, even though I loaded an older savegame. Same for spaceship colors (in the small windows, at least). I don't think this is supposed to happen. While not really a big issue, some sensitive comps (like mine, apparently) may be allergic to this kind of sloppy coding.
So, give it a try. Start a new game, then load your old saved game. Works great for me.
5,850 views 4 replies
Reply #1 Top
What version are you running?
Reply #2 Top
Well, the auto-update via stardock only made things worse (game won't start anymore), so I went back to 1.0. Until something solid comes out. Never fix a running system ...
Reply #3 Top
Primus....

I agree.

My 1.09x or whatever version was out before the last beta is what I play. I will never play a beta version.
Reply #4 Top
Primus, just uncheck the "show pre-release version" box.

1.0x is stable. Don't touch beta's if you don't know how to work around them