[HF2] FMS Text distance/time numbers broken?
-
- Posts: 75
- Joined: Sun Sep 16, 2018 12:35 am
[HF2] FMS Text distance/time numbers broken?
This is either bugged or I don't understand how to read it. I was at least 250+ NM from YUL but it's showing the final destination to be much closer:

Then, after passing a waypoint, it looks more normal?


Then, after passing a waypoint, it looks more normal?

-
- Posts: 5
- Joined: Mon Dec 15, 2014 9:29 pm
Re: [HF2] FMS Text distance/time numbers broken?
I was seeing the same last night.
Dest was approx 250NM away and the value was showing a number in the vicinity of 30NM, but the value was reducing. Almost seemed like it was showing the distance to the waypoint after the next one or something like that. Hope to get a flight in tonight and will see if I can work out what the value is actually based on.
Dest was approx 250NM away and the value was showing a number in the vicinity of 30NM, but the value was reducing. Almost seemed like it was showing the distance to the waypoint after the next one or something like that. Hope to get a flight in tonight and will see if I can work out what the value is actually based on.
-
- Posts: 268
- Joined: Sat Dec 21, 2019 10:02 pm
Re: [HF2] FMS Text distance/time numbers broken?
1.) I have run into the same issue:
CEN4 DCT TULOB DCT LYTON DCT CYPS (first screenshot) EDIT: After further investigation: Once I threw in a RWY at the destination with a 25nm extension it worked fine. EDIT2: A little bit later in the flight it is acting up again. Additonally:
2.) And I would like to add: Once the ETA goes below 1hr, so lets say 0h 59min 59sec it seems that the aicraft does display 60 minutes. Shouldn't that be still 1:00? (second screenshot).
3.) Also the range does not add up. Lyton is about 60NM from CYPS. On the FMS it is correct.(third screenshot)
I would like to add that on the first screenshot was correct for some reason. The shots were taken within the length of writing this post.
CEN4 DCT TULOB DCT LYTON DCT CYPS (first screenshot) EDIT: After further investigation: Once I threw in a RWY at the destination with a 25nm extension it worked fine. EDIT2: A little bit later in the flight it is acting up again. Additonally:
2.) And I would like to add: Once the ETA goes below 1hr, so lets say 0h 59min 59sec it seems that the aicraft does display 60 minutes. Shouldn't that be still 1:00? (second screenshot).
3.) Also the range does not add up. Lyton is about 60NM from CYPS. On the FMS it is correct.(third screenshot)
I would like to add that on the first screenshot was correct for some reason. The shots were taken within the length of writing this post.