Repeatable CTD

[Gil R.]

I just checked the manual, and at two different places it says that one cannot besiege a city until all forts in a province are taken, but it does not say that one can only besiege one fort in a province at a time.

If those of you who had crashes while conducting two sieges could retry the game while conducting just one siege I would be very interested to hear whether you are still having crashes. (And I'm sure that many others would benefit from this as well.)

Thanks!

[krrpt]

FYI: I am having this issue and I am not besieging two targets in the same province.

[Alex Gilbert]

Well, I just had the above reported microsoft error announcing that the application would now close.  It was siege related, but in this case, it was the computer who was conducting the siege, and it was a single siege in a province.
 
As a side note, regarding the problems with besieging multiple forts in the same province simultaneously, I noted in my game that the COMPUTER uses this tactic, and so it may not be as simple as just having the players avoid this.
 
Alex
 
(I am sending the save files)

[oldspec4]

ORIGINAL: Gil R.

I just checked the manual, and at two different places it says that one cannot besiege a city until all forts in a province are taken, but it does not say that one can only besiege one fort in a province at a time.

If those of you who had crashes while conducting two sieges could retry the game while conducting just one siege I would be very interested to hear whether you are still having crashes. (And I'm sure that many others would benefit from this as well.)

Thanks!

Just to clarify...my CTD occured when I laid siege to two separate forts (Carroll and Madison) in the same province (Annapolis) with three separate armys (two on Carroll and one on Madison). I retried the sieges with only two armys with one each on Ft. Carroll and Ft. Madison and had no CTD.

[Gil R.]

Yeah, I was wrong -- one can besiege two forts in a province at the same time. For some reason I thought we decided against that. Mea culpa. But cities definitely can't be taken until the forts are gone.

[ericbabe]

Thanks for sending the save files.  I've been looking at Temple's save files under the debugger.  It does seem to have to do with the siege.  Will try a fix tomorrow morning and let you know how it goes.

[Luciano B]

Im' afraid that I encountered the same problem: as soon as the window tells me that I captured Columbus (OH) the game crashes to desktop ...the same occurred in a previous campaign when I captured Kentucky's capital ...maybe it is something related to the seige of the capitals?

[Luciano B]

...just sent the "autosave" files to Eric ...thanks in advance.

[Texican]

ORIGINAL: Gil R.

Yeah, I was wrong -- one can besiege two forts in a province at the same time. For some reason I thought we decided against that. Mea culpa. But cities definitely can't be taken until the forts are gone.

But regardless, violating a game rule should simply be prevented or made impossible by the code, not cause it to crash.

[Luciano B]

...I started a new campaign ...again, the same problem after a siege ...this time with the capture of a fort in Maryland ...at this point I can only wait that someone will manage to resolve or patch the siege issue, since right now I can't play the game without encountering  a crash to desktop after the capture of a town or fort...

[spruce]

I had a CTD when I (CSA) as besieging the cumberland fort with 2 siege works (one army container and one division container ) - I saw 2 siegeworks on the map.
 
Then after some time - the fort is taken - I get 2 messages from my confederate "messenger" telling me I have taken the fort (can't remember the name). Then CTD

[Gil R.]

ORIGINAL: Texican

ORIGINAL: Gil R.

Yeah, I was wrong -- one can besiege two forts in a province at the same time. For some reason I thought we decided against that. Mea culpa. But cities definitely can't be taken until the forts are gone.

But regardless, violating a game rule should simply be prevented or made impossible by the code, not cause it to crash.

It's pretty clear that the crashes are not linked to violation of a game-rule, since some crashes occurred when only one target was being besieged.

[tc237]

I have the same crash.
For me it seems to be when a Div. container enters an area being besieged by another container (Army in Murfreesboro in this case).
Upon ending the turn, I get the standard "Fort xxx has been successfully besieged..." message.
Hit "OK" and the game hesitates for a few seconds then crashes.
Have an auto-save that will crash every single time upon End of Turn.
 
-sending save file

[Temple]

And the third CTD situation for me [:(]. This time the siege of Knoxville. Files have been sent to Eric. Noted something odd, when the "siege sucessful" message came up the city was blue (I am union) but the siegeworks icon was still there. That's wrong, right?


UPDATE: And just to make it clear, I had a single force laying siege directly to Knoxville, there were no forts listed when I made the option to besiege.

[ahauschild]

I have also received this crash, after a successfull siege in Kentuky I get the window error message and then it shuts down to the desktop.
Happend now on 4 diffent campains, pretty much the game is unplayable till this is fixed, as you have to siege in order to take lands.
Hope we get a quick fix for his real soon.

[Great_Ajax]

I am getting a CTD every time I reload one of my saves. Not sure what is causing it but it happens after I pick a technological upgrade and before units even begin to move. Music starts to stutter and then I get the Windows crash dialog. Screen says "Moving ..." Disappointing because I was doing really well and enjoying the campaign in Jul '62. Probably not going to start a new game until these CTDs get fixed as this is the second one in as many games. Highly frustrating.

Trey

[Gil R.]

ORIGINAL: el hefe

I am getting a CTD every time I reload one of my saves. Not sure what is causing it but it happens after I pick a technological upgrade and before units even begin to move. Music starts to stutter and then I get the Windows crash dialog. Screen says "Moving ..." Disappointing because I was doing really well and enjoying the campaign in Jul '62. Probably not going to start a new game until these CTDs get fixed as this is the second one in as many games. Highly frustrating.

Trey

This sounds like something Eric should see. Please send those save files to him (ericbabe@west-civ.com) in a zip file. Thanks!

[JaguarUSF]

As I noted in my e-mail to Eric, I seem to remember that the game said I captured the Cumberland province 1 turn BEFORE the game said I seiged Fort Hill. I sent the past 3 turns to him. Maybe this is the issue?

[Temple]

Damn, damn, damn. In my current game where I had the repeatable CTD after besieging Knoxville I loaded an "autosave3", in other word three turns back. I did NOT besiege Knoxville again, instead I passed it by and attacked Chattanoga. All well and good and the siege worked. And then I went back to Knoxville and laid seige and this time it was successful without the CTD.

However.... I continued playing and eventually attacked Atlanta. After several turns I suddenly found, once again, that the city color was blue but the siege icon was still there. And when I pressed the "Next Turn" button, after several other messages I got that "Atlanta has fallen" and bang, the MS dialog box pops up and the CTD occurs. My fourth CTD file set on the way to Eric.

That's it, I give up. Please get the patch out ASAP.... I can't deal with these CTDs anymore.

[krrpt]

7 (attempted) games - 7 siege related crashes. At this point do you need any more saved files sent your way or do you have enough information to debug this issue?