#2474 787-8 CDU stopped working on 2020.3.4

[legoboyvdlp]

https://forum.flightgear.org/viewtopic.php?f=25&t=38443&p=378007#p378007

I recently updated from FlightGear 2018.3.5 to 2020.3.4

I exclusively use the Boeing 787-8 model. The aircraft model did not change. I only updated FlightGear.

I use Windows 10 with an integrated graphics card. A low end system. But based on my analysis this has to do with missing/bad data and not graphics or performance.

THE PROBLEM: In the GPS Settings page of the Electronic Flight Bag (EFB) MDU (to the left of the pilot in the cockpit) a map is displayed with the position of the aircraft along with the Desired Magnetic Course, Desired True Heading, and Distance to Waypoint. These latter three values are supposed to change depending on what the next waypoint in the Active Route is. They display correctly in version 2018.3.5

However, in version 2020.3.4, no matter what your next waypoint is the values are these:

Desired Magnetic Course 0
Desired True Heading is 9.37767_
Distance to Waypoint -1

Desired True Heading fluctuates wildly and in real time down near the millionths past the decimal place, but always stays approximately 9.37767_

NOTE: I am entering the route via the CDU -> INDEX -> FLIGHTPLAN -> ACTIVE RTE -> ROUTE page. If I use the GUI Drop down menu to plan a route (Route Manager), then EFB -> GPS Settings page values display correctly in both versions of FlightGear. However, I want the cockpit to be able to mimic the CDU functionality. The CDU route planning works for GPS Settings in version 2018. It stopped working in version 2020.

I downloaded the codebases of both versions, thinking that the most likely cause was a change in XML tags or levels, or possibly even Nasal code. But I couldn't find any change specific to GPS settings in the area I am looking for.

[James Turner]

Will take a quick look. Does the 787 have an active maintainer, I wonder?

[legoboyvdlp]

Doesn't appear to.

I was the last person to make any serious change, but for me, the CDU never worked properly so I just fixed a few runtime errors.

But just in case it was this one:
https://sourceforge.net/p/flightgear/fgaddon/4982/

Before that radi was the maintainer but he told me that he isn't around very much anymore when I messaged him about these changes.

[James Turner]

Just checked, those properties are still present of course, ntohgin changed. I'm guessing what is happening is that the GPS is not in LEG mode? Jonathan, can you try to build a route using the CDU of the 787 and check for any errors? My wild guess is route entry is broken somehow.

[James Turner]

Looking a bit more: might be that the 787 CDU never activates the route, so GPS leg mode doesn't do anything.