Crash During AI Epeiros Turn

**ldb88** · 12-16-2009, 03:53

My Averni save crashes immediately after the Epeiros turn. I've checked for revolts and taken control of their faction. They are very small (only one city) and no real army, so if it can be fixed by simply moving their units around or something similar, there shouldn't be many options. But still I have been unable to find the problem. I've tried scaring off the army siegeing their city, siegeing Epidamnos, killing the KH diplomat, and a few other things. None of them have worked.

Here is my save game (right before the crash, still controlling Averni): http://ul.to/nu8qos

This is using the Alexander executable. I have a save from a couple years back, but I've already reloaded that save 4 or 5 times because of crashes. I think if I have to do it again, I'll just give up and abandon the campaign. Taking over GB gets really old the 4th time in a row! I guess since they're basically already dead, I could teleport some units over and take over their last city (destroying the faction), then gift it to Macedonia, but I would have to somehow siege and take over the city in the same turn (not sure how to do this).

If anyone has any ideas how to fix this, please let me know. Thank you.

**XSamatan** · 12-16-2009, 10:43

fixes installed? (especially the sweboz refrom marker-fix?)

After the Epeirus-turn? Is the shield of the eleutheroi coming up? Or is your own faction symbol showing in that status bar at the to of the screen?

If they got only one city left, there cannot be any revolts, if it is linked to Epeirus (what I doubt) then the reason should be something like a bad trait or duplicated FM's. Did you teleport any of them in your game?

Do you have any revolts taking place in your own realm?
Try to get over that turn by not activating the script, this could help if the crash is related to the EB-script.

To kill them, teleport a good spy and enter the city and let him open the gates. (Maybe you have to try it more than once) Alternatively you could create a unit of elephants and simply smash the gates. As I said before, I do not think they are the reason.

XSamatan

**ldb88** · 12-16-2009, 16:18

Yes, all fixes are installed.

Pushing end turn for Epeiros, any remaining unit movements are handled, and there is a slight pause where the music keeps playing (I assume this part is fine). Then the music stops, and Windows brings up the box saying it crashed (It doesn't really show the desktop or the box until I ctrl-alt-del, but the box is definitely there, as moving the mouse over that region indicates). The shield for Eleutheroi does not appear. However, even after destroying the Epeiros, the crash occurs. So it seems you are right in that the problem is with the Eleutheroi.

There are no revolts in Averni cities. I went around the map and dropped the population to 400 in all revolting cities, but this was during my Averni turn so things may have changed between then and Epeiros/Eleutheroi turn.

Turning off the background script allows me to get past the turn. Is it safe to leave it off for one turn? It seems that if it's crashes, it's trying to do something, so disabling it might cause problems. Either way, turning on the background script during the next turn, it crashes after this turn also, with Baktria displayed at the top. The next turn it's Epeiros. And so on....

EDIT: Note this is just what's displayed on the screen. I've noticed before that the same crash can display different factions at the top each time I try it (simply reloading the save). For example, one time this current crash happened when I was controlling Averni, it displayed the faction before Epeiros when it crashed.

If we continued to pursue this, would there be a hotfix for EB? Or is EB 1 bug fixing completely done for?

**XSamatan** · 12-16-2009, 17:14

I would please you to try this with your original save (epeirus alive):

open the console and write" toggle_fow

select in the option menu "follow AI-Turns"

decrease unit moving on the campaign map, press the space-bar (or if you load fresh, do not press it)

With these steps you should be able to see any move a AI faction is doing through its turn, so you should be able to figure out which faction is causing the bug, if it is still to fast, do it again.

It would help to know exactly which faction is causing the CTD.

btw: what year is it?

XSamatan

**ldb88** · 12-16-2009, 23:01

I did what you suggested. Epeiros was at the top at the time of the crash. They didn't really move any units. The camera just centered on their city; wait a second or two; then crash.

It's Winter 216.

**XSamatan** · 12-16-2009, 23:24

Thanks. Hmm, if you checked all cities (yours and AI) for rebellion and the delete of Epirus does not help, you should go back to an earlies save.

I'll see if I get your save to work.

XSamatan

**ldb88** · 12-17-2009, 01:37

Thank you for the help. Don't work too hard on it, though. I had already almost beaten the campaign. Though it would have been nice to fight Macedonia and AS.

I'll check for rebellious cities again, this time from the Epeiros turn. If that doesn't work, I think I'll give Hayasdan a go.

Thanks again.

**XSamatan** · 12-17-2009, 08:00

I tried it on ALEX and on RTW exe. With RTW it does not load, with ALEX it crashes repeatably. Do you have some minimods installed?

XSamatan

**ldb88** · 12-17-2009, 15:13

The only modifications I have made to the installation are
1. Install the three hotfixes
2. Install the "engine only" files for Alexander (https://forums.totalwar.org/vb/showthread.php?t=94861)
3. Modified the generic script to allow for controlling Epeiros.

**XSamatan** · 12-17-2009, 15:40

sad...I will try it with my 3rd build tonight

AlX-exe should be normally more safe and stable than RTW-exe.

**bovi** · 12-28-2009, 08:41

Originally Posted by ldb88

If we continued to pursue this, would there be a hotfix for EB? Or is EB 1 bug fixing completely done for?

EB1 is not being actively worked on, but if we can successfully isolate the cause, official fixes will be made available for crashes. Less critical stuff like recruitment errors, grammar and such will be part of a 1.3 maintenance release, whenever that comes.

In general, we try to simply help people work around the problems except when it seems very likely that we will be able to find the cause. I have one report from Weebeast from august or september that I'm going to have a crack at when I once again can spare the time (fatherhood takes a huge effort), but no other report is on my plate. Yours would have been one, if you had not been using Alexander.