Saving after the fight

[Caridor]

Hi,
after few tries I have finally manager to destroy Hannibal on hard difficulty level (I’ve lost 666 men LOL http://imageshack.us/f/834/0000ug.jpg/ )and then (when game was opening campaign map screen) game crashed to desktop. I was devastated. Please unable saving option during the fights or immediately after the fight (in battle result window) because I don’t want to randomly lose my progress anymore. I want to play this great mode but in this state I won’t be able to finish it.
Sory for my English.

[Caesar15]

Hi,
after few tries I have finally manager to destroy Hannibal on hard difficulty level (I’ve lost 666 men LOL http://imageshack.us/f/834/0000ug.jpg/ )and then (when game was opening campaign map screen) game crashed to desktop. I was devastated. Please unable saving option during the fights or immediately after the fight (in battle result window) because I don’t want to randomly lose my progress anymore. I want to play this great mode but in this state I won’t be able to finish it.
Sory for my English.

Lol that exac tthing happend to me an di was pissed off

[themrwho]

Yes, it CTDs sometimes but if you save before and after every battle, the frequency of CTDs is not unacceptable. I am in 193BC in my campaign and have over 150 saves already.

With this method, when the CTDs comes I lose only the progress of one single battle.

The only time you can't save (or perhaps 'shouldn't' save) is during the AI turn. If several armies attack you in a single AI turn and it CTDs after the last of those battles, obviously you lose the progress of all the others. To address this issue, try limiting the number of battles on a single AI turn. Since we can't control AI, the only way to ensure this is, using forts extensively. Sure it takes some effort to save the games all the time, but it is much better than losing several long & huge battle progress.

Another side effect is when your legion in the fort is besieged, it takes a lot of time to sally out. To address this issue, depending on terrain, I use one or more forts and protect them with peasants. When AI besieges the peasant fort, next turn after saving the game, I attack with the nearby legion.

This method works for me so far.

EDIT - If you haven't developed the habit yet, do not forget to activate the garrison/4TPY script each time you load the game...

[Caesar15]

Yes, it CTDs sometimes but if you save before and after every battle, the frequency of CTDs is not unacceptable. I am in 193BC in my campaign and have over 150 saves already.

With this method, when the CTDs comes I lose only the progress of one single battle.

The only time you can't save (or perhaps 'shouldn't' save) is during the AI turn. If several armies attack you in a single AI turn and it CTDs after the last of those battles, obviously you lose the progress of all the others. To address this issue, try limiting the number of battles on a single AI turn. Since we can't control AI, the only way to ensure this is, using forts extensively. Sure it takes some effort to save the games all the time, but it is much better than losing several long & huge battle progress.

Another side effect is when your legion in the fort is besieged, it takes a lot of time to sally out. To address this issue, depending on terrain, I use one or more forts and protect them with peasants. When AI besieges the peasant fort, next turn after saving the game, I attack with the nearby legion.

This method works for me so far.

EDIT - If you haven't developed the habit yet, do not forget to activate the garrison/4TPY script each time you load the game...

Using peasants...wonder if anything about that is in the house rules