Jump to content

Recommended Posts

Posted

From technical documentation it is known that brief interruptions in target signal are handled by extrapolation of the memorized target movement.

This works more or less in BVR mode the FC3 aircraft.

 

But this mode is entirely absent in any of the close combat modes. Brief interruptions in target tracking will instantly destroy the lock. This is incorrect behaviour, as we can see from this real world MiG-29 HUD footage. Note how it remains in target tracking mode for 2 seconds after the target left the gimbal limit of the IRST:

R-73K_shot - YouTube

 

So to make things more correct, the extrapolation ("memory mode") that already works in BVR mode needs to also be added to the close combat modes.

  • Like 2
Posted

It's not clear from this video how far off the angle the aircraft was, so the time off the gimbal is not known.

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
18 minutes ago, draconus said:

It's not clear from this video how far off the angle the aircraft was, so the time off the gimbal is not known.

You don't need to know how off the angle was. You can see at 00:18 how the antenna position indicator starts wiggling because it is trying to regain lock, and it does that for about 2 seconds before going back to vertical mode. And it does that as soon as the target goes below the nose as the pilot has only IRST active.

  • Like 4
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...