Command Range

[LoneRunner]

Banks Command Range 1.png (759.24 KiB) Viewed 668 times

I may be missing something but is there a reason that Banks command range does not reach the two units marked with X? No units have moved and the weather is clear.

Probably a simple explanation but I can't see it.

[Platoonist]

I've noticed this issue also in bad terrain. I'm not sure, but I think HQ command range is subject to the same penalties as movement. It always reaches farther along roads and railways than it does cross-country. Bank's influence can't reach the brigade just north-west of Alexandria because that unit is currently sitting in two enemy ZOCs and the route back to Banks has to cross the Potomac without the benefit of the direct rail/road connection that the unit in Alexandria has. He can't reach the brigade just south of McDowell because it has to cross a forest hex that is in the ZOC of a Confederate unit. Of course, with better field telegraph technology all these problems could be overcome at this range.

[LoneRunner]

Thanks Platoonist, perhaps you are right, the zone of control, even when weak, appears to affect command range.

However, there's some inconsistencies. For example the command range reaches through the forest hex within the weak zone of control and reaches the hex below the armored train with the black star but doesn't reach the hex below McDowell that's on the road.

Also, the command range reaches through the forest hex and overlaps the CSA unit with the black square, which is within a hard zone of control.

Banks Command Range 2.png (758.48 KiB) Viewed 641 times

[Platoonist]

Yeah, I'm still not 100% sure why the Union brigade NW of Alexandria isn't quite in range. I'm hoping an expert will chime in.

Regarding the hex with the black star, I think the hatching which represents command range always shows theoretical influence regardless of enemy units. That's why it's present under the Confederate unit with the black square. I think that's to prevent players from using the command range hatching graphic as a kind of fog of war lifter. Otherwise, if you saw the command range hatching going really short in the fog of war shroud for no apparent reason, you would know without much doubt that there is an enemy unit lurking in there just out of sight. HQs can't be scouts.

[Hubert Cater]

Looks like there is a bug there, it should only be taking the same things into account as regular movement range minus the zones of control, and in this case it looks like the road southwest of Washington is not reducing the movement penalty of that Land + Sea hex, e.g. it is counting it as 2 movement points, instead of 1 due to the road there.

[Hubert Cater]

The hex southeast of Frederick also marked with an X, does appear to have the HQ range highlight there, but it also appears to show a reddish highlighted hex there as well which almost hides the HQ range highlight.

At least that is what it looks like to me from the screenshot.

[Platoonist]

The hex southeast of Frederick also marked with an X, does appear to have the HQ range highlight there, but it also appears to show a reddish highlighted hex there as well which almost hides the HQ range highlight.

At least that is what it looks like to me from the screenshot.

Isn't that the command overlap with McDowell?

[LoneRunner]

The hex southeast of Frederick also marked with an X, does appear to have the HQ range highlight there, but it also appears to show a reddish highlighted hex there as well which almost hides the HQ range highlight.

At least that is what it looks like to me from the screenshot.

Isn't that the command overlap with McDowell?

Hubert is right. I recreated the situation using hotseat and removed McDowell (see below) and Banks command range reaches both hexes next to Frederick.

Banks Range 2.png (747.35 KiB) Viewed 542 times

Sorry, my mistake. I should have noticed that the command range was hidden by McDowell.