Slitherine

quote:

ORIGINAL: MarkShot

Glad you enjoyed it!

Now, get out there and give some orders before you're surrounded!

quote:

Here is a situation that makes me mad:

I need to hold on to an objective, so I garrison it with appropriate forces. Then the damned AI blast them continuously with some damn heavy arty hidden somewhere in the bushes God knows where. It's an easy target for him since they are immobile at the objective. This makes me crazy.

I sent 1 or 2 units in recon in the area to try to spot the bastards but to no avail (my recon units get repulsed easily as soon as they meet some opposition).

What do you do guys in such a situation? I am now thinking about gathering a task force to go around and clean up forcefully the whole area, but this is a long process and my forces are stretched thin for now anyway (I am playing the Eindhoven Campaign as Allies, and I need to hold on all the objectives placed along the highway, so I don't have much forces to spare beating the bushes around the highway).

quote:

ORIGINAL: MarkShot
(1) Give priority to those objectives which are wooded or BUA. These areas will be the hardest to take if the enemy gets time to dig-in. So, make sure that you are the one who gets time to dig-in.

quote:

Page 41 of states that you can have arty provide on-call support by issuing a [D]efend task and adjust ROF as per your requirements. This is incorrect ROF will always be LOW. The only way to adjust ROF for bombard capable units is manually issue [B]ombard orders.

quote:

ORIGINAL: MarkShot

ROF was hardcoded to low so that arty would not run out to rapidly; as I understand it.

quote:

Para rescue? (in reply to MarkShot)

I haven't been able to get better than a draw on this scenario as the Allies. How do you do better?

When I go straight to the Son Bridge it gets blown up every time. Same with the bridge to the east. I find the only way I've been able to secure the bridge intact, and secure the area, is to go waaay east, cross at the unprimed road bridge, and Assault from the East. I can secure the bridge and the obj, but I do not have the strength to take the northern obj.

Any tips?

quote:

ORIGINAL: Paul Roberts

This raises a further question: what is the cost of attacking when you could just move? Why should we ever use move instead of attack?

I'm assuming that move orders take less time to plan and fulfill, but I'd like to make sure. Does an attack order cause more fatigue even when no enemy is encountered?

quote:

ORIGINAL: MarkShot

You have already answered your own question. Move is faster (no FUPing) and a lot less stressful.

quote:

ORIGINAL: Golf33

In a Move, all units will travel in formation. They will also prioritise fire over movement. In an Attack, some units will remain behind in the reserve location. Units in the actual assault will prioritise movement over fire.

In a Move, your Speed setting will affect how fast all units travel along the entire route. In an Assault, your speed setting will only affect the move to the FUP; the assault will always be undertaken at Fastest speed.

In a Move, your Aggro setting will affect whether your units attempt to bypass (low Aggro) or deploy and engage the enemy (high Aggro). In an Attack, your Aggro setting will only influence what proportion of the force gets held in reserve (I think, have to double-check this one).

In a Move, your units will follow the path you specify, with the Route type you specify, along the whole route. In an Attack, your units will follow the path and Route type you specify to the FUP, but will always follow a Shortest path from there to the objective.

There are some considerations to start you off!

quote:

ORIGINAL: MarkShot

Steve,

In your very detailed analysis, you neglected to mention that forces ordered to [A]ttack are not required to pay parkway tolls at the toll plazas unlike forces which are simply ordered to [M]ove.

quote:

ORIGINAL: madmickey

One thing that you can do with a move is change the formation type and aggression level without order delay. I also assume that transition time for deploying armor units is faster than for infantry therefore quick moves to control open territory is much better with tanks. Still if I have a 30 combat power formation Is it a waste to attack a 1 combat power unit especially if I am worrying about the enemy moving reinforcement in the time it take me to launch the attack.

Steve Golf33 Long

quote:

ORIGINAL: Mr.Frag

even a move command is subject to a reorg phase unless you specifically order a formation type of In-Situ (ie: go as you are).

quote:

ORIGINAL: Golf33
Moves aren't subject to a reorg phase as such, but on beginning a Move, they will shake out into whatever formation they have been ordered to adopt which will take a few minutes. It's still not generally the lengthy and vulnerable reorg that happens before an Attack though.

If you order Move In-Situ your troops will stay where they are. I occasionally use this to halt a move already in progress, by setting the formation to In-Situ; doing this does seem to incur orders delay however, as does restarting the move by selecting a different formation. Changes that don't require the whole formation to stop do seem to happen without delay.

quote:

ORIGINAL: Arjuna

If you set the formation type to in-situ for a Move, the force/unit will just stay where it is. It won't more at all. So don't use it for a Move task. ( Perhaps we should make it inactive for a Move task. I'll add that to the wish list ).

Further, a Move is one simple task conducted from the units current locations to the objective. An attack is a complex network of tasks one of which will be an advance to an FUP where units reorg and shake out into assault formation. This reorg does not take place in a straigt Move task. The only reorg task which may be imposed on any other task occurs involuntarily when a unit/force's cohesion is so bad that it must stop temporarily and organise itself.

Steve Golf33 Long

quote:

ORIGINAL: Mr.Frag

Ok, now I am royally confused ... why would an order to move NOT be subject to the very same sets of delays that an attack would be except for the actual timing of the kickoff?

Are you saying that I can effectively bypass Painfully realistic orders by running around with line formations each pointed at their own personal spot coordinated by my mouse instead of the command HQ? That doesn't sound right.

quote:

ORIGINAL: Golf33

This is a confusion of terminology. In HTTR, the term "Reorg" refers to a specific type of activity - the reorganisation - which occurs in four specific circumstances only. Units conducting a Reorg are shown with the reorg symbol in the unit task icon ("F4" key). Units will conduct a Reorg only under the following circumstances:

1. After a reinforcement arrives by parachute/glider/aircraft.
2. When a unit's cohesion becomes too low.
3. When ordered to reorg by the player using the Reorg command (hot key "R").
4. When the unit has an Attack task and has reached the FUP, prior to beginning the assault.
<edit - thanks to MarkShot for the reminder:
5. When the unit has an Attack task and has completed the assault and is securing the objective.>

This is separate from Orders Delay, shown as a pink background to the task icon. All fresh orders from the player incur orders delay. Under some circumstances, changing the parameters (Speed, ROF, Aggro, Formation etc) of an existing order may not incur orders delay. Some situations which generally don't incur orders delay are listed below. The list isn't complete, so there is still room for you to experiment and discover some of this for yourself, but in general anything not specifically mentioned below will probably incur orders delay.

Move task
Changing Speed, Route, Aggro, ROF, and Losses.
Changing Frontage, Depth, and Facing.
Changing Formation, except for In-Situ, which does incur orders delay. If you set a Move-ing force to In-Situ, it will incur orders delay, and any further changes you make will not take effect until after it has processed the In-Situ formation order. Similarly, once the force has processed the In-Situ order and stopped moving, if you change the formation type, it will again incur orders delay and once it has processed the change it will start moving again.

Defend task
As for Move tasks.

Attack task
Changing Speed, Route, ROF, and Losses.
Changing Frontage, Depth, or Facing.
Changing Formation (except for In-Situ) during the move to FUP, or sometimes but not always during the assault.

Changing the objective of any task (i.e. the location of the final waypoint, the one that shows the task type), or the FUP of an Attack task (which shows the Reorg task), will always incur orders delay. Like setting In-Situ, no other changes to the order will be processed until after the new location has been processed. However, intermediate waypoints (the ones shown by a small circle with an upward-pointing arrow in it) can be moved without incurring orders delay - so if you are looking to bypass any resistance on a Move, or during the move to FUP phase of an Attack, it's a good idea to plot the route using waypoints every 1000-2000m and send a scout unit ahead. When the scout discovers enemy defences, you can move the waypoints to bypass the enemy.

Steve Golf33 Long

quote:

Hi all,
Started the game a couple of weeks ago. Nice game. What I'm getting confused about is when I set waypoints. From A to B I would like to Probe between the points At B reorg and Assault to C. Only the last action is implemented. Did I miss the explanation in the manual? Is the move from A to B Probe by default?

Lifer

quote:

Lifer,

The game does not implement actions specific to each waypoint. I think Dave had put this on the wishlist for me.

It sounds to me like you are trying to combine the actions of recon and attack together. What I do:

(1) Use a single unit recon element to evaluate whether the route is open and that the FUP is safe for use. The unit terminates its travel at the FUP and keeps an eye on it. I use the [D]efend command for this.

(2) Follow the recon up with an attack order to a force to take the same route and FUP where the recon unit ended. Often you can issue these orders concurrently, since the recon will happen much faster. Later, if there are problems you can change the force's orders. Also, at the start of the game or with reinforcements, you generally have 58 minutes to conduct fast recon and issue orders on the the 59th. minute with no delays. (assuming that you are playing with order delays)