Jump to content

Recommended Posts

Posted

With the IAT, when a target is selected, the target box is first created behind the target and then "jumps" to the target shortly after.

With the IAT there is also a problem when the LST is set to manual. As soon as LST-manual is activated, an immediate desync is noticeable for the pilot, in which then the TADS either stops, looks around wildly and partially shakes around.

If a target was selected with the IAT during the LST-manual, the IAT can no longer turn cleanly to the target after switching the LST to off.

 

LST_IAT-bug_cpg_seat.zip LST_IAT-bug_pilot_seat.zip

Main machine: Ryzen 7 5800X3D, 64Gb 3600Mhz, Gainward RTX 5080 Phoenix V1

Second machine: Ryzen 7 5700X3D, 64Gb 3600Mhz, Gainward RTX 5070 Python III

Equipment: DIY FFB-Pedals, Virpil AH-64 Collective, DIY FFB-Rhino, TrackIR 5

  • 1 year later...
Posted

this sounds similar, but our experience tonight (and this is on DCS 2.9.18.12899) is that in multiplayer, IAT actually causes LST to lose lock. 

Specifically, Apache 1 is lasing on laser code Romeo, and Apache 2 and 3 are LST on Romeo, they set LST to auto and their TADS immediately snaps to the laser spot. As soon as Apache 1 turns on his IAT, the LST of both Apache 2 and 3 immediately goes into scan mode, essentially they lost the laser. As soon as Apache 1 IAT is deleted, the LST of both Apache 2 and 3 snaps back on the laser spot again.

  • Recently Browsing   0 members

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