CTD - Elasson Rearguard

This forum is for bug reports and support requests.

Moderator: Arjuna

Post Reply
Golf33
Posts: 701
Joined: Sat Mar 29, 2003 6:54 am
Location: Canberra, Australia

CTD - Elasson Rearguard

Post by Golf33 »

Playing as Allies, Painful orders delay. Dxdiag report attached - note that the machine has 512MB SDRAM installed but the graphics adaptor is using 128MB of that. I did receive a warning on installing the game that there was insufficient memory but have been able to play games successful despite this.

In this game I did experience frequent pauses of a couple of seconds each, during which the hard disk would thrash. The cursor would remain visible and could be moved, and the speed control could be adjusted and units selected/deselected, but the side panel and map graphics (footprint etc) would not update until the pause finished.

I successfully blew the bridges at Kallithea and Elasson. The Axis flanked left and I failed to blow the bridge at Magoula. The Germans pushed through there and at Amouri and reached the Dhomenikon bridge. At this point I had an AT Pl cut off North of the blown bridge at Elasson, and an Inf Coy cut off in the area of Sikia-Magoula. I also had inf bns either side of the Dhomenikon bridge with the Axis spearhead in between. I had issued a Deny Crossing order to the battalion East of the bridge. Late on D2 I heard the bridge-blown sound and got the 'bridge blown (recalculating terrain tables)' then the screen went black apart from the order cursor, which could still be moved. After a few seconds of this I received CTD followed by a Microsoft error reporting dialog.

Unfortunately I don't have any saves but will try and keep them from future games, particularly just before 0600 and 1800.

Dxdiag report attached.

Cheers
Steve
Attachments
DxDiag.txt
(40.17 KiB) Downloaded 3 times
Steve Golf33 Long
Image
Phisto
Posts: 13
Joined: Sat Jan 29, 2005 12:30 am
Location: Poolesville, MD USA

RE: CTD - Elasson Rearguard

Post by Phisto »

I want to confirm a similar CTD with this scenario, as well as the various slow-downs and pauses despite having 1 GB of RAM with a 2.6 GHz Pentium 4.  I was playing as the Axis and had just reached Road Bridge 2 later in D2 when it blew.  Shortly after that the game CTD.  The Allies had not been able to blow any of the other bridges up to that point.  I also neglected to make saves, but I can make the DxDiag report for my machine available if that is of interest.  I will turn on the autosave feature the next time I play through.  Thanks.
Kurt
Post Reply

Return to “Conquest of the Aegean Support”