I have discovered three airports which, when any one of them is added to the flight plan between the departure and arrival points, will cause the following malfunctions in Glass Cockpit Instruments:
1.  Airspeed, Altitude, Heading and Bank indicators are frozen.
    (i.e they show no change of data)
2.  The map doesn't move in the "moving map" displays.
In addition, for any aircraft flying this flight plan, the "VFR MAP" invoked via the "Tools" menu will have no moving map and no zoom capability.

The offending airports I've found (there are probably others) are:
KPMD (Palmdale California)
KRMG (Rome Georgia)
KBOI (Boise Idaho)

I am running MSFS Ver 1.26.5.0 (SU9 & WU10) on a Windows 10 machine.  I have nothing in my Community folder. All my flights use default planes and MSFS created flight plans.
A simple test can be run as follows:
Plane:            Cessna Grand Caravan
Flight plan:    Departure - KSLC (Salt LakeCity, Utah)
                      Arrival - KSEA (Seattle - Tacoma, Washington)
                      Add in between - KBOI (Boise, Idaho)
                      Type - VFR or IFR (Either type will exhibit the odd behavior)
Fly the route and notice the non functional glass instruments and VFR MAP.

I was wondering if anyone else has experienced the same oddity?

Bug report it over on the main forums.

6 hours ago, spc4529 said:

I have discovered three airports which, when any one of them is added to the flight plan between the departure and arrival points, will cause the following malfunctions in Glass Cockpit Instruments:
1.  Airspeed, Altitude, Heading and Bank indicators are frozen.
    (i.e they show no change of data)
2.  The map doesn't move in the "moving map" displays.
In addition, for any aircraft flying this flight plan, the "VFR MAP" invoked via the "Tools" menu will have no moving map and no zoom capability.

The offending airports I've found (there are probably others) are:
KPMD (Palmdale California)
KRMG (Rome Georgia)
KBOI (Boise Idaho)

I am running MSFS Ver 1.26.5.0 (SU9 & WU10) on a Windows 10 machine.  I have nothing in my Community folder. All my flights use default planes and MSFS created flight plans.
A simple test can be run as follows:
Plane:            Cessna Grand Caravan
Flight plan:    Departure - KSLC (Salt LakeCity, Utah)
                      Arrival - KSEA (Seattle - Tacoma, Washington)
                      Add in between - KBOI (Boise, Idaho)
                      Type - VFR or IFR (Either type will exhibit the odd behavior)
Fly the route and notice the non functional glass instruments and VFR MAP.

I was wondering if anyone else has experienced the same oddity?

Yes, I have noticed this a few times using the glass cockpit in the Longitude. I'm fairly certain that this problem -- believe it or not -- has to do with the length and font size of the waypoint as visible on the cockpit display. Most of the waypoints are short abbreviations. When you add in a waypoint that has a long name attached to it, things can go awry. I've noticed that, whenever my instruments freeze up exactly as you've mentioned, I can get them restarted by deleting the long-winded waypoint name that's currently showing on the FMS.

23 hours ago, David Mills said:

Yes, I have noticed this a few times using the glass cockpit in the Longitude. I'm fairly certain that this problem -- believe it or not -- has to do with the length and font size of the waypoint as visible on the cockpit display. Most of the waypoints are short abbreviations. When you add in a waypoint that has a long name attached to it, things can go awry. I've noticed that, whenever my instruments freeze up exactly as you've mentioned, I can get them restarted by deleting the long-winded waypoint name that's currently showing on the FMS.

Thanks for the reply.  It's good to know that I'm not the only one who has seen this.  Your observation is very interesting.

With respect to Glenn's suggestion to "bug report" it, I'll consider it.  I'm in the process of updating my XBOX Live account(s) and will probably wait until after that completes.