Page 1 of 1

This is going to be a fight

Posted: Mon Jun 26, 2006 7:19 am
by Crimguy
Just about to have my final assault in the Charge of the Centaurs scenario. About 6500 troops are taking part in the first assault (pictured). Another 5000, led by the XXV Corps, hopefully will make it to the mountain beyond after the 23rd Division's troops soften the enemy's lines.

Should be a hoot. I'm getting nervous just watching them reorganize.

Image

RE: This is going to be a fight

Posted: Mon Jun 26, 2006 11:57 am
by pvthudson01
holy cow! That will be one heck of a fight! Let us know the numbers involved when its all said and done

RE: This is going to be a fight

Posted: Mon Jun 26, 2006 1:36 pm
by Real and Simulated Wars
Wow! Let us know what it did go.
 
 

RE: This is going to be a fight

Posted: Mon Jun 26, 2006 6:04 pm
by Trigger Happy
CVan you put a little more general screenie to see where it is happening. I remember having to do the something similar, but only to try to take the crossroad. I would have had a clear route had it worked... unfortunately it did not. [:(]

RE: This is going to be a fight

Posted: Mon Jun 26, 2006 6:21 pm
by MarkShot
What I find most agonizing when assembly large attacks (which are often intended to kick off right before dawn) is when FUPing drags on and on and the sunrise approaches ... that feeling of dread as the first faint rays shoot out between the hills ... all of a sudden that hollow shrieking sound followed by the first muffled thuds ... shouts of "incomming" ... sometimes the dawn just seems to come too quickly ... if you know what I mean.

RE: This is going to be a fight

Posted: Mon Jun 26, 2006 9:08 pm
by Banquet
ORIGINAL: MarkShot
all of a sudden that hollow shrieking sound followed by the first muffled thuds ... shouts of "incomming" ... sometimes the dawn just seems to come too quickly ... if you know what I mean.

Yep.. and that's just the girlfriend getting up and finding me still playing CotA at 7am [:D]

RE: This is going to be a fight

Posted: Mon Jun 26, 2006 11:31 pm
by Crimguy
ORIGINAL: MarkShot

What I find most agonizing when assembly large attacks (which are often intended to kick off right before dawn) is when FUPing drags on and on and the sunrise approaches ... that feeling of dread as the first faint rays shoot out between the hills ... all of a sudden that hollow shrieking sound followed by the first muffled thuds ... shouts of "incomming" ... sometimes the dawn just seems to come too quickly ... if you know what I mean.

If you look on the screenie, you can see that dusk is approaching. This one took 2 days to get going due to reinforcements repeatedly showing up, forcing reorganizations.

RE: This is going to be a fight

Posted: Tue Jun 27, 2006 3:58 pm
by Agema
Heh, I once planned a brigade assault, reckoned it would take 2 hours for orders delay, give an hour or two to form up, and hour to cross some open ground without beng seen, and dawn would break with me 500-1000 metres away from the target. My troops had just started off from the FUP when dawn broke, and I barely got half-way before nearly all of my lead companies were broken by artillery, and enemy reinforcements flooded in long before I reached the objective. Lost 1/8th of my brigade to little effect. [:(]

That experience got neatly filed away under "more preparation time needed".

RE: This is going to be a fight

Posted: Wed Jun 28, 2006 1:19 am
by Deathtreader
ORIGINAL: Crimguy
ORIGINAL: MarkShot

What I find most agonizing when assembly large attacks (which are often intended to kick off right before dawn) is when FUPing drags on and on and the sunrise approaches ... that feeling of dread as the first faint rays shoot out between the hills ... all of a sudden that hollow shrieking sound followed by the first muffled thuds ... shouts of "incomming" ... sometimes the dawn just seems to come too quickly ... if you know what I mean.

If you look on the screenie, you can see that dusk is approaching. This one took 2 days to get going due to reinforcements repeatedly showing up, forcing reorganizations.


Hi all,

I've noticed something like this before.........and its annoying as hell. [:@]
Is there anyway to stop reinforcements from constantly forcing replans when all you want to do is attack with what's already at hand?? If not, then shouldn't there be?? Look what happened at Kursk. The constant replanning etc. delayed the offensive by months. An extreme example to be sure but is the logical extension of the 2 day delay mentioned above.
A wishlist item perhaps? [:)]
Regards,

Rob.





RE: This is going to be a fight

Posted: Wed Jun 28, 2006 1:25 am
by MarkShot
Reinforcements don't force replans, you do.

If you don't want a replan, then don't attach them to their organic command when they arrive. Find some other mission for them.

However, I do believe that for COTA some threshold was put in the code such that a detach/attach may not cause a replan if the sub-force involved is relatively small enough. Dave would be able to shed some light on that. Myself, I always assume that any force changes will result in a replan.

RE: This is going to be a fight

Posted: Wed Jun 28, 2006 3:50 am
by Crimguy
Then I don't know what the hell was taking so long.  I just sat there watching them for two days as they seemed completely unable to get their act together.  As luck would have it, their attack started at 0715, and they've been putting up a gallant fight on into the day (it's now 1330)>  I'll keep you posted.

RE: This is going to be a fight

Posted: Wed Jun 28, 2006 6:46 am
by Crimguy
Well, the battle dragged on to the very end, with little to show for it. 6500 Greeks and Brits died, while 7400 valient Italians lost their lives. The two assaults sputtered and stalled at Kalpaki crossroads. The hill wasn't taken until early on day 9, and no other major objectives were achieved.

I did note that one of my divisions replanned their assault when we failed to open the road to the furthest objective - they sent two brigades wide right, across 2 rivers, and attempted to flank their objective. That, of course, was a tremendous waste of time, and their guns would have been more useful in the fighting as opposed to swimming. I also noted one of my divisions managed to get wayyyy ahead of the main force, almost to the southernmost objective, while the rest of his troops were about 6 clicks north. Pretty weird. I'm wondering about the coding as I saw some erratic behavior on the part of more than one of my brigades - regiments being separated from their commanders by 10 clicks was not uncommon.

Image

RE: This is going to be a fight

Posted: Fri Jun 30, 2006 12:34 am
by Fallschirmjager
It would be nice if in future versions we could specify a time for an attack or any order for that matter to kick off. This way you could plan well ahead of time and then hopefully your unit would move at the time you specify.
Of course this would have a chance of breaking down, but it would be very nice.

RE: This is going to be a fight

Posted: Fri Jun 30, 2006 2:34 am
by Crimguy
It was requested numerous times after HTTR came out.  I'm sure it's on the wishlist.

RE: This is going to be a fight

Posted: Fri Jul 21, 2006 1:57 am
by Deathtreader
ORIGINAL: Deathtreader

ORIGINAL: Crimguy
ORIGINAL: MarkShot

What I find most agonizing when assembly large attacks (which are often intended to kick off right before dawn) is when FUPing drags on and on and the sunrise approaches ... that feeling of dread as the first faint rays shoot out between the hills ... all of a sudden that hollow shrieking sound followed by the first muffled thuds ... shouts of "incomming" ... sometimes the dawn just seems to come too quickly ... if you know what I mean.

If you look on the screenie, you can see that dusk is approaching. This one took 2 days to get going due to reinforcements repeatedly showing up, forcing reorganizations.


Hi all,

I've noticed something like this before.........and its annoying as hell. [:@]
Is there anyway to stop reinforcements from constantly forcing replans when all you want to do is attack with what's already at hand?? If not, then shouldn't there be?? Look what happened at Kursk. The constant replanning etc. delayed the offensive by months. An extreme example to be sure but is the logical extension of the 2 day delay mentioned above.
A wishlist item perhaps? [:)]
Regards,

Rob.





Hi,

Thanks for the reply MarkShot but if I give them a direct order then I up my command load. If I don't then I face the possibility of replans with attendant delays just when I don't need or want them. Couldn't there be a generic "Advance to superior HQ at normal speed via fastest route" or something for all reinforcements when they 1st hit the map?? Maybe with a timelimit to override the default or something. I don't know...
Bottom line is that replans shouldn't happen simply because an anti-tank platoon arrives at map edge and forces an attack to be re-calced. Just my opinion. Still love the game. [:)]

Rob.


RE: This is going to be a fight

Posted: Fri Jul 21, 2006 3:10 am
by Arjuna
Rob,
 
In fact that is exactly what should happen if the size of the force is not a major addition - eg if an AT Pl arrives for a Bde. But if a Bn arrives for the Bde then it will replan. The argument here being that such a significant addition may enable the force to undertake an alternative plan that was previously unavailable.

RE: This is going to be a fight

Posted: Fri Jul 21, 2006 5:49 am
by Grotius
Cool screenshots, in any case. :)