OUO

R Ctrl + R Shift + K,alternatively you can call ground staff to open DTC

The guidance head field of view can be fixed at any position on the HUD,will not return to the nose pointing direction FA18 AIM9.trk

It's already past two in the morning here. I'd better go to sleep first

The AIM120 cannot successfully hit me when I turn on the ECM and continue to maneuver.（Premise: The plane that launches the missile cannot keep locking onto me, otherwise the missile will still hit me, so I will also launch a missile to drive the enemy plane away） apparently, we have a minor problem with our missiles again. The above applies to both AIM120 and PL12. ECM ON.trkECM OFF.trk

LINK16 and ECM.trk i suggest watching TRK first. when I detect an aircraft with electronic jamming turned on through the airborne radar at a non-burn-through distance, the direction of the jammer should be displayed at the top of the radar screen however, the interference source target will be overlaid on the target displayed by LINK 16. When using radar lock, the current distance will be displayed on the HUD also, when my radar is no longer illuminating an enemy aircraft, its track file will take a long time to be deleted. (More than 8 seconds) the TRK playback shows that when I manipulated the radar to prevent it from finding the target, the tracking file of the enemy aircraft without electronic jamming was deleted first, followed by the enemy aircraft with electronic jamming turned on. this problem has persisted for several versions and has not been improved

CAGE/UNCAGE button This button switches the AIM 120 to VIS mode, even if your radar is locked on a target. You will use this button to calibrate the HMD. Solution: Press the CAGE/UNCAGE button again.

When the MED altitude is selected, the missile seeker is turned on, and the target is locked, the missile may fail to hit the target. If you use LOW height, you can hit the target. If you choose HIGH, you can't hit the target. Moreover, at the cruising altitudes of MED and HIGH, the AGM84E did not dive in time when approaching the target. Instead, it did not start to descend vertically until it was close to the target. 84E MED 01.trk84E MED 02.trk

OK

within 30nm：terrain loads normally. 35nm-45nm：a wide FOV does not load terrain, a narrow FOV loads terrain. 50nm away：unable to load terrain properly. the trk file only uses AGM84H for demonstration,AGM84E also has the same problem. 45nm.trk50nm.trk

the current CM802 AKG and AGM84E/H both have this problem. as long as the aircraft is far away from the attack point, the terrain will not be loaded.

Hahaha, my English is not very good, let me explain with pictures. For example, if I click SAVE, this box should appear, indicating that I have clicked SAVE.Just like when I click REST and SET on the attack radar page, there will be this box. This is part of human-computer interaction, but when you click SAVE on the EW page, this box does not appear. I just feel there is something wrong with this logic based on other pages.

However, on the attack radar page, clicking RSET will be box-selected, and clicking SET will also be box-selected.

AIM120C,hit from behind

In the current version, I feel that the pilot’s survival rate is higher. I have ejected many times after being hit.

The SU27 and J11A only have a total of 96 positions for loading chaff and flare, so the numbers should be 48C and 48F, not 96C and 96F. The SU33 also has only 48 positions for loading chaff and flare.