ORIGINAL: Bullwinkle58
I guess I'm confused still. The air stuff always does that to me.
I looked in my archives for both my games. I don't have very many cases where I had CAP up, there was more than one attack on a base, and some of the CAP survived to meet the second attack. But in every case I found the CAP was at the patrol altitude--"teleported" in Erik's terms--when the second attack began. If the Oscars were assigned to 38,000 feet and my poor P40Es were at 15,000 that was the case at the start of both reports. As has been said many times the attack queue isn't really consecutive. It's reported that way in the animation, but it's not one run, then the next, then the next. Losses carry forward, but it's not as clean as it looks time-wise.
What negative modifiers do escorts get? I truly don't know. Learning opportunity for me. I think that they're tied to their strike package and don't loiter might be what he means, and that's true, but the fatigue accumulation for LRCAP is much higher than for Escort in the other direction. And 100% of the LRCAP percentage isn't there 100% of the time in both day phases. That's a disadvantage. I have always looked at LRCAP as a sometime thing. I'd rather do sweeps and not have them tied to bomber timing, or do pure escort and make the fighters ablative. LRCAP has always seemed the worst of both worlds in offense. In defense LRCAP can make sense, especially when dissimilar sized AFs are in the mix. But I watch the fatigue.
Haha, you know what? I never thought about the teleporting CAP. Excellent observation! [:D]
To be honest I don´t know anything about the penalties given to escort besides the fact that its there. Having used escorts exclusively for almost two years now I can say that my experience mirrors that of Millers. Anything used for escort have a life expectancy of basically nil. My above Manila strikes are a good example. Whether or not the Corsairs are CAP from the CVs or LRCAP you can see in the first strike just how badly the P38s on escort were mauled compared to the Corsairs.
Besides having some sort of negative modifier attached to the mission itself you also have the height disadvantage. The CAP will dive on the escorts causing further losses.
I have played as you have using sweeps followed by escorted bombers. The worked very well in 43 and early 44 when the quality of allied fighters (P47s/Corsair) was so much better than Japanese Georges and Tojos. Now in late 44 and forward I´m facing a complete wall of basically thousands of Franks. At Saigon there were 900 fighters on CAP at most.
If you send a lone sweep (25 planes) against 900 fighters on a layered CAP you will get beat up. So at this point I started adding LRCAP to the sweeps and did remarkably better. The problems with this is our stupid "agreement" about not using LRCAP for pure escort. LRCAP is almost impossible to control as I said before. This one of the biggest reason I avoided using it. That and the insane fatigue. This time I used 200 planes on LRCAP above Manila but the sweeps (and possible the LRCAP) rained in. Thus the bombers took off in the AM phase before the sweeps had cleared the CAP. So now my bombers possibly got "LRCAP escort" and here we are...
Its not like I would have like this to go in before the bombers...[8|]
--------------------------------------------------------------------------------
Morning Air attack on Manila , at 79,77
Weather in hex: Heavy cloud
Raid detected at 79 NM, estimated altitude 38,000 feet.
Estimated time to target is 21 minutes
Allied aircraft
P-51B Mustang x 49
P-51D Mustang x 124
F4U-1A Corsair x 11
F4U-1D Corsair x 72
No Allied losses
Aircraft Attacking:
25 x P-51D Mustang sweeping at 32000 feet
25 x P-51D Mustang sweeping at 32000 feet
24 x P-51D Mustang sweeping at 32000 feet
25 x P-51D Mustang sweeping at 32000 feet
25 x P-51B Mustang sweeping at 32000 feet
25 x P-51D Mustang sweeping at 32000 feet
24 x P-51B Mustang sweeping at 32000 feet
--------------------------------------------------------------------------------
Morning Air attack on Manila , at 79,77
Weather in hex: Heavy cloud
Raid detected at 79 NM, estimated altitude 38,000 feet.
Estimated time to target is 21 minutes
Allied aircraft
P-38L Lightning x 15
P-47D2 Thunderbolt x 25
P-47D25 Thunderbolt x 25
P-51B Mustang x 48
P-51D Mustang x 75
F4U-1A Corsair x 11
F4U-1D Corsair x 30
No Allied losses
Aircraft Attacking:
25 x P-51D Mustang sweeping at 32000 feet
25 x P-51D Mustang sweeping at 32000 feet
25 x P-51B Mustang sweeping at 32000 feet
23 x P-51B Mustang sweeping at 32000 feet
25 x P-47D2 Thunderbolt sweeping at 32000 feet
25 x P-51D Mustang sweeping at 32000 feet
25 x P-47D25 Thunderbolt sweeping at 32000 feet
EDIT: Looking at the above sweeps it actually enhances my belief that the possible LRCAP shown up over Manila is infact NOT LRCAP set for Manila at all. Looking at the number of the last bombrun that "LRCAP" is absolutely fatigued/shot down and is down to just a couple of planes. But in the first sweep there are 72 Corsair "1Ds" present. The only model set to LRCAP Manila directly was "1Ds".
I also came up with another possible source for the Manila "LRCAP". I have a big convoy unloading at Batangas 1 hex south of Manila. That TFs is LRCAPed from iloilo and consists of Lower EXP "1As" and "1Ds" doing CAP/LRCAP to gain EXP. Its very possible that LRCAP "strayed" into Manila.
This just further enhances the problem with having a HR/agreement that tries to limit LRCAP. You can NEVER tell for sure where the LRCAP comes from except looking at where the losses occurred after the turn. So I could just set a massive LRCAP over a nearby TF fully knowing it will stray to where I want it. Or I could simply set the the LRCAP to where I want it and then tell my opponent it must have strayed from somewhere. And he could never tell whether I was lying or not. Its just an impossible HR/Agreement. Simple as that.