Siege results crash

[nmleague]

I have started 3 seperate games and have gotten through about two years in each, but I keep having a problem after about the first year. I click end the turn and the game gives me a message that a siege was successful, and then the game crashes and I get an error message. If I load the game from my last save, if it was about the same time, I will get the same crash, it has happened multiple times in all three games, and always while giving the seige report. I think that I recall the game scrreen showing an area that was not where the actuall siege took place. If I load a save from several turns earlier I have been able to get past the point of the crash.

In each game Im contolling the Union.

[nmleague]

Should point out that between the three games this has happened with the sieges of a number of cities, just to name a few Shreveport, Chattanoga, Savanah and the latest was Fort Pickering.

[Peever]

Eric is aware of the problem and even has it fixed I think.  The patch to fix it should be out soon.

[nmleague]

Great, I cant get past the crash in my latest game [&:], the CSA only has Knoville left in TN and has a Union army in Lynchburg in Virginia, the South is on the ropes [:)], in Nov 1862.

[quikstrike]

Good, I believe that will fix my problem--sieges have been ongoing every time all three of my games have crashed as well.  I've given up playing until the issues are fixed.

[marecone]

Damn[:@] I got a crash on Lynchburg siege.

[Hard Sarge]

We are testing it now, we think it is a message bug (that why it don't happen all the time)

sorry my last run, I made it all the way with out getting a crash on any seige

but early on, it looks like we found and corrected what was wrong

[marecone]

Thanks. Looking forward to that patch [:)]

[Hard Sarge]

Roger that

early testing looks good, but I don't know what kind of timeline we looking at

[freeboy]

this one hopefully can get us playing again...

[Paper Tiger]

Sarge can you send out the "beta" version of the patch to those who have registered the error and we can assist in the testing and feedback any problems?

[marecone]

Guys, I am so frustrated with that crash [:@] 1862 just began and I already have Kentucky, Arkansas, 90% of Virginia and kicking rebel butt, but Lynchburg siege crash doesn't let me go any further. Tried everything. Nosound, video, music to lowanim and nosound.
I belive that this should be your primary target for fixing as it is serious bug.
Everything else is very nice [:D]

Thank you in advance

[marecone]

Even did try to disable messages about the siege but it crashed againsm=Christo_pull_hair.gif]

[Hard Sarge]

Keep the save, hopefully once the patch is out, the save will still work, the OOB changes will not matter as you are far enough in that they don't mean anything
it is seen as serious and is being worked on, all it needs is testing now

the patch is too big for me to pass out, it would need to be set up for download from Matrix

I get enough runs in on it, I hope to be able to give the thumbs up on it and then they can see how they want to handle it

[Kadste]

I was able to get past the siege bug by loading the last autosave and putting the siege on aggressive on the last turn before the fall.

Maybe this can work for you.

[Justin Case]

Greetings to all,

I just thought i'd upload the MS Failure Report.
It shows the failed module, I believe.

This was Small Scenario, after Ft. Hill was successfully sieged.

[Hard Sarge]

we have a fix for what we think is the trouble with the seige bug

they have to build the installer for it before they can release it

[marecone]

Thanks for the patch guys [&o]