Ivandrov

Would probably be better if you showed us an example of what you are talking about. Track or video.

That's the only bug that I see so far is that STC doesn't seem to be functioning in PPI. You say "focusing radar energy" but this is just an issue of the reflected radar energy weakening with distance. The manual gives the formula as 1/r^4. The brightness of radar returns is expected to diminish as the distance to them increases. As you turn the gain up, radar reflections from further distances start showing up. Gain is not a function that physically adjusted the antenna itself or how much power it is outputting, it is a modification to the returned signals that are received through one of the amplifiers so that you can have a useable picture to look at, because if you just turn the gain all the way up, the entire radar screen completely whites out and is unusable. So, if you gradually swipe through the gain control and look at what happens to the radar picture, the returns should bias towards the closer distances of the aircraft as you turn it down, and as you increase it, the closer distances white out and the longer distance returns begin to show up and intensify. You should be able to see that here. The only that has changed is that the receiver gain was turned up in the 2nd picture.

Bring up the gain and switch to a circular polarization to find the full coverage of the beam on the ground. The LIN polarization makes many potential ground clutter returns less reflective and this dynamically changes as you roll the aircraft for instance. It's also a case where the relative angle of the surface being painted by radar will increase as you try to look at the longer range ground returns and so less radar energy makes it back to the aircraft, either because it is attenuated by distance or diffuses/reflects in another direction. That's what I can think of off the top of my head. MAP-PPI directly counters this by dynamically increasing the gain as the range of returns increases.

My understanding is that the circuitry responsible for sounding off launch warnings is specifically reserved for the guidance commands of certain C/D band SAM systems. These have very distinct signals. The RWR will however sound off anytime it detects a PRF change from a present emitter. So, you'll be able to hear a MIG-23 change from search to track for instance by listening to the new guy audio tones. It's an entirely different beast of RWR from anything else we've had before especially simulation wise. At the time these were installed, the MIG-23 really wasn't the primary air threat, they were only in service a few years at that point, and it is unlikely that the US intelligence community at that point had the proper ELINT data to be able to feed to RWRs in the first place. Also keep in mind that we're still really less than a decade (like 6 or 7 years) from when these types of RWR systems were geting fitted in these aircraft in the first place, and their primary focus in these first iterations were for SAM threats. Which is why air threats in the threat library get the short end of the stick as far as identification. I guess as a TL:DR, the primary radar threat that these first RWR's were looking for was the SA-2 and the other systems employed by Vietnam. Everything else is extra.

The reference point that the AWACS uses is the same one as the one on the F10 and the briefing. The other parameters are up to you. Set threat axis to where you would expect bandits to be based on the briefing. Sectors and angle coverage are preference. I like to use pairs of settings that make the sectors 10's of degrees wide with an even number of sectors so that the border of the two middle sector goes right through the threat axis. (120/4, 120/6, 90/6, 80/4 ) You need less angle coverage the farther away bullseye is from the expected engagement area. That just makes it faster and easier to process bandit positioning on the NAVGRID. Say we have a threat axis of 300, with 6 sectors that are 20 degrees wide. If AWACS calls a bullseye 270, you can immediately deduce that he is in the middle of the 2nd sector to the left. Even if he's not showing up on datalink for whatever reason. I cannot overstate how useful NAVGRID is, especially when datalink drops the ball. You can very quickly plot an entire picture call on it like a spider card with self updating own position and indicators for your radar coverage.

AWACS picture call outs. Use the NAVGRID all the time for that because Bogey Dope simply gives you the closest Bandit. Which might not be the one you are going for.

Your boresight is limited to 5 nm. His is not.

That's at 30 nm. It's not at all sufficient for closer distances. Even at 30 nm I find he doesn't scan fast enough through elevation for the default behavior to be useful for anything but co-altitude, much better success telling him to scan an altitude.

Use his Boresight mode for that. You can point at the visual contact with your pipper and he'll come straight up on radar most of the time.

Yes. He will scan mostly co-altitude and may steer the antenna up and down a little bit. If there's a significant altitude difference you'll have to tell him the expected altitude. So he can actually point the antenna that far up or down.

There was a significant amount of noise about it, and it was a significant change. Iron bombing feels quite good now. Very enjoyable. LGB's can be placed amongst a group of vehicles like a SAM site. Possible to destroy an entire SAM site with one or two well placed bombs.

Never launch beyond 20 miles? Regularly launch at 35 miles with success against fighters. You might as well be using Sparrows if you only want to launch within 20. Key with long-range Phoenix use against fighters besides understanding it is a big fat missile and it wants high altitude launch and high altitude targets is understanding how the flight profile works and how much it is affected by bandit aspect. If you are chasing a bandit your range massively decreases, side on shots also have quite a reduced range. Hot high closure bandits are where you can comfortably stretch the range of the Phoenix. Even 50 mile shots are possible against high speed Foxhounds for instance. Keep in mind with Jester in PD TWS, he will have several blind spots when it comes to a target's closure. You have a Notch and a Hardware filter. So, Jester won't be able to see targets that are in drag aspect moving left or right of you (Closure equals your aircraft speed +-133 knots) or if they're matching your speed in a chase (Closure equals 0 +-100 knots)

Yeah, It's just a commercial product taken off the shelf and added into the cockpit. There's likely not a universal military standard as to what specific model of GPS system you will find. Maybe at the most they've narrowed down a family or brand of systems to install or general recommendations based on what mounting brackets have been made for them, (Sometimes custom jobs within squadrons)

Computer IP is useful for some more advanced lofting where you need to designate and release before you gain sight of the target. Like from behind a mountain. Effective with both LGB's and CBU's against SAM sites for instance.

The stick on the ground at zero airspeed will move very fast and hit stick traverse limits while adjusting the trim. But, that's not an indication of the actual trim adjustment limit. Don't look at the stick, just look at the gauge and continue holding the trim until you get to the desired setting.