What is this?

[Numdydar]

I have never seen this before. Does anyone know what the heck this means?

[bradfordkay]

Interesting... is the Abukuma in the same hex as a carrier TF or just nearby?

[koniu]

If there is a carrier it must be damaged.
If i am correct carrier is not able to send planes in air if one of damage types is 30+ or summary of all damage types is 50+

[offenseman]

I have seen that message result from a CV group being unable to provide LRCAP due to weather in the CV's hex. So besides damage, that is a possibility as well.

[KenchiSulla]

ORIGINAL: Numdydar

I have never seen this before. Does anyone know what the heck this means?

It means that the carrier is unable to supply CAP..

[Numdydar]

Really? I kind of got that from the message [:)]

I was wondering WHY I got that message, not what it meant. So I guess I should have explained myself better in the OP.

The weather was partial cloud which is shown in the screen so weather is not it. There were multiple CVs in the TF and the CL that was targeted was part of the CV TF. So no LRCAP, etc.

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.

The TF was in open ocean as well so no costal/base hex nonsense either.

Since I had never seen this message in all the times I have played the game, I was hoping someone here could shed some light on what happened so if it was something I did (or did not do) it would not happen again.

[oldman45]

For what ever reason, the cap was not able to get into position when the attack came in. There are too many variables at play here to give a specific answer. I have seen that message many times over the years and it has been on account of weather, number of enemy raids, damage to the base/carrier, or bad luck and the planes were just not in range to reach the target in time.

[offenseman]

The weather was partial cloud in the hex the CL Abukuma was located in. Unless the CVs were in the same hex, that does not mean the CVs had flyable weather. Was the weather partial cloud in the hex the CVs were in?

[geofflambert]

I've not seen that message when the carrier(s) are in the same hex with the covered TF. Has anyone else?

[Numdydar]

Just to be clear the CL was IN THE SAME TF AS THE CVS.

[btd64]

Numdydar, Maybe the size of the incoming strike was so small that it was not picked up in time. Do you have radar? Just a though.[:)] GP

[Numdydar]

Considering the screenshot shows 19 mins before the raid shows up I seriously doubt that is it either.

[geofflambert]

Your experiences must be superior to mine, I don't know how many times I've cursed a blue streak at squadrons doing nothing when my plan depended on them doing something. [:D]

[wdolson]

The message goes into the report if there was a carrier in range, but there happened to be no CAP airborne at the moment of attack. Airborne CAP might get exhausted with a previous wave and the carrier hadn't launched new CAP to replace them yet. I would guess it might also happen if the fighter squadron was not set to CAP or the CAP percentage was very low.

Bill

[Chickenboy]

ORIGINAL: geofflambert
Your experiences must be superior to mine

Yes. They likely are. As a matter of fact, I'd attest to this as a certainty. [:'(]

[Czert]

ORIGINAL: Cannonfodder

ORIGINAL: Numdydar

I have never seen this before. Does anyone know what the heck this means?

It means that the carrier is unable to supply CAP..

Ty, captain OBVIOUS.

[geofflambert]

ORIGINAL: Chickenboy

ORIGINAL: geofflambert
Your experiences must be superior to mine

Yes. They likely are. As a matter of fact, I'd attest to this as a certainty. [:'(]

I can attest to having won more than one chickenboy plucking contest. [:'(]

[Numdydar]

ORIGINAL: wdolson

The message goes into the report if there was a carrier in range, but there happened to be no CAP airborne at the moment of attack. Airborne CAP might get exhausted with a previous wave and the carrier hadn't launched new CAP to replace them yet. I would guess it might also happen if the fighter squadron was not set to CAP or the CAP percentage was very low.

Bill

Thanks so much Bill. "there happened to be no CAP airborne at the moment of attack. Airborne CAP might get exhausted with a previous wave and the carrier hadn't launched new CAP to replace them yet" must be the answer. I noted in Post 6 that CAP was at 70%.


I had no idea that the CV could actually run out of the ability to launch CAP versus running out of planes in the air flying CAP. The latter happens pretty often but the other must be very rare as it is the first time I have even seem it.

So it seems like for this message to occur.

The CV has planes available to launch on CAP
A lot of small raids attacked the CV TF (which did happen in this case)
However, some magic and hidden number was reached (which I will now name CV OP Number) where, if exceeded, no further aircraft operations are allowed by that CV. Even if CAP planes are available to fly.

This number seems to be CV based and not TF based given the message text. So it is good to know that nothing I did or did not do caused this to occur. Also it is good to know that you can exhaust a CV's ability to launch planes that has nothing to do with the sortie number since CAP does not count against the number of sorties you can fly.

Given this a bunch of small raids could be more effective than 1-2 large ones. Be interesting to try out [:)]

[geofflambert]

I don't know if this is relevant. I've never seen (or noticed) this message in reference to my forces. My usual CAP % is 30. Sometimes I go to 40% and only in very rare situations do I go to 50%. Could putting too large a percentage of the unit on CAP lead to this, or at least be one reason why it might happen?

[PaxMondo]

ORIGINAL: Numdydar

ORIGINAL: wdolson

The message goes into the report if there was a carrier in range, but there happened to be no CAP airborne at the moment of attack. Airborne CAP might get exhausted with a previous wave and the carrier hadn't launched new CAP to replace them yet. I would guess it might also happen if the fighter squadron was not set to CAP or the CAP percentage was very low.

Bill

Thanks so much Bill. "there happened to be no CAP airborne at the moment of attack. Airborne CAP might get exhausted with a previous wave and the carrier hadn't launched new CAP to replace them yet" must be the answer. I noted in Post 6 that CAP was at 70%.


I had no idea that the CV could actually run out of the ability to launch CAP versus running out of planes in the air flying CAP. The latter happens pretty often but the other must be very rare as it is the first time I have even seem it.

So it seems like for this message to occur.

The CV has planes available to launch on CAP
A lot of small raids attacked the CV TF (which did happen in this case)
However, some magic and hidden number was reached (which I will now name CV OP Number) where, if exceeded, no further aircraft operations are allowed by that CV. Even if CAP planes are available to fly.

This number seems to be CV based and not TF based given the message text. So it is good to know that nothing I did or did not do caused this to occur. Also it is good to know that you can exhaust a CV's ability to launch planes that has nothing to do with the sortie number since CAP does not count against the number of sorties you can fly.

Given this a bunch of small raids could be more effective than 1-2 large ones. Be interesting to try out [:)]

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. I shoot down a ton of his planes, but in the end he will put 6 - 8 torps into my ships and send me into the yards for +12 months. [:(]