fixed ACM modes stuck at 5 miles

[Comrade Doge]

Hello everyone, found an interesting behaviour in the F-16, namely when using the ACM RADAR modes, in that they become stuck at a 5 mile range, from the usual 10 mile range they should scan and lock targets at.

Since this is a relatively small bug, I will not go into many details apart from offering the procedure to replicate the bug:

1. Acquire an ACM lock in DGFT submode, with the scan mode of your choice (BORE, 20, 60, SLEW)
2. Wait for the target to close and the FCR screen to autoscale to a 5 mile range (shown on the MFD)
3. Drop the lock by TMS Down
4. Enter the same ACM mode you previously used to lock, and you would notice it's scan range is now 5 miles instead of 10.

Note: The 5 mile range bug, when triggered, persists only in the ACM submode that it was triggered in initially (BORE, 20, 60, SLEW). For example, if you trigger the bug in BORE acquisition mode, and the range becomes stuck at 5 miles, the rest of the modes still scan at the regular 10 miles, until the bug is triggered using each one of them as well.

Below I attach the trackfile where you can see me triggering the bug in the BORE, 20 and 60 submodes, one by one.

Have a great week everyone!

F16ACMbug.trk

[BIGNEWY]

Reported

thanks Comrade Doge