fixed Undesignate button magically lock the own missiles when multiple missiles launch

Max Mak · July 28, 2022

Undesignate button magically lock the own missiles when multiple missiles launch

Bug report for the recent patch DCS 2.7.16.28111 Open Beta.

After the in depth testing of how the own missiles being mistakenly designated when multiple missiles launch in the current F/A-18C module, I got some new findings for the bug.

In order to keep the consistency of every replicated tests. I standardised the procedures for every replicate tests:
1. Hold attitude and auto throttle just at mission start
2. Select AIM120C, then TWS mode (variable parameters in each replicate) or RWS mode
3. Shoot first missile at time 04:01:00, and complete final shot at 04:01:12
4. Press undesignate button at 04:01:13
5. Screen capture at 04:01:15

All the following tracks I shows are using 20 degree 2 bar scan for TWS mode; 140 degree 2 bar scan for RWS mode, 4 seconds AIM120 radar profile age out time. I actually tested all the combinations with these settings, also in RAID mode, or even not in EXP option, but the final outcomes are all the same so I only provide the 4 most representative tracks here.

Test 1
In the first test I use TWS auto and press the undesignate button to cycle the contact between AIM120 launch. The final press of undesignate button at 04:01:13 (step 4) resulted in own missile lock. Noted that the radar elevation is going up, should be weird because all my contacts (IL-76MD) are co-attitude with me, the missile I locked is already going up, I shouldn’t have chance to even tracking it.

Test 2
After Test 1 I think the problem should solved if I use TWS MAN, as the TWS will not change the antenna elevation settings with contact position, and thus I should have no chance for looking up like Test 1.
Like Test 1 I also use the undesignate button to cycle the contacts between launches. Interestingly, I also lock the same missile as in Test 1 after the final press of undesignate button at 04:01:13. Noted that the lock is clearly outside my radar elevation scan zone if you compare the radar elevation setting that the TWS auto bring me in Test 1.

Test 3
Then, I do think that the problem should be the undesignate button. Therefore I do the same test again, and this time I use TDC depress button to cycle the contacts instead of using the undesignate button, but I also press the undesignate button once at 04:01:13 as I did in Test 1 and 2. This time I don’t lock my own missile anymore even I’m in TWS auto. Own missiles still clearly defined by MCs as a triangle symbol.

Test 4
Finally, I also try these AIM120 launch procedures once not in TWS mode but in RWS mode, using the undesignate button to cycle the contacts, and again the finale press of undesignate button at 04:01:13 still locking up the same own missile. Thus, it clearly shows that the problem is on the undesignate button itself and not related to the scan radar.

Conclusion
1. Own missiles lock problem is not radar related (TWS rankings, gating etc.)
2. Undesignated button can do a magical lock on own missiles even without a contact track from own radar.
3. Once the own missiles being locked, all the track files on the tracking radar will be lost. This will screw up your multiple missiles launch on multiple targets.

I know that the issue can be solved by the user end that not to frequently press the undesignate button to cycle the contacts. However, it is clearly a bug and need to be fixed, you won't see the TMS right will do this weird behaviour when cycling the contacts during mulriple missiles launch in F-16 module.

I think the problem should be related to the MCs memory being erased by undesignate button. I don’t know, but I hope that the tests I did can provide a direction for you the ED team to fix the problem.

Thanks for reading this long paragraph.

Best wish,
Max Mak

Test 1 TWS Auto undesignate 20220729.trk Test 2 TWS MAN undesignate 20220729.trk Test 3 TWS TDC depress 20220729.trk Test 4 RWS undesignate 20220729.trk

Edited July 28, 2022 by Max Mak