fixed HSI distance to INS destination shows slant range

[Frederf]

Demonstrated with a flight plan at 7nm altitude (42,532 feet) and spacing between consecutive waypoints of 42,532 feet it is seen that HSI distance to destination is showing slant range instead of the two-dimensional range to destination.

 

Upon passing the first waypoint the simulation is frozen and 9.9nm (about 60,000') is shown on both the HUD "B" line and the HSI range window. The slant range between the two waypoints is roughly sqrt[ (42,532^2)x2 ] or 60,149' or 9.899nm.

 

The HUD data line of "006>002" is showing 6nm to waypoint 2 which would be the case if all values 6.00000 to 6.9999999nm are displayed as "6". I think the real F-16 rounds instead of floors this value but I'm not sure. In either case of rounding technique the HUD ">" line is showing 2D distance and the HSI should show this as well for INS destination.

Viper HSI INS distance.trk

[Terzi]

I confirm this and a very similar problem. I recall once I was with mavericks in VIS mode, moving the cursor was changing the range in HSI. In other words, the HSI was showing my weapon's slant range to current maverick SPI.

 

I was too lazy to report it because it definitely needs a track file

[Frederf]

Pretty sure how DCS has it that in NAV mode HSI bearing is to destination and AG mode HSI bearing is to SPI is correct. But in both cases range is 2D.

[BIGNEWY]

this has been reported to the team

 

thank you