Krag6 Posted June 3, 2018 Posted June 3, 2018 (edited) As we know we can change the way coordinates are displayed between Standard and Decimal. Hornet automatically switches the input method based on your choice in the options. Except the input as it flipped. If F10 screen displays standard, input needs to be in decimal. If F10 is in decimal, hornet needs standard. For Example N 40 07 75 (decimal) ufc input, will result in N 40 07 45 (standard) waypoint. Making the waypoint placement inaccurate. To clarify, waypoints are displayed correctly. The input method is switched. Edited June 3, 2018 by Krag6
Krag6 Posted June 3, 2018 Author Posted June 3, 2018 I Switched the Standard and Decimal in options. And it switched it in the aircraft. It was never correct. It was always flipped. This is multiple tests.
Krag6 Posted June 3, 2018 Author Posted June 3, 2018 (edited) Upon further inspection it seems that. Whatever you use it seems that you need to input your LAT and LONG in Minutes, and Waypoint page switches it to Decimal. Edited: You are right I'm wrong thank you. Edited June 3, 2018 by Krag6
Krag6 Posted June 3, 2018 Author Posted June 3, 2018 (edited) It is weird. I entered a Minute based location, and it was shown of HSI inaccurately. I even switched to decimal mode to check that precise location. It seems it gave me accurate translation on WPT page.(hornet computed it correctly, but displayed it wrong on HSI). Have you experienced the same? HSI computed course is 12.9 at 321, when the point is 12.9 at 326. EDIT2: Flied to the point. It seemed fine. I guess its inaccurate only right after putting it in. Weird behavior. Edited June 3, 2018 by Krag6
Recommended Posts