Matrix Games Forums

The best and nearest Air HQ can be used to help increase the number of groups that can be 'administered'.
[Air HQ of same command as the base will use its full command radius value, or half it if of a different command.]

In addition, the nearest Command HQ (within 2 times command radius) can also help.
[If base belongs to same Command or base is within radius, then it uses its full radius value, or half if not same.]

In addition, the nearest Command HQ (within 2 times command radius) can also help.
[If base belongs to same Command or base is within radius, then it uses its full radius value, or half if not same.]

The seaplanes affecting coastal AF is something that I had not originally set aside due to the problems of trying to split land base and sea planes when a base only had the one 'aircraft' counter.
This is not the problem it was as I now have to recalculate the numbers on the fly.

Manual page 214: An overstacked airfield affects how many aircraft can be launched, casualties from attacks
and aircraft repairs.

groups at rest or in training only count as 1/3 for the purposes of counting aircraft
at the base, and don’t count at all against the number of groups. Split groups only count as
individual groups if they are attached to different HQs.

Groups present at base is based on:
1. All groups at rest/training count as 1 group
2. Detachments are not counted if the parent group is in base and has same HQ as the detachment
3. All fragments and Chutai, Section or flight groups count as 1 group
4. The units of a split group in the same base count as 1 if all have same HQ
5. Any case counts as 1
(c) if counted groups larger than admin stacking limit, then over-stacked.

ORIGINAL: michaelm

Lack of AV support is not directly tied to over-stacking.
The lack of support will be felt with slower repair/readiness of aircraft, and operational limits to launched aircraft.

ORIGINAL: Al Boone

bump, please when time allows for answers to my questions above in post #22 of this thread.

Also there is confusion as follows:

Manual page 214 -

groups at rest or in training only count as 1/3 for the purposes of counting aircraft
at the base, and don’t count at all against the number of groups. Split groups only count as
individual groups if they are attached to different HQs.

From michaelm (from earlier in this thread) -

Groups present at base is based on:
1. All groups at rest/training count as 1 group
2. Detachments are not counted if the parent group is in base and has same HQ as the detachment
3. All fragments and Chutai, Section or flight groups count as 1 group
4. The units of a split group in the same base count as 1 if all have same HQ
5. Any other case counts as 1
(c) if counted groups larger than admin stacking limit, then over-stacked.

These statements seem to conflict. Can they be clarified or the correct case identified and explained better?

ORIGINAL: Al Boone

Overstacking by administration "groups" - from response by michaelm

The best and nearest Air HQ can be used to help increase the number of groups that can be 'administered'.
[Air HQ of same command as the base will use its full command radius value, or half it if of a different command.]

I assume that the base must still be within the combat radius of this best and nearest Air HQ? yes. Except for command hq where it can be twice the radius.
If not, what is the maximum range? (and see next question relative to similar situation)

In addition, the nearest Command HQ (within 2 times command radius) can also help.
[If base belongs to same Command or base is within radius, then it uses its full radius value, or half if not same.]

If the base does not belong to the same command and is located between Combat Radius distance and 2 times combat radius distance, is the enhancement = ½ CR x ½ CR = ¼ Combat Radius, or does it become 0?
Only 1/2 applies once. The case is "not in same command" OR "more than normal radius".

In addition, the nearest Command HQ (within 2 times command radius) can also help.
[If base belongs to same Command or base is within radius, then it uses its full radius value, or half if not same.]

An effort should be made to more widely broadcast the above rule which was added after manual printing. It definitely should be added to future manual addenda for page 214.

The seaplanes affecting coastal AF is something that I had not originally set aside due to the problems of trying to split land base and sea planes when a base only had the one 'aircraft' counter.
This is not the problem it was as I now have to recalculate the numbers on the fly.

From this, do I assume that the inclusion of seaplanes is under review for possible future change relative to airfield overstacking? For now, is it handled as I have suggested above?
Seaplanes will be excluded from physical stacking if in a coastal hex from patch01.

Manual page 214: An overstacked airfield affects how many aircraft can be launched, casualties from attacks
and aircraft repairs.

Is it unlikely that we will ever get any even vague idea of the degree of overstack penalties associated with launches, casualties and repairs?

ORIGINAL: Jonathan Pollard

ORIGINAL: michaelm

Lack of AV support is not directly tied to over-stacking.
The lack of support will be felt with slower repair/readiness of aircraft, and operational limits to launched aircraft.

Is the "operational limits to launched aircraft" a change from stock WITP? I don't remember right now if there used to be any effect on operational limits to launched aircraft in the earlier version.

Manual page 214: An overstacked airfield affects how many aircraft can be launched, casualties from attacks
and aircraft repairs.

ORIGINAL: John Lansford

So what does a red "number of squadrons" value on the air transfer screen indicate?  I've seen that in the past and had assumed there were too many squadrons there at that particular base.