We believe this is related to the jetway not being disconnected prior to pushback. We have a way of forcing the EXT AC to disconnect during pushback currently in testing, and we intend to include it in the next update. Mark - Just Flight

Charts are the primary source of the ILS course/frequency in the F70/F100. It is possible to view the ILS frequency on the FMS > REF INDEX > NAVAIDS page by entering the ILS identifier, but that requires you to know the ILS identifier, which the charts are likely needed for anyway. Mark - Just Flight

We are aware of some door interaction issues with third-party liveries that looks to stem from livery artists using a different format in the Title= entry of the aircraft.cfg compared to our own liveries. If the Title= line does not include the door variant, then the correct door logic will not load in the simulator. We're investigating this on our side to see if there's anything else we can do to detect which variant it loaded in the simulator, but for now, the quickest solution would be for livery artists to update the aircraft.cfg Title= entry so that it is in the format of: [Aircraft Type] | [Pax Door Type] | [Cargo Door Type] | [Airline] Mark - Just Flight

There is a post here on how to get the display variables with SPAD.Next - it will need a little conversion to other tools however the variables will remain the same: https://community.justflight.com/post/51540

The "NEUTRAL" option in the sensitivity menu should allow you to control where the changeover between forward and reverse thrust occurs on the throttle axis. Mark - Just Flight

Excellent find!

In Europe the F70 and 100 are RVSM certified - you can find a lot of flight plans on EDI GLA with a cruising level up to FL 350.

Further observation: it seems the aircraft is losing track seconds after you go DCT OKAKI again.. tried it a few times and can't keep track to OKAKI. Crosswind is about 100kt from the left if that's something to consider too?

Let's start a survey amongst customers to see who's interested in extended failures even as a payware option to determine if it's value to develop it or not.

Could this be added/fixed in a coming update?

Thanks a lot by attention!

I have this time to time with more planes. It's something they cannot just fix, it's a MSFS thingy. We just have to live with that.

That's for sure But it is a wonderful bird!

I'm not able to replicate this on my side. The temperature is imported directly from the METAR (16C in the example below). [image: 33b28362-13e7-4fd9-99f9-ca4fca430e75.png] If this occurs again, it would be interesting to know the METAR that is being generated/imported. Mark - Just Flight

I had a hunch that could be related. If it happens again I'll be sure to let you know with a ticket.

Thank you for reporting this. I have logged this on our internal trackers for our development team to investigate further. Mark - Just Flight

Thank you for the feedback. I have passed that on to our IT team for further evaluation. Mark - Just Flight

On the EFIS Control Panels, the APP/VOR button needs to be selected to VOR in order to allow tuning of the VOR DME radios: https://support.justflight.com/en/support/solutions/articles/17000152234-how-to-tune-vor-radios- Mark - Just Flight

I've been able to trigger this pretty consistently. During a turn around if I cycle the FD, the message will appear.