PDA

View Full Version : Dammit!!! Stupid EB 1.0 CTD!!


jsadighi
10-30-2007, 06:55
This has happened on 2 occasions.

My Hayasdan army beseiging Charax is attacked from behind by a small Seleucid army consisting of a unit of Hellenic Bodyguards, and 1 unit of Hellenic archers. The besieged Seleucid army of Charax (which consists of 1 unit of Hellenic archers, 2 units of Native Hellenic Spearmen, and 1 unit of heavy spearmen) are used as reinforcements.

Anyway, I win a ridiculously easy clear victory. I then choose to occupy Charax, and then boom, the game gives me an all too convenient CTD.

Here is the link to my save game: http://uploaded.to/?id=tsmcy5
iwwtf_az
10-30-2007, 07:09
reinforcement ctd strikes again?

have you checked the bug fixes? have you tried w/o the script on?
jsadighi
10-30-2007, 07:50
I don't think its the reinforcement bug you've mentioned. I've had several battles with reinforcements and no CTD.
jsadighi
10-30-2007, 07:52
I've also checked the bug fixes but none of them apply to my issue.
Thaatu
10-30-2007, 09:07
I have no answer, only speculation. It's not a battle CTD, since it happens after the battle when occupying the settlement. It's probably not a reform bug, since you'd have to build structures to the settlement, and you probably don't have Susa and Persepolis. I doubt there's nothing wrong with Charax itself, since in Seleukid hands it seems to work without any problems. I wonder if there's some scripted message that Hayasdan gets when taking Charax..?
bovi
10-30-2007, 09:41
Please try the fixes. As said in the top of the post, even though they may not seem relevant, they may be. I think the traits nerf is probably going to get you past this one, or running without the script.
bovi
11-07-2007, 21:02
The game didn't crash when I played out the battle and occupied the city.
L.C.Cinna
11-07-2007, 23:42
Most probably one of the crashes that just occurs from time to time. had this thing happen in earlier EB versions as well (and with some other mods iirc).

After the battle is over just wait a few secs befor you occupy a settlement. My guess is that it happens sometimes if the pc is still busy with battle/switch to campaign map/changing of owner/checking script which causes this error.

retry.