reported FCR A-A SAM steals FCR range from pilot

[Bear21]

1. The appended track shows how after entering A-A SAM the FCR steps down display range on its own both before and after AIM-120 launch (18:53:30 and fwd), and does not allow the pilot to increase display range to control second Mig29 (several attempts to increase range to control second Mig29 are not accepted).

2. The FCR does not allow DTT on said Mig29 when it's within the hijacked range, instead it continues to step down range as SAM (on Tgt 1) comes closer and is active (there is no need for the pilot to have the SAM target at an optimal range display, you only need to watch azimuth coverage for datalink updates to AIM-120). In cases where the second Mig29 is further behind you are victim to the FRC and can't follow Mig29 no 2, even though you are in SAM and not in STT or TWS.

2024.1.4 F-16 vs 2 Mig29.trk

[Bear21]

Here is the mission file for others to try. Mission: Kill off the Mig29s, then the Tu95. Observe how the FCR controls range scale from SAM (one TMS up) start.

F-16 2 Mig29 CAP R27, R73 and Tu95MS, E3 Caucasus.miz

[BIGNEWY]

Hi Bear21,

I maybe misunderstanding and will ask the team.

I am looking for evidence that SAM mode would allow for range changing and/or switching mode to DTT when tracking a target. If you do have public declassified evidence please PM me. 

thank you 

[Bear21]

The DCS F-16 Early Access User Guide page 238 "Dual Target Track (DTT). Dual Target Track is entered from SAM by bugging a second target.", which is what I did. No effect.

Regarding the range hijack, I never flew the F-16C so can't say but it seems to me the programmer took the easy way of using the STT behavior for SAM and DTT. For Single Target Track (STT) the FCR control of display range makes sense, but for SAM not, as SAM shall allow stepping up to DTT, which can be at a different range to the SAM target. The solution is to do nothing for SAM and DTT, let the pilot manipulate range.

Edited January 9, 2024 by Bear21

[BIGNEWY]

Thank you we have reported this to the team and it will be fixed.