Ivandrov

The MPRS unit in the mission editor does not use its boom at all. It only refuels with the drogues for Navy aircraft.

Question 1: There's probably an actual answer for it, but in my experience it stops the aircraft from wanting to pitch up on you as you increase speed faster than the wing sweep schedule can keep up with. It's one less thing to have to fight the pitch up with trim as you are doing the pattern. Question 2: Would have to see a track to know what exactly you are talking about. Not sure why Chuck's is saying not to use the stick for pitch adjustment. You absolutely should be using the stick for pitch adjustment during the landing while you adjust the trim. (Trim adjusts the center point of the stick, so trim nose up or down can be thought of as slower stick movement for pitch.)

Not able to replicate the RCS bit. Still can only detect them at about 100-110nm.

I do not have the track for it. You can see up in the top left in the Tacview where it says AIM-54C has destroyed TU-22M3. The parameters of the Phoenix in the screenshot match the plane, was going about Mach 2.1.

TU-22M3 is capable of higher than that. About Mach 1.88 in DCS. Here's the shot I took.

Yeah, that looks about right. Don't try to use it as the primary flight instrument, it's not meant to be used for more than an eyes up reference. It'll be slightly off more often than not. A: Not at the moment B: Aircraft Wings Symbol if you're talking about the center reticle. You use it with the pitch ladder for a quick attitude reference among some other small things.

Eh, there's more than a couple of scenarios I could see where it would be a decent shot to take. Bombers are more likely to be on long-range strike duty lacking coverage by EWR. Especially, if we consider a historical scenario with weaker Soviet airborne radar assets like the TU-126, which wasn't able to detect missile sized objects, much less at decent range.

Well, now you seem to be confusing detection of radar and detection of launch signals. It's also difficult to answer some of these threads when the poster seems to be at least initially stuck on looking back at older technology and wondering why it doesn't have some of the capabilities of the newer technology. These RWRs were replaced with newer models for a reason. Technology improved and doctrine about the role of the RWR changed. To answer your question about my response. The SA-11 doesn't give a launch warning because any guidance commands are either not in a detectable frequency range or not of the style that the missile launch warning circuitry was designed for. Some of the active homing signals and the SA-15 are happy accidents as far as I am aware. They fall into detectable parameters and could be included later, along with updated threat libraries.

I don't believe that's Jester doing that. There are switches in the back that control when the RWR overrides the display. It's default setting is for the RWR screen to come up when a radar is detected, it simulates the non-continious painting of an enemy radar as it scans you and around you, so it pulses the screen on and off.

Not at the moment, it was a while ago. Try using the Mk.47 motor. It's more efficient at high altitudes than the Mk.60. An F-14A can also achieve Mach 2.0+ with a single missile for extra speed.

Both are installed together yeah. The ALR-50 is a missile warning system for the SA-2, SA-3, SA-4, and SA-6.

Not really, you are hitting the max range of acquisition at this point for the Blackjack. You may be able to see them in PD search but they drop off in the acquisition mode, until about this range. At this point, the only difference you can make is to go through the controls faster. The TU-95 or the A-50 can be acquired out from farther but they don't move fast enough to permit that high range of a shot. The Tu-22m3 will be the one that you can actually acquire at a range that stretches the Phoenix to it's absolute limit. Just under 150nm I've done, but closure needs to be 2100+ knots . Further ranges are impossible as the battery doesn't last long enough to go out farther.

It's been a little bit, but estimating the angles here based on your videos, Your antenna should be pointing about 2.2 degrees up. The coverage of the beam with Jester's usual settings is 3.7. So part of your radar beam is still going below horizon. That's just the mainlobe we care about of course, sidelobes are probably responsible for all the clutter near the target. Combined with Jester having to turn up the Gain a lot because of the intercept geometry against a tiny Mig-21. False locks happen all the time in the Phantom, doesn't matter that STT is a "narrow beam." (It actually isn't, it's subject to sidelobes just like it is in search.) The radar still needs to figure out which radar echo you are trying to go for and fails frequently in cluttered conditions with such a weak return. (I can't even really see it myself in the video.) Worth noting in the Tomcat, the Main Lobe Clutter Filter doesn't shut off on it's own until the antenna angle is above 3 degrees. That's what I generally consider a look-up situation.

Hard to tell just based on the screenshots and the description given is a bit confusing due to ambiguity. Saying that 1-2 was self lasing on 1711 when his code is 1712?

It isn't a false warning. It completely prevents me from opening the track regardless of whether items from the pack are being used. You have to disable the assets pack in the module list and create another track if you want people who don't have the assets pack to view it.