As we speak of fluid & dynamic I think there maybe something wrong with the "build up" to an attack.
Can't really nail it down but let me describe.
-Started Elsborn Ridge and issued all the battalion attacks.
-I let the 2 Bats south (I of the 27th and I of the 48th) attack in left & right echelon towards Losheimergraben.
-They start moving up to the FUPs(Behidn the rail for 27th and at the T crossing for 48th).
-When the first 2 coys of each bat. hit the FUP the movement task is reported as complete but the 3rd coys(I guess used as rear guard but they don't have that role listed) are still far behind and in road column, these coys deploy and do not move up to the FUP anymore.
-Now the first 2 coys get tasks to switch places with each other while the 3rd should still move up to the FUP. Strange here is that these movement orders are far in the future, 2 first coys hit FUP shortly before 7.00 but these new move orders don't start about a 45 minutes later. In the meantime they are all still listed as moving but deployed
-When they start moving the 3rd coys also start moving again up to the FUPs.
-After moving a bit they get reorg tasks a bit away and move to them, this seems like taking the actual positions for the attack formation.
Anything took so long that the actual attack moves from the Fup didn't start almost 2.5 hours after the initial attack was ordered.
The strange for me is this huge delay between first units hitting FUP and the time the get into the actual attack position, I doubt that the orders delay has somewhat to do with it.
I send the whole save set to firstname.lastname@example.org, I hope that is OK.
You should see what is going on when using Autosave #4.
I have seen this kind of behaviour, but put it down to them moving tactically in the dark/twilight, over very difficult, muddy terrain, in very cold conditions.
I don't know if that is the right answer or not, but am happy to roll play/use my imagination for a delay this short in the grand scheme of things.
< Message edited by dazkaz15 -- 3/29/2013 10:05:08 PM >