From: Living in the fair city of Melbourne, Australia
There would have been a whole Regiment of armour just to the south if they hadn't decided to pull out at the last minute
Could you imagine the kind of reception they would get from the infantry Coy's if they did that for real?
Sorry mate, didn't get that. What regiment of armour? I only see a force the size of a Bn.
I was wondering if the support units should be more closely linked somehow to the Coy's they are attached to.
So that when it stops they do. If it retreats they do.
Is there an orders delay between the support unit, and the Coy it is attached to during an assault?
If there is I think it should be removed, because these 2 units would be working very closely together during an assault when used like this.
If they were deployed further back in a longer ranged support role then I could see the need for an orders delay, but not when working closely like in the assault in this example.
I'm not aware of anything like such an orders delay. Orders delay is modelling the time needed to work out plans and communicate them to subordinates. There are other delays, but these are of a more 'contingent' nature (for instance, a unit needs to take cover because of incoming enemy artillery fires, delaying other units moving in formation).
In CO1, the planning routines are not capable of developing attack plans where a part of the force plays the role of 'direct fire support', as would be fitting for that AT platoon. Such a thing is expected to be done by the player (see the Tutorial, where Dave develops a plan with fire support manually). One of the big jobs for CO2 is extend the current gamut of plans the AI can develop, including developing "fire plans" that take into account units capable of either direct and indirect fires.
< Message edited by Bletchley_Geek -- 2/12/2014 12:48:44 AM >