i've the identical problem.

Whenever a memory leak or similar issue surfaces it has this deletion effect. GalCiv deletes the current save file before creating the new one. Net effect is that when it finds it cant complete a Save routine, you lose the lot. I have never understood why they do this, its not rocket science to rename the old save file to .... whatever ... before doing a save, if the save routine goes wrong at least you have the original. Rename it and move on.

With memory leaks present, after the save routine is started, it discovers it cant complete a save due to no memory available. Fair enough as such, it happens, but by that time it has already deleted the original. So if you see the "Cannot save- not enough memory" warning, dont try to save, its a self destruct exercise. If you do it multiple times, you just work your way through all the save files you have, starting with the most recent, and each one gets zapped - press save 3 times, you lose the last 3 save files etc.

Now when "Cannot save- not enough memory" appears, I just accept it as life, come out - restart with last save file, at least I am still running. Its a crazy way to do things, but there is no other choice.

Regards
Zy

The problem here is that Stardock wont accept that they have buggy code causing this and like Ive said earlier this problem has been round since the first GC2, all they do is say only a small % of people are having these problems, and then go on adding bells and whistles instead of fixing the bugs.

At no point has anyone denied that there is an issue. Cari has been working on this (among other things), but the cause has remained elusive (yes, there have been bugs before that did not manifest when the game was run in the debugger, making them very difficult to pin down).

If they ever get this fixed, can someone give me a shout, because I would dearly like to buy and play DA.
Or maybe Cari would PM me if/when she kills this bug dead with a big stick, it has to be truly dead though unconscious or still wriggling don't count.

That halfview open thing seems to happen until the end of the turn that I bring it up (usually to do something like find a lone Spore Ship)
It hasnt given me any game-crashing problems though...

I've never had any problem with slowdowns or crashes running a gigantic map. I use to get slowdowns midgame when the AI would stack ships, but they made a beta patch for that. Try getting a 256mb video card, and bumping your virtual memory up.

Hehe, that's funny, if this is the problem then why have frequent random planet surfaces and gigantic maps, you may as well put a option in the game (crash out of game and hard lock computer in the next turn please)

So if we turn every thing off that's off-able and reduce everything that's reduce-able, turn our displays down to 60x40 with 16 colours, cross our fingers and anything else cross-able then we might get a game without a crash. Okay then, but why dident you say this on the game box?

Yep, Im a little wissed at not being able to play these games due to bad code that's been with GC2 from birth and gone though a expansion and a trillion updates yet that same darn memory leak is still with us and goes round and round and round and, well you know what I mean, actually I'm a bit of a expert when it comes to this bug, mainly because of all the fixes and 3rd party pogs I tried, yet to no avail. 2 of the main areas when this bug rears it ugly head are on saves/auto saves and random events and always usually happen on large and gigantic maps halfway into the game and it dosent matter what you turn down or off the crash will get you in the end, just gain a few more crash free hours that's all.
I hope one day they find and plug it.

I just wanted to add my little story.

I am running on a E6600 Core 2 Duo, 2 gigs ram, and a GForce 7950 GT (512 megs ram).

The game locks up after about 4 hours of play/idle time. I will frequently start up a game and have to walk away to do various domestic stuff (2 small children seem to be a time sink...). I will come back to the out of memory error.

I don't think it is related to a random planet generation problem because on my current game I am playing at rare plants and rare suns. I have also downloaded the pre-generated planet pack.

I am looking forward to this being fixed because the crash always comes at teh worst possible time.

Wonderful...does it appear in the Stardock updater or is it a separate patch?

I did a search on the forums and couldn't find anything. Do you happen to have a link?

Thanks!

Thank you...I will try it out today.