Ivandrov

To supplement, here's a screenshot of what your TID looks like without the MLC filter. Lots of garbage on the TID from the ground clutter. There is doppler shift happening from these ground objects, but since we know ground objects generally don't move that fast towards or away from around your own airspeed unlike aircraft, the MLC filters these contacts for you to clean things up, with some drawbacks as mentioned. A good RIO can use the MLC filter off even over ground and just tell you to ignore the TID while they find what they are looking for on the DDD. Also, to clarify, "Doppler Shift" refers to the shift in frequency of the radar wave depending on relative closure of the object making the return. Targets moving towards you effectively causes the radar wave to bunch up, increasing the frequency. Targets moving away lengthen the radar wave decreasing frequency. "Zero Doppler Shift" also means zero closure. I.E. you are following a plane that has the same airspeed as you do. Zero doppler filter is actually pretty useful as well, if you are flying in a loose combat formation with friendlies, they won't be added as tracks and added to the TWS firing order on accident.

We've had three different books mentioned as the original source for these diagrams, which one is it?

Eh, I find this to be kind of confusing. What's with the numbered -21 flying through the search areas? The way it's labeled makes it seem like bars are your azimuth. TWS is shown as if it doesn't have a +-40 mode, which it does. STT is shown only in its pulse mode and as a search mode with an azimuth which is not correct. I don't really know what the VSL graphic is supposed to be showing. It doesn't really explain how it works at all. You are also missing PAL and Supersearch.

No, it definitely makes it less pitch sensitive. It's pretty much procedure for our squad to bring them back to bomb mode throughout form up/refueling/leaving.

Hmm, last time I had this problem with my crew we figured it was caused by a lag spike. Same with our Tacview where it looked like everything was normal. So, I would just increase you the formation spread off the Tanker just in case.

Again, you can believe what you want. Heatblur has documentation and SME feedback guiding how they tune the TWS performance and you do not, simple as that. I believe Heatblur unless you can prove otherwise.

I can't link to it either, you would just search for the Tomcat NATOPS on Google. There's one for the F-14B specifically. But that's where the numbers come from. The why of it all is theory gleamed from pilots, as well as some deduction on my end.

Sort of, it's more so that the Meatball is supposed to be calibrated so that for whatever plane is landing, a centered meatball means the hook hits the deck in the optimal spot for a trap The more you deviate from this spot the more of a chance you will just bolter. The non-DLC configuration probably has the hook land a little long if I would have to guess, the suspension would have to compress more for the hook to reach down to the wires.

Yeah, seems about right.

It's entirely possible, I've done it multiple times in an actual game environment. As already said, there's far more processing involved with TWS than RWS. You will notice that you can't hook an RWS contact on the TID for all the juicy information a TWS track provides.

NATOPS can tell you. Without DLC enabled you are about 6 knots slower and you'll be landing at 14 AoA instead. DLC enabled, you are 6 knots faster at a slightly higher 15 AoA from the loss of lift by the spoilers in the neutral position and this configuration is what the hook was designed for.

I don't see how there would be a suprise attack scenario with just the Carrier by itself, as if it's by itself, it would not be ready for flight operations anyway. I've seen them load up the deck with cars for transport for instance when sailing the west coast going to drydock. Other forces are willing to form a group with the Carrier as well like this combined U.S. Japanese group. As far as aircraft deployment, that's pretty close to what they did. Patrols are never just single aircraft, at least 2 a flight. There would be at least one S3 in the air for tanking. The usual loadout was with 2 Phoenix's. The CAP distances could, according to a Tomcat pilot, extend out to over 1,000 miles from the Carrier.

Only one bomber would launch because the radars they need to get the target coordinates for the KH-35's would be blocked by the bomber in front of them. Like I said, it would be a pretty dumb formation, the front bomber would have to fire and then take forever to get out of the way of the next one. Those KH-35's would be picked out of the sky 4 or 6 at a time by the carrier group. Instead what they should be doing which is firing all 24 in the entire formation at once.

And I suppose for the record, the formation you are attempting to defend against would not at all be a formation that these bombers would be using. They have their own radars that would be blocked for the same exact reason.

Example of how a good RIO enhances your awareness. Here is me controlling your track. I'm attempting to offset and the TID still shows one contact. However, if I look at my DDD and hold the IFF button to change the DDD to show range. I can see what is really going on. I can see that there are in fact 4 separate bricks. Well, you can believe what you want. But, you'll need to show some documentation to Heatblur if you want to argue that the TWS performance should be changed.