fixed internally TWS: Cancelling a Cursor/Bugged Target doesn't return Azimuth Scan Limits to a normal TWS scan

[Delta134]

While in TWS mode and hovering the radar cursor over a System Target, it is correctly made a Cursor Target and the scan limits are correctly set to a 3-bar ±25° pattern centered on the target. However, when slewing away from the Cursor Target, scan limits are not restored. The same is true for a Bugged Target.

This issue complicated workflow and pilot load in addition to being in conflict with the functionality described on page 243 of the DCS F-16C Early Access Guide by Eagle Dynamics.

See the attached track file.

tws_scan_limits_bug.trk

[Lord Vader]

Hello @_Delta13_

As we've mentioned here before, the DCS: F-16C Viper manual is undergoing an extensive review to produce a new and more accurate document, based on the various updates and improvements we've done to this module over time. Therefore, that particular section and phraseology may require some polishing. Thanks for understanding.

In the current version, the TWS hands-on azimuth selection (60º) is entered by moving the cursor to the left or right edge of the MFD (or using the OSB 17 and 18 as you did), and it is also exited with the same procedure. But this is only if there are no TOI selected via TMS up. If there is, the scan volume will "stick" to the TOI and will remain available.

[Delta134]

I think I may not have stated the issue clearly enough.

In order to upgrade a System Target to a Cursor Target, one does not need to press TMS up. One simply hovers the cursor over the System Target. This correctly sets the scan limits to a 3-bar ±25° pattern. However, once moving the cursor away from the Cursor Target (again, no TMS down required) the target should be returned to a System Target and the scan limits should return to the original scan limits. In the track file I demonstrated this is not the case.

I agree that in case of a Bugged Target (TMS up on a System Target) the scan volume should stick to the target and the scan limits are reduced.

So to clarify: the issue is not the location of the scan volume (this should be centered on the Cursor or Bugged target) but rather the azimuth limits of the scan volume not being returned to the original as soon as the Cursor or Bugged target is returned to a System Target (i.e. the ±25° is not returned to the original)

The issue particularly pertains to the following sentence on page 243 in the manual:

Quote

The Cursor Target can be changed by slewing the cursor to another system target. Slewing away from all system targets returns the radar to a normal TWS scan.

Disregarding the issue due to the manual being work in progress is too easy. Please seriously look into the issue I am describing.

Edited October 2, 2024 by _Delta13_

[Lord Vader]

Hello again @_Delta13_

4 hours ago, _Delta13_ said:

Disregarding the issue due to the manual being work in progress is too easy. Please seriously look into the issue I am describing.

There was no disregarding of an issue, I simply read your post and the description lead me to a possible misinterpretation of the procedure vs the fact our EA manual is being reviewed. It's not a matter or being "easier" and we take all reports seriously. 

Now that you clarify your point, I will take this internally for analysis.

Thank you for your time.