Speeding up sieges after the patch

[von Beanie]

I've got the patch installed. I started three sieges last turn. The next turn when the siegeworks were in place, I selected the "Attack Fort" option to speed up the conquests. In all three cases when the turn ended it said that the sieges were abandoned because there's no attackers, but my armies that started the sieges and built the siegeworks are still there. So I restarted the sieges, constructed siegeworks again, and the same thing happened. What am I doing wrong?

[spruce]

have witnessed this to when besieging Cairo - I think it's a bug[&:] - choose "aggressive siege" instead of what you have selected and it will work out better.
 
In a certain battle I had 2 div's of each 16.000 besieging a city with 2.500 troopers left - I saw the garrisons doing nearly 2.000 damage on my 2 divisions - after the battle they were down to 6.000 each - it seems they had been attacking one another ...

[Hard Sarge]

When I tested this, I went right into HW combat when the turn ran

(if in detail combat always or quick combat always)

do you remember what areas you were in when you were trying this

(maybe a area has something that is interfearing with this ?)

[von Beanie]

Before the patch, when I selected the attack option for a siege and it did go into a detailed battle, so I know my game once worked that way.

As I wrote, this is happening in three different areas simultaneously. One was Frankfort, KY. The other was at Louisville (river province to the NW), and the third was somewhere near Wheeling, WV. The fact that it is happening everywhere, and repeats when I tried it again, suggests that either I'm doing something wrong or there is now a new bug.

[spruce]

In my case =
 
- it was the siege of Cairo (I was CSA),
- the problem only occured when I was doing an "attack fortress" with my siege works. When I choose aggresive siege, there was no problem,
- I had 2 divisions doing the siege, both with their siege work,
- and the math numbers didn't match the battle casualties during the detailed animation (there were excessive losses not to be accounted for in the detailed animation window),
- it gave the strange text "siege stopped because no besiegers left" - still the division wasn't lost and could continue the siege during the next turn,
- I'm not sure if there was an enemy gunboat present - not sure tough,

[von Beanie]

I actually found the autosave file just before this happens. There are no gunboats in any of the locales. I would be happy to email anyone the game file. Simply select "Attack the fort" at Louisville, Frankfort and Wheeling, then end the turn. Watch the end of the turn report and you can see for yourself. I get the same message, something to the effect that "no besiegers left," but my armies are still there and can restart the siege.

Just let me know the email address where you want the file sent to and I will do so.

[Hard Sarge]

PM sent

Odd as I have tested this for some one else since the patch came out, and I went right to HW when the time came (different question)

[ericbabe]

There's a thread discussing this already; it seems to be the case that the "attack" siege option isn't working with cities (though seems to work with forts?)  We're looking into it.

[Hard Sarge]

I'll send you some info Eric

it looks like we got a bug in that some areas work, and some areas do not

in my last run, I can attack the fort, but yea, looks like I can not Attack the City

(hmmmmm, well it does say attack the fort ?, the city is not a true fort, could that be kicking it out ???)

sorry, my last test run on the patch was for the message error, so was trying to get the seiges to finish or die

but I did run a couple of attacks and I happen to pick the areas that are working

[Hard Sarge]

Reports turned in