Game Crashing during auto save

Yes.
Don't use auto save.
I keep 3 saved games and rotate between them. I always save every turn unless i didn't do much. That way if one is destroyed, i have 2 recent backups and not much to repeat.

Yes it is tedious and a pain in the aSS but definately necissary.

You could be running low on memory, if it is that far into the game when it starts to crash.

If I have a particularly long turn during a war where I have destroyed a couple hundred ships and taken several planets I will run out of memory as well. And I think it has to do with how much it needs to keep in RAM, not the total available including swap file. Because when it fails to save the game and gives the error that I am out of memory my total system usage is usually around 2.7GB (I have 3GB of RAM and plenty of swap).

(I am not playing DA, though. But this is what I have noticed with DL.)

I think also the more times you reload a game, the more chance of getting problems. This is true for all turn based games as far as i know.

However i have noticed that the reloaded game in Galciv is not identical to its save. Notice if you rush buy a colony ship, save and reload the game, you don't get the colony ship next turn! Ergo a different game to what you saved. I think this is most likely what is behind all the saved game instability.

Mystikmind thanks for the info, I will try playing thru with the auto save turned off and see what happens.

Having the same crash problem here. Yet Beta2A doesn't just crash on autosave, but manual save as well all the time once reach the mid-game...

Having the same crash problem here. Yet Beta2A doesn't just crash on autosave, but manual save as well all the time once reach the mid-game...

This is what i first thought, but then i realised i wouldn't necissarily know if it was crashing on the autosave. Just as easy to asume it might be if the game ever crashes after hitting end turn. Because you know, who ever keeps track of when an auto save is due? i know i don't!

Happens to me too. They had this problem with one build of DL, but Cari fixed that problem relatively quickly. Looks like it's back. I've sent in my error log, not sure if it will help without a saved game. I've got 512 MB of RAM and additional 768 paged.

Thanks Mystikmind, I was able to play the game without any further crashs after shutting off the auto save

This is what i first thought, but then i realised i wouldn't necissarily know if it was crashing on the autosave. Just as easy to asume it might be if the game ever crashes after hitting end turn. Because you know, who ever keeps track of when an auto save is due? i know i don't!

Oh thank you thank you! you are absolutely right. Disabling autosave actually makes the ever-stopping crash-frenzy gone! This makes me wonder what exactly does autosave do anyway...

Signed.

Yeah I had autosave crash on me yesterday. Emailed exception info in along with debug.err. Autosave file was 0 bytes.

While shutting off autosave may fix the issue (assuming it is autosave and not something else that effects it) this is counter productive. The point of the beta is to get the devs as much info about crashes and other problems as we can. Avoiding them allows you to play but doesn't result in something to help track a problem down. I hadn't seen this issue until I had a particularly long play session of a few hours. So it could be related to a memory leak of some sort.

cyberj914, shutting off the auto save is not counter productive... when the game crashes I email in the report. After that I continue the session to see if there are any other problems or irregularities. Which is hard to do, when the game crashes every time the auto saves kicked in. Have now been able to play out several games without any further crashes, except for some odd AI building patterns...

I am having the same problem. Games continually crash during the sutosave. Same time, same place, every game. I have seen in the forums that this build is very stable and does not crash alot. Unfortunately, that has not been my experience. This game crashes constantly, especially when playing a gigantic map. Reminds me of the same problem they had with Dread Lords. The memory usage is incredible. I have watched a game use over 2 GB of RAM and 98% of the cpu cycles just before it decides to crash. Windows event log always point to a fault bucket and a problem with the GC2DarkAvatar.exe file. I like this game, it just doesn't want to play on my system.

Well, with the new DA Beta2B, I'm not having crashes from autosaves anymore. However, I still get CTDs after a certain point. Do a quicksave, and a turn or two later it crashes when I hit the TURN button. Load the game, and it happens again at the same exact point. I then have to go to one of the autosaves and load from there....only to have it happen again maybe 10 turns in. It's getting to be quite frustrating playing on Gigantic. Not sure if this happens on smaller maps, but something is corrupting the game save files.

Interesting. Except for the one time I reported above I have yet to have the game crash on me again. I do play on the smaller maps typically Medium or Large. The game I had it crash I think was actually a Huge map. There very well could be some memory usage problem here that manifests itself sometimes with the save crash.

Going to have to play a gigantic map and see if it happens as well. Off hand how many opponents are you using?

My settings are Gigantic with only military victory and no surrenders allowed, everything set to common in loose clusters. Tech rate: normal; minor races: 3; opponents: 9 and random; tech trading allowed. Auto saves set for every 6 turns. AI set to suicidal. Let it rip, cyberj, and let me know what you find out. I would hate to think it is my drivers. My vid drivers are fairly up to date, but I can't update my sound card beyond what's available from the manufacturer and that's already a couple years old. Then again, this wasn't happening with DL so...

Try doing random quick saves and loading from them while playing. See if that starts destabilizing the game. If so, that is a problem, especially for us evening players who have jobs and families.