fixed internally SAM still do not loft 7/23/21 Update

[AlexCaboose]

Missiles launched in SAM still do not loft as they should after today's hotfix.

F-16 SAM bug 2.trk

[FullMetal_cooKie]

Yep same problem

[Rhayvn]

A few issues:

1. There is incorrect symbology on the FCR now.  A non datalink symbol is overlayed on top of the datalink symbol.  This only happens in RWS SAM mode.  Not in the others.
2. Antenna elevation is not adjusted automatically.  If the track goes outside of your scan zone, it will drop soft lock.  This may be intentional, but it was not like that previously and is not like that for TWS or STT.
3. 120s fired at a SAM target do not loft.  The otherwise perform normally, but definitely do not loft.  The same target in the exact same parameters will have the 120 loft if fired in STT or TWS.

Bottom line, only partially fixed.

[AlexCaboose]

1 hour ago, Rhayvn said:

A few issues:

1. There is incorrect symbology on the FCR now.  A non datalink symbol is overlayed on top of the datalink symbol.  This only happens in RWS SAM mode.  Not in the others.
2. Antenna elevation is not adjusted automatically.  If the track goes outside of your scan zone, it will drop soft lock.  This may be intentional, but it was not like that previously and is not like that for TWS or STT.
3. 120s fired at a SAM target do not loft.  The otherwise perform normally, but definitely do not loft.  The same target in the exact same parameters will have the 120 loft if fired in STT or TWS.

Bottom line, only partially fixed.

@BIGNEWY these are all issues with SAM, not just those mentioned in the patch notes.

[esequiel]

In SAM mode you can still move a bit the antenna

Track Test.miz

[SCPanda]

TWS is a good workaround. It also automatically change radar elevation and radar scale on MFD for you. Just use RWS to lock and target and then TMS right long to switch to TWS, since TWS search time is tooooo long. 

[BIGNEWY]

We are looking into it, we have work in progress or being merged currently and I will be testing this once the current fixes are ready to make sure it is not a side affect of a current open issue.

 

thanks

[BIGNEWY]

And confirmed, this is fixed internally and are lofting, hopeful for the next patch.

 

thanks