correct as is Vertical resolution of Attack format tactical region incorrect

Jak525 · January 28, 2021

The Attack format is currently referencing the bottom of the tactical region to the top of the dugout (angle only trackfile zone) as its range reference. For example, if the maximum range displayed is 80, then the 0nm point is at the bottom of the tactical region and the 80nm point is at the top of the dugout. This is incorrect.

The dugout is its own thing, above the range-resolved tactical region. The maximum range scale point should be the BOTTOM of the dugout, and the 0nm point should be the bottom of the tactical region, as it is now. Note also that beyond the correct 80nm point, it shouldn't go to 81, 82, etc. It just ends there. The dugout inherently has no defined range. Vertically, it's completely ambiguous.

I attached some pictures to demonstrate.

IMPORTANT NOTE: The tick marks on the left and right side of the tactical region need to be re-done as well. They currently represent the incorrect scale. They need to be slightly closer together and adjusted down so as to indicate the correct fractions of the maximum range scale.

Also note that the cursor and BRA indication serve as proof that the 80 mile point is indeed being considered as the top of the dugout. In the .trk, the bottom of the dugout indicates about 76 miles.