[2.9.15.9599] DT does not (always) use the range bar as a range reference

[Stickler]

Observe the attached tracks and .acmis starting from the same position and parameters.

Track "DT" (Dive Toss):

• As per the bombing calculator, I enter 1.04 as the CB, subsequently lock a harbour tug in AIR-GND mode, and pickle at the same location while still in active pause.
• Approaching the target as precisely as possible at the planned parameters, the bomb releases at at plan range of 5117 ft from the target, resulting in a 3783 ft long bomb.

Track "DL" (Dive Laydown):

• As per the bombing calculator, I enter 9216 ft as the release range, subsequently lock a harbour tug in AIR-GND mode and pickle at the same location while still in active pause.
• Approaching the target as precisely as possible at the planned parameters, the bomb releases at at plan range of 8980 ft from the target (thus 236 ft closer than set).

Evaluation:

• I was able to trace back the "closer than planned" release in DL mode to the range bar not tracking the leading edge of the target return (which is where the actual target is located), but the trailing edge, in this post. This error can be easily overcome by adjusting the release range or setting a release advance.
• Generally, for DL, the range bar's position seems to be the only relevant factor in determining the range to target entered into the WRCS.
• As can be seen from the "DT" track, in DT, the range bar's position does not seem to determine, or at least is not the only factor determining, the target entered into the WRCS.
• I was able to exclude a faulty CB as the reason for the DT miss: When locking the tug from a dive, pickling with the tug underneath the pipper and subsequently levelling off to release at 500 KTAS and 2000 ft, the bombs hit (no track uploaded since this behaviour is as expected).
• Thus, in DT, having the target under the pipper at pickle and the range bar at the corresponding location ensures a hit even for the Dive Level variant. However, moving the range bar a significant distance away from the main beam clutter, even if the target was under the pipper at pickle (and thus utilizing a grazing angle within the 10° DT limit), will cause the target to be missed. What this "significant range" is, and by how much the target is missed, is unpredictable (at least I could not identify a clear logic); the actual target hit will neither be the center of the pipper not the place marked by the range bars if the threshold of significance it exceeded. Please reference this post for additional information.
• Based on even further testing, everything described above is valid for releases from single-stage trigger or from lock-on.

Bombing table:

dtdl-dl.trk dtdl-dt.trk dl.acmi dt.acmi

Edited Saturday at 08:45 PM by Stickler