Page 1 of 1

Assault posture not working?

Posted: Fri Aug 17, 2007 11:12 am
by Jacek
Here is the situation. My stack under Johnston fights McClellan in Kentucky, who wants to take that part south of Evansville. There is a battle (rather inconclusive, because both stacks have almost identical strength) and in its aftermath both stacks sit in one region - Henderson, KY. I set Johnston to assault posture so he can finish off McClellan in the next turn. Turn passes and NOTHING happens - both stacks sit still without any fight!

I checked the whole log searching for some information about movement, reatreat, cancelled orders etc. concering the two stacks. Nothing again.

I replayed the turn adding a depleted cavalry unit, which was resting in the region, to Johnston stack. His detection rating didn't change (4/3 as before) but his hide value went from 1 to 2 (?). This time his stack found McClellan INFLICTING 7000 losses and losing 490 men in the process.

Any ideas?

Posted: Fri Aug 17, 2007 4:20 pm
by Jagger
Jacek wrote:Here is the situation. My stack under Johnston fights McClellan in Kentucky, who wants to take that part south of Evansville. There is a battle (rather inconclusive, because both stacks have almost identical strength) and in its aftermath both stacks sit in one region - Henderson, KY. I set Johnston to assault posture so he can finish off McClellan in the next turn. Turn passes and NOTHING happens - both stacks sit still without any fight!

I checked the whole log searching for some information about movement, reatreat, cancelled orders etc. concering the two stacks. Nothing again.

I replayed the turn adding a depleted cavalry unit, which was resting in the region, to Johnston stack. His detection rating didn't change (4/3 as before) but his hide value went from 1 to 2 (?). This time his stack found McClellan INFLICTING 7000 losses and losing 490 men in the process.

Any ideas?


Are you using the "delayed order execution" option? That option can delay the execution of an order for an entire turn from time to time.

Posted: Sat Aug 18, 2007 5:15 am
by Jacek
Well I am playing 1.05a demo on my dang old laptop. There is no "delayed order execution" option in the menu.

BTW, Johnston was active in both turns. Can't speak for McClellan though and I don't think his force wasn't small enough to just hide from my stack.

Posted: Mon Aug 20, 2007 9:38 am
by Pocus
the option delay the engagment, not the orders.

Same problem in Kentucky with 1.06d

Posted: Mon Aug 20, 2007 2:50 pm
by DaemoneIsos
I am having the same problem in Louisville, for two turns in a row. My army commander is on assault with two and a half divisions; no battle report. I thought the railroad repair on the first turn may have delayed the battle, but that was not the case the second turn. The defender is a single militia unit (at most a brigade) which should be a trivial fight. I have clicked and unclicked and reclicked the postures, etc.

It is winter, but I have not had this problem in any other location. And I do not have the engagement delay on.

I have not had this problem before on either side in any other situation, even for a single turn.

Thanks!

Posted: Mon Aug 20, 2007 5:26 pm
by blackbellamy
Army Commands do not initiate combat, regardless of posture. Keep the Army behind the lines, staffed with leaders, extra supply wagons, a some reserve troops so the HQ doesn't get accidentally overrun - do not send them into battles.

Posted: Mon Aug 20, 2007 8:45 pm
by Jacek
Army Commands do not initiate combat? Didn't know that. Maybe that is the answer though I have used Johnston and Beauregard as just another corps and it worked fine until that "Kentucky event" of mine.

Posted: Mon Aug 20, 2007 9:06 pm
by McNaughton
Jacek wrote:Army Commands do not initiate combat? Didn't know that. Maybe that is the answer though I have used Johnston and Beauregard as just another corps and it worked fine until that "Kentucky event" of mine.


Could be that the US were the ones initiating combat at those other opportunities. Given that in this situation their goal was flight, I doubt they would have attacked.

Posted: Tue Aug 21, 2007 10:27 am
by heroes99
Jacek wrote:Army Commands do not initiate combat? Didn't know that. Maybe that is the answer though I have used Johnston and Beauregard as just another corps and it worked fine until that "Kentucky event" of mine.


Army Command does not initiate combat on their own , however they have a chance to join the battle initiate by corps.division ..am I right ...?

In your case I believe the attack must have come from Union side

Posted: Tue Aug 21, 2007 10:42 am
by heroes99
DaemoneIsos wrote:I am having the same problem in Louisville, for two turns in a row. My army commander is on assault with two and a half divisions; no battle report. I thought the railroad repair on the first turn may have delayed the battle, but that was not the case the second turn. The defender is a single militia unit (at most a brigade) which should be a trivial fight. I have clicked and unclicked and reclicked the postures, etc.

It is winter, but I have not had this problem in any other location. And I do not have the engagement delay on.

I have not had this problem before on either side in any other situation, even for a single turn.

Thanks!


This clearly the case of Army Command do not initiate combat on their own , so I think you have to detached a small unit to attack the militia and the Amry Command will join in the battle

Posted: Tue Aug 21, 2007 11:36 am
by Hobbes
I had this also at the weekend with a (non-Army) Division not attacking when on assault. Could there be a bug? I will double check it tonight.

Cheers, Chris

Posted: Tue Aug 21, 2007 3:55 pm
by Pocus
Can be an unlucky delay, as I said some posts above ;)

Posted: Tue Aug 21, 2007 6:31 pm
by blackbellamy
heroes99 wrote:Army Command does not initiate combat on their own , however they have a chance to join the battle initiate by corps.division ..am I right ...?

In your case I believe the attack must have come from Union side


yeah Armies definitely do participate - they just don't initiate