reported F18 Showing Ground distance instead of slant range

[nighteyes2017]

Was practicing 30 and 45 degree dives today, using my F16. I decided to try the same in the F18, and it didnt work. The numbers weren't adding up.

After some searching, it turns out the ranges in TGP and the HUD are Ground distances instead of slant ranges. So i made a mission to compare the F16 and the F18 together to be certain.

Using the F16 to overfly a steerpoint at 18000ft, the slant range should not be able to reach 0, because directly over the steerpoint, you are still 18000ft away from the waypoint (slant range). This works as expected in the F16. In the F18 however, this is not the case. The distance reaches 0 when directly overflying the steerpoint. 

You can see it in the trackfile, or use the mission file to test and compare.

 

 

F18 F16 Slant range.trk F18 F16 Slant Range.miz

[maxTRX]

The way it works currently:  Within 10 nm, your target designated, Your FLIR in INR mode - bump your SCS switch up toward HUD to use AGR ranging.  If your FLIR is in SCENE or AUTO modes (using ATFLIR in this example) - bump the SCS switch up toward HUD. 'FLIR' will show up on HUD as the ranging sensor (I'm not sure if AGR is also working to 'help' in this case)

So, it does work within roughly 10, 9.xx nm slant range.

[nighteyes2017]

that sounds more like a workaround, than a feature.

Also, the manual also shows multiple pictures of it being (should) slant range, with the pod as sensor of interrest, and not the HUD. So maybe AGR ranging mode does show slant range, while the others dont. (they should)

 

[Jak525]

The range to the designation is not supposed to be slant range. Only TACAN is slant range.

[BIGNEWY]

reported

this is working correctly in our dev build, not sure what has happened here we will check

thanks