Matrix Games

quote:

ORIGINAL: BigDuke66

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 contact@panthergames.com, I hope that is OK.
You should see what is going on when using Autosave #4.

quote:



ORIGINAL: Arjuna

The messages "stalled and waiting", "stalled and bypassing" an "stalled and replanning" were introduced in the last build. These all relate to cases where the subject of a Move task comes within threat range of an enemy ( 1000m plus unit radius ) and where the subject is a senior HQ (ie. Bde and above) or a Base for any type of Move task or is a support unit or any type of HQ conducting an advance to the Reserve position as part of an attack. If Bypass is allowed they will try to bypass. They may get several attempts at bypassing as sometimes the bypass route may not get them out of threat range. In such cases they will wait till the next attempt. With each attempt they increase the caution factor of the route thus giving a wider berth around known threats. If they can't bypass either because the option is not checked on the order setting or they just can't get a suitable route, then they will replan. This may not help. It depends on the orders they have and the situation around them.

So if you see these messages take a good look at the subject's situation and if necessary change its orders. HQs and support units are not meant to be placed in harms way.

The message "stalled attack" has been in the engine in for quite some time and relates to cases where an attack has failed to make progress. If the stalled force is part of a complex attack then it will bunker down leaving other subAttacks to continue. If it's just part of a basic attack then it will replan.

quote:

ORIGINAL: BigDuke66

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 contact@panthergames.com, I hope that is OK.
You should see what is going on when using Autosave #4.