Notes from a Small Island

[Canoerebel]

Fatigue is low.

I'm not sure what you mean about "rotating patrol."

[MakeeLearn]

ORIGINAL: Canoerebel

Fatigue is low.

I'm not sure what you mean about "rotating patrol."

7.4.1 COMBAT AIR PATROL (CAP) When enemy aircraft are spotted by those aircraft that are airborne or by radar or ground forces assigned to watch for enemy aircraft, all planes available for CAP are scrambled. CAP Aircraft are assigned, but they do not all fly at the same time. They are divided into varying levels of readiness in order to maintain a standing CAP over an assigned target hex. There are three levels of CAP.

Airborne CAP is the most prepared, and can be considered that portion of a group of Aircraft Assigned to CAP that are currently flying at the assigned altitude. There is no delay in this portion of the CAP being in position to intercept an incoming raid.

Ground CAP, is the next level of readiness in the CAP hierarchy. This portion is considered to be on deck to rearm/refuel, or waiting to relieve the Airborne CAP in a ready status. There is little delay in this portion of the CAP Fighters to being airborne and in a position to intercept an incoming raid.

Available CAP is any ready Fighter that is assigned some mission other than “Rest” and can be scrambled in extremis. There is a significant delay in this groups scramble and may be manifested in the Available CAP only being able to intercept a raid AFTER it has struck it’s target. This is the POST TARGET Intercept phase.

[Lokasenna]

ORIGINAL: MakeeLearn

ORIGINAL: Canoerebel

Fatigue is low.

I'm not sure what you mean about "rotating patrol."

7.4.1 COMBAT AIR PATROL (CAP) When enemy aircraft are spotted by those aircraft that are airborne or by radar or ground forces assigned to watch for enemy aircraft, all planes available for CAP are scrambled. CAP Aircraft are assigned, but they do not all fly at the same time. They are divided into varying levels of readiness in order to maintain a standing CAP over an assigned target hex. There are three levels of CAP.

Airborne CAP is the most prepared, and can be considered that portion of a group of Aircraft Assigned to CAP that are currently flying at the assigned altitude. There is no delay in this portion of the CAP being in position to intercept an incoming raid.

Ground CAP, is the next level of readiness in the CAP hierarchy. This portion is considered to be on deck to rearm/refuel, or waiting to relieve the Airborne CAP in a ready status. There is little delay in this portion of the CAP Fighters to being airborne and in a position to intercept an incoming raid.

Available CAP is any ready Fighter that is assigned some mission other than “Rest” and can be scrambled in extremis. There is a significant delay in this groups scramble and may be manifested in the Available CAP only being able to intercept a raid AFTER it has struck it’s target. This is the POST TARGET Intercept phase.

They rotate amongst whatever percentage is set to CAP.

So if you have 90% set to CAP, then 30% of the full unit will be in the air (1/3), 60% will be on the ground/in standby (these are the ones that scramble in the combat reports), and 10% will be available as the final emergency scramble or as escorts (but if range is 0 then no escorts).

[Lokasenna]

ORIGINAL: Canoerebel

It can't be that. All squadron and HQ leaders have good leadership stats. In fact, I spent well over 1,000 PP on leaders over a month preparing for the invasion. Fatigue and morale numbers for the pilots were all very good too.

I wonder if the airfield being overcrowded had an effect? It's level 8 with way more than enough aviation support but more squadrons than there's room for. My experience is that 600 fighters at a level 8 field will result in more downtime for plans that need repairs or maintenance but that it doesn't really effect the fighters that get airborne and most of them will get airborne.

It's still possible that every leader failed checks. Unlikely, but possible.

An overcrowded airfield could perhaps cause this, but that isn't really my experience. I don't overstack bases that will come under attack very often because of the greater risk to the planes while on the ground, but in the few cases that I can remember having done so I do not remember CAP performing any differently than usual.

[Canoerebel]

I know what CAP is but I wasn't sure about your question. I'm still not.

I think you mean this: "Okay, you have 70% of your aircraft on CAP; that's a high percentage, so they get tuckered out and don't have much of a reserve of fresh aircraft to rotate with."

If that's what you mean, it doesn't seem to work that way. You can routine run CAP at 70% or even 100%. As long as range is set to zero, fatigue will be very low. Since the % is set so high, most aircraft are aloft or ready to fly, meaning response times to raids is low (which is what I'm aiming for but not getting, apparently). The drawback is that layered raids - a raid followed by another followed by another may eventually wear out the CAP, since the percentage aloft early is so high, leaving relatively few planes to take on the later raids. That's why I'm using 70% instead of the 100% (like Loka favors, I think).

[MakeeLearn]

IC

Rotation is within the 70%

[MakeeLearn]

Interesting...
tm.asp?m=3605776&mpage=1&key=CAP�

"What is this?"

"Carrier support unable to supply air cover"

"CAP was set for all CV at 70% and fatigue was under 20 (most under 10) for all Fighter AGs. Had good leaders for both the TF and the AGs".

"Many small raids with a large CAP % => yes, your CAP can exhaust itself. Many small raids with a small CAP % and more likely to have CAP, albeit few planes in number, for more raids."

"Think of it this way: your CAP was up and in strength. But after 2 hours, they had to land to re-arm. During the re-armament another strike came in ... no CAP. Happens fairly often to me. My opponent (Andy AI) always seem to hit me with like +20 small, uncoordinated strikes that wears my CAP down."

[HansBolter]

I routinely increase my CAP percentage from the default I operate at of 50% to 70% when faced with a threat.

However, instead of restricting it to range 0, I set it the rest percentage to 30%.

Yes, it means I won't be escorting any sorties, but I am assuming a defensive posture, so the loss of escort is negligible.

With the setting of 70% CAP and 30% rest I can run this setup for days without appreciable fatigue.

[Canoerebel]

I prefer to run CAP at 70% (or higher) at 0 range than to run it at 70% CAP and 30% Rest. Why? Because all fighters are available if needed and fatigue is very low when range is set to zero - always single digits unless combat has occurred. If I need range (for CAP, LRCAP, sweep or escort duties), I adjust things so that fatigue isn't excessive.

[crsutton]

ORIGINAL: Canoerebel

I know what CAP is but I wasn't sure about your question. I'm still not.

I think you mean this: "Okay, you have 70% of your aircraft on CAP; that's a high percentage, so they get tuckered out and don't have much of a reserve of fresh aircraft to rotate with."

If that's what you mean, it doesn't seem to work that way. You can routine run CAP at 70% or even 100%. As long as range is set to zero, fatigue will be very low. Since the % is set so high, most aircraft are aloft or ready to fly, meaning response times to raids is low (which is what I'm aiming for but not getting, apparently). The drawback is that layered raids - a raid followed by another followed by another may eventually wear out the CAP, since the percentage aloft early is so high, leaving relatively few planes to take on the later raids. That's why I'm using 70% instead of the 100% (like Loka favors, I think).

As long as I have good leaders and good radar I will often set my CAP in the 20% range. I get plenty of response this way with planes joining the battle mid fight. And they seem to do fine. High CAP rates seem to sap morale but it just may be the way I am using them. I "never" set my CAP above 50% and then only do %50 rarely. I am usually in the 20 to 40 range. Like I said, if your base is loaded up with good radar, it does not seem to be a concern. I never set my units on rest because I have always thought that units on rest will never participate in a fight. Just a preference but it seems to work fine. If they need rest, I move them to the rear and stand them down. I set the range accordingly only to prevent units from flying escort. I never fly escort with fighters (only by accident), only LRCAP and sweeps over the target. Just goes to show that there are lots of theories and solutions out there.

[Canoerebel]

That's a nifty idea, though I wish I could test it before employing it in such a critical theater. Perhaps I'll try it with a few squadrons to see how it works. It makes sense, though things that make sense don't necessarily translate into things that mechanically work in the game.

[Barb]

His LRCAP and your CAP are mingling it most of the day so less is available to counter any direct attack. However flying LRCAP at high altitude and range >3 costs truckload of fatigue both on pilots and planes. Coupled with your CAP his LRCAP has to be suffering much more than your CAP.

Only options open to you are:
1. Draw his LRCAP away by sweeping enemy target (as you cannot sweep your own bases or ground units)
2. Draw his strikes away by presenting target in different hex (CAP Trap) - set your CAP at range 1 or 2 and offer some DDs next to Shikuka. His LRCAP will stay at hex, while your CAP will be drawn by his Naval Attack away from the LRCAP
3. Increase your CAP presence and/or keep it going. Fatigue will bring his fighters morale down.
4. Strike what he has to protect.

[HansBolter]

In my current game I have had several instances of LRCAP bleeding one hex out of the target hex.

I wasn't aware this was possible.

Perhaps its very high experience levels that make it rarely possible similar to the way high experience pilots can sometimes exceed aircraft range limitations.

It has only started happening in early '44 with squadrons that have 80+ average experience.

[Canoerebel]

6/22/44

Strategic Bombing: Successful Allied nighttime and daytime bombing raid vs. Harbin encounters no fighters and little flak. Thus far, two days of bombing and about a week of recon indicate that Erik doesn't have his flak and fighters well distributed to defend against strategic bombing. It'll be quicker for him to move fighters around. He probably wants to focus on offense rather than defense, so this will increase his desire to strike by air and by sea. I'd rather sit at Sikhalin Island unmolested, so I regret further stirring up the hornet's nest. But the more damage done and the more pressure applied the better. He's coming sooner or later anyway.

AFTER ACTION REPORTS FOR Jun 22, 44
--------------------------------------------------------------------------------
Night Air attack on Harbin , at 109,39


Weather in hex: Partial cloud


Raid spotted at 27 NM, estimated altitude 6,000 feet.
Estimated time to target is 9 minutes


Allied aircraft
Liberator B.III x 10


Allied aircraft losses
Liberator B.III: 1 damaged
Liberator B.III: 1 destroyed by flak

Manpower hits 26
Fires 4680

Aircraft Attacking:
10 x Liberator B.III bombing from 2000 feet *
City Attack: 5 x 500 lb GP Bomb

--------------------------------------------------------------------------------
Night Air attack on Harbin , at 109,39

Weather in hex: Partial cloud

Raid spotted at 17 NM, estimated altitude 5,000 feet.
Estimated time to target is 5 minutes

Allied aircraft
Liberator GR.III x 5

No Allied losses

Manpower hits 28
Fires 17062

Aircraft Attacking:
5 x Liberator GR.III bombing from 2000 feet
City Attack: 8 x 250 lb GP Bomb

--------------------------------------------------------------------------------
Morning Air attack on Harbin , at 109,39

Weather in hex: Light rain

Raid spotted at 34 NM, estimated altitude 10,000 feet.
Estimated time to target is 10 minutes

Allied aircraft
B-29-1 Superfort x 54

No Allied losses

Manpower hits 639
Fires 363300

Aircraft Attacking:
3 x B-29-1 Superfort bombing from 7000 feet
City Attack: 20 x 500 lb GP Bomb
5 x B-29-1 Superfort bombing from 7000 feet
City Attack: 20 x 500 lb GP Bomb
4 x B-29-1 Superfort bombing from 7000 feet
City Attack: 20 x 500 lb GP Bomb
4 x B-29-1 Superfort bombing from 7000 feet
City Attack: 20 x 500 lb GP Bomb
4 x B-29-1 Superfort bombing from 7000 feet
City Attack: 20 x 500 lb GP Bomb
5 x B-29-1 Superfort bombing from 7000 feet
City Attack: 20 x 500 lb GP Bomb
3 x B-29-1 Superfort bombing from 7000 feet
City Attack: 20 x 500 lb GP Bomb
3 x B-29-1 Superfort bombing from 7000 feet
City Attack: 20 x 500 lb GP Bomb
5 x B-29-1 Superfort bombing from 7000 feet
City Attack: 20 x 500 lb GP Bomb
4 x B-29-1 Superfort bombing from 7000 feet
City Attack: 20 x 500 lb GP Bomb
5 x B-29-1 Superfort bombing from 7000 feet
City Attack: 20 x 500 lb GP Bomb
5 x B-29-1 Superfort bombing from 7000 feet
City Attack: 20 x 500 lb GP Bomb
4 x B-29-1 Superfort bombing from 7000 feet
City Attack: 20 x 500 lb GP Bomb

[Canoerebel]

6/22/44

NoPac: Erik has a notion as to the location of my damaged subs. I'm hoping he doesn't know how fast they're moving though. His subs are trailing but getting a bit closer each turn.

[crsutton]

ORIGINAL: HansBolter

In my current game I have had several instances of LRCAP bleeding one hex out of the target hex.

I wasn't aware this was possible.

Perhaps its very high experience levels that make it rarely possible similar to the way high experience pilots can sometimes exceed aircraft range limitations.

It has only started happening in early '44 with squadrons that have 80+ average experience.

I have experienced this a number of times.

[CaptBeefheart]

Can you show us a mouseover of Harbin showing the damage?

Cheers,
CC

[Canoerebel]

Commander, on the turn of the raid, mouseover didn't show any damage. I think that's normal for Manpower raids. Damage should register over following turns as fires burn.

We haven't played another turn since then. Obvert was out of action for a week or more due to family activities. Now his gaming computer is down. I'm not sure when he'll be back up and running, though I'd hazard a guess that within a few days.

[Chickenboy]

ORIGINAL: Canoerebel

Commander, on the turn of the raid, mouseover didn't show any damage. I think that's normal for Manpower raids. Damage should register over following turns as fires burn.

We haven't played another turn since then. Obvert was out of action for a week or more due to family activities. Now his gaming computer is down. I'm not sure when he'll be back up and running, though I'd hazard a guess that within a few days.

How long does it take to show up in your "Strategic VP" slot? If immediate, how has that changed over the past couple days?

[Canoerebel]

There hasn't been a "past couple of days." Obvert went dark on the turn of the raid. He should be back up and running as soon as he has a new computer.