133BC CTD in AI Getai turn

**QuintusSertorius** · 06-17-2008, 18:01

I'll give the "kill them on the sally" option a go. Back in a bit...

...*le sigh* No, I get a CTD on their turn in about the same place again. :(

**Dumbass** · 06-17-2008, 18:37

Does it ctd before they even sally out to attack you? That is strange. I guess you'll have to take the settlement in one go. I'm not sure of the command but try creating some stone launchers to take the settlement.

Edit: Or try moving a spy in there to open the gate and then get an FM to take the settlement in one go.

**QuintusSertorius** · 06-17-2008, 18:43

Originally Posted by Dumbass

Does it ctd before they even sally out to attack you? That is strange.

Yep, never even gets to the stage of that pre-battle screen. Also CTDs if you try to look into the settlement either with a spy, generic script, or with anyone near enough to actually see something.

Originally Posted by Dumbass

I guess you'll have to take the settlement in one go. I'm not sure of the command but try creating some stone launchers to take the settlement.

That was delra's suggestion, it CTD'd on pressing the assault icon.

**delra** · 06-17-2008, 19:41

This just sucks but this is also the sad reality of EB. Most of my games ended like this, with a persistent CTD I couldn't circumvent in any known to humanity way. It's a shame it ends such an excellent AAR, probably the best AAR I've ever read.

What do we have left except waiting for EB2 (it's still at least a year of waiting at best)? Not much except starting another campaign.

**Swordmaster** · 06-17-2008, 20:18

This is bloody annoying, even more so since it was a splendid campaign. I'm afraid the only option is to either ditch it, or take it again from your last save of 140 BC. Too bad you didn't keep more saves. For this reason I actually keep a save of every single turn, as a habit. Everyone should.

My guess is that it's a cloned FM inside Buridava, and whatever you want to do with the garrison there, either view it or attack it, crashes the game. I can't think of any solution, actually.

**bovi** · 06-17-2008, 20:35

This other guy also had a problem that seems similar to this one. When he was to attack or even look at Ipsos, the game crashed. I moved a spy closer and closer, and while I could see all the units inside the game crashed when I moved him closer (or into the city), so I'm pretty certain there's something about a building. The last files to be accessed there were some concerning the "egyptian stone walls", but I couldn't find out what was wrong with them. Could you run FileMon alongside EB and see if it's the same files being accessed last in this case? I fear there is nothing that can save your campaign, but perhaps we could fix it for the next version.

**QuintusSertorius** · 06-17-2008, 21:58

I'm going to be away from my machine til tomorrow evening; does anyone have FileMon that they're willing to run my save through? You could be saving my AAR!

Could it be something I can fix in my save at 140BC? I must admit I'm less than enamoured with playing out the last couple of days all over again, especially if I might hit the problem again.

Otherwise it's my Epeiros/Pergamon game before I try another Roman game with all the fixes in.