Jump to content

Recommended Posts

Posted
On 7/28/2025 at 8:48 AM, Muchocracker said:

HARM only produces AOT's, so you can't. FLIR is also in a similar boat, but it does hve its own separate FLIR trackfiles that it can produce (up to 8). They don't contribute to MSI so you can't L&S those either but they can be correlated to MSI trackfiles. 

What makes you think we can't L+S trackfiles just because they're angle only? If an MSI trackfile is created by FLIR or even HARM, sure it may end up being angle only for one reason or another, but there is no reason why you shouldn't be able to L+S it.

Even in current DCS, an angle-only trackfile from the radar can be L+S'd. You are L+Sing an MSI trackfile that is angle only, in this case one which happens to have radar contribution. For FLIR, it should behave be the same if modelled properly, being just as L+Sable just without a radar contribution circle and with an F instead. The ONLY kind of trackfile you should not be able to directly L+S are CIT only trackfiles, and DCS does not even model those yet (currently only tracks already built by the radar show up with IFF responses when interrogated, which is another inaccuracy compared to even the F-16 in DCS).

We need to stop this weird narrative that you can L+S some things and not some other things. Everything MSI can be designated as L+S, that is the point. The only thing you can't L+S are completely uncorrelated IFF responses (CIT-only trackfiles) which don't built a full MSI trackfile in the first place.

Posted
18 minutes ago, CaptPickguard said:

What makes you think we can't L+S trackfiles just because they're angle only? If an MSI trackfile is created by FLIR or even HARM, sure it may end up being angle only for one reason or another, but there is no reason why you shouldn't be able to L+S it.

Even in current DCS, an angle-only trackfile from the radar can be L+S'd. You are L+Sing an MSI trackfile that is angle only, in this case one which happens to have radar contribution. For FLIR, it should behave be the same if modelled properly, being just as L+Sable just without a radar contribution circle and with an F instead. The ONLY kind of trackfile you should not be able to directly L+S are CIT only trackfiles, and DCS does not even model those yet (currently only tracks already built by the radar show up with IFF responses when interrogated, which is another inaccuracy compared to even the F-16 in DCS).

We need to stop this weird narrative that you can L+S some things and not some other things. Everything MSI can be designated as L+S, that is the point. The only thing you can't L+S are completely uncorrelated IFF responses (CIT-only trackfiles) which don't built a full MSI trackfile in the first place.

FLIR trackfiles are pretty explicity not MSI trackfiles if you read the sources. You can desigate them to slave other sources to them to create MSI trackfiles. They are not MSI trackfiles onto themselves. It applies just the same to AOT's. 

Posted
9 minutes ago, Muchocracker said:

FLIR trackfiles are pretty explicity not MSI trackfiles if you read the sources. You can desigate them to slave other sources to them to create MSI trackfiles. They are not MSI trackfiles onto themselves. It applies just the same to AOT's. 

Just as radar trackfiles are not MSI trackfiles. I believe you are thinking about this wrong.

MSI trackfiles can be built by both radar trackfiles AND FLIR trackfiles. While FLIR trackfiles aren't MSI trackfiles, neither are radar trackfiles. They BOTH build MSI trackfiles and MSI trackfiles can always be interacted with.

  • Like 1
Posted
FLIR trackfiles are pretty explicity not MSI trackfiles if you read the sources. You can desigate them to slave other sources to them to create MSI trackfiles. They are not MSI trackfiles onto themselves. It applies just the same to AOT's. 
They are not, but will automatically become MSI track files if one of the eight slots are open.

Sent from my moto g stylus 5G (2022) using Tapatalk

  • Thanks 1
  • Recently Browsing   0 members

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