OUO

If the target is not found on the radar page, the height and speed information of the data link target cannot be seen through TDC selection.New BUG in this version

Yes, firing the AIM120 after burn-through does not use high-projectile ballistics TRK has been uploaded. You can check it out or do the test yourself. There is distance information after burn-through. Why does AIM120 not use high-projectile ballistics?

In the case of burn-through interference, the AIM120 does not follow a high-throw ballistic trajectory. Referring to the TRK document, the ECM burned through and fired the AIM120, barely making the jump to 40,000 feet despite the given ejection angle,but if the target does not turn on the ECM, the AIM120 can easily jump to more than 50,000 feet. ECM OFF.trk ECM ON.trk To put it simply, as long as the target turns on ECM, the AIM120 can only take a horizontal trajectory, even though the fighter has burned through the interference.

Triggering conditions：Within 6NM of the target, the airborne radar is turned on and the radar does not create a tracking file. F18 AIM7.trk This problem only occurs when F18 uses FLOOD mode, so do not submit the weapon vulnerability section.

It is unreasonable to rely too much on TDC in air-to-air radar operations and to move too slowly.Refer to F/A-18C, TDC cursor movement is quite flexible There is a video of the TDC movement speed of the F/A18 and F15 in the link

But these operations themselves do not affect the work of the radar, the radar will still scan the area again according to your adjustment after completing a scan

Through special options, customize the setting of TDC movement speed and radar pitch adjustment speed. It feels that the TDC cursor moves very slowly

In fact, I am more curious whether the AIM120 in reality can also do this

F18 can be used in this way, and it has a 32-second radar memory, which will be more convenient

AIM120 omnidirectional attack on any target until the radar track file is deleted. i'm not sure if this matches reality? AIM120.trk

In the second video, try pressing the nose of the aircraft under the target?This is not ATFLIR's problem.

well, forgot that the AZ/EL pages change based on the radar page distance, not the radar's cursor

This yellow box is the radar scanning field of view.

the target displayed on the AZ/EL page is already within the FOV, but the scanning range of the radar page cannot cover the height of the target

The AZ/EL page shows that the radar FOV range does not match the actual. Or is it that the upper and lower limits of radar scanning have become smaller? AZ.trk