Bug - Flight Director, unable to change active waypoint after takeoff

[eaglerainbow]

Describe the bug At various cases, I was unable to change the active waypoint selected by the FD after take-off. It kept stay at the starting airport's runway even though I tried to give inputs to change it to a more recent waypoint.

To Reproduce Steps to reproduce the behaviour (these are steps were it worked best for me):

1. Take LPPT as starting airport, RWY 03.
2. Program FPLN via MCDU with SID GANSU*
3. Note that on the top right corner of the ND, LPPT-03 is written.
4. Take off.
5. Note that on the top right corner of the ND, LPPT-03 still is written.
6. On the MCDU, click on DIR.
7. Select waypoint GANSU and insert it into the Flightplan (i.e. making it active).

Expected behaviour The active waypoint in the ND changes from LPPT-03 to GANSU.

Observed behaviour The active next waypoint as reported by the ND stays at LPPT-03. There is no chance (or at least my knowledge/skill does not suffice to do so) to change it to something other than the RWY.

Screenshots Here are some screenshots which I took in that kind of situation. Don't be confused - I took them a little later not with GANSU (as in the example above), but with NARTA, which was just a little more down into the flight. The problem still persisted until then (i.e. 160NM from the airport).

Initial State:

Selecting Waypoint on the MCDU via DIR

Now clicking on "DIR TO INSERT"

Response of the system: none

System (please complete the following information):

• OS: Windows 10
• FlightGear version: 2020.1.3

Additional context In some cases I was able to "fix the problem" by letting the plane fly over the runway again (i.e. using AP1); then it got going (and then I was also able to program directs).

[eaglerainbow]

Am I doing something wrong?

[legoboyvdlp]

Do you have a log file?

http://wiki.flightgear.org/index.php?title=Commonly_used_debugging_tools&redirect=no#fgfs.log

[eaglerainbow]

Not yet. But I'll try to get one for you. Stand by...

[eaglerainbow]

We are lucky: The old log file was still available. It was the original session from which I also took the screenshots above.

During that session I tried it a dozen times, but no avail. I went down to LPMA with the autopilot in HDG mode only.

Note: It took me (I would guess - didn't look at the watch, though) at least 15 minutes to get things settled in the plane until I taxied to the RWY. And also taxiing took longer than normal, as I had troubles to find the way.

A good starting point for reading could be

 1413.15 [INFO]:input     C:\Jenkins\workspace\Windows-release\flightgear\src\Input\FGJoystickInput.cxx:137: Looking for bindings for joystick "Flight Rudder Pedals"
 1413.15 [INFO]:input     C:\Jenkins\workspace\Windows-release\flightgear\src\Input\FGJoystickInput.cxx:149: ... found joystick: C:/Users/Nico/AppData/Roaming/flightgear.org/Input/Joysticks/for-c172p/Flight-Rudder-Pedals.xml
 1413.15 [INFO]:input     C:\Jenkins\workspace\Windows-release\flightgear\src\Input\FGJoystickInput.cxx:137: Looking for bindings for joystick "Flight Yoke System"
 1413.15 [INFO]:input     C:\Jenkins\workspace\Windows-release\flightgear\src\Input\FGJoystickInput.cxx:149: ... found joystick: C:/Users/Nico/AppData/Roaming/flightgear.org/Input/Joysticks/Flight-Yoke-System.xml
 1413.15 [INFO]:input     C:\Jenkins\workspace\Windows-release\flightgear\src\Input\FGHIDEventInput.cxx:921: Re-Initializing HID input bindings

which I did right before starting to taxi.

 1967.78 [INFO]:flight    C:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:587: 15: GEAR_CONTACT: 1877.76 seconds: RIGHT_MLG 0
 2044.12 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:18: saw departure changed
 2044.12 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:134: creating default GPS FPDelegate
 2045.38 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:101: saw active flightplan cleared, deactivating
 2045.38 [INFO]:autopilot C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\route_mgr.cxx:799: deactivating flight plan
 2045.38 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:18: saw departure changed
 2045.38 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:39: routing via SID GANS8N
 2045.38 [WARN]:navaid    C:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\procedure.cxx:355: SID GANS8N not for runway 03
 2045.38 [WARN]:nasal     C:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalPositioned.cxx:3289: procedure.route failed for ArrivalDeparture somehow
 2045.38 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:60: routing via STAR LIDR1A
 2045.38 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:87: routing via approach VORV05
 2045.38 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:18: saw departure changed
 2045.38 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:101: saw active flightplan cleared, deactivating
 2045.38 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:134: creating default GPS FPDelegate

could be an indicator of me changing the departure configuration (in mid-air), in the hope that playing around there could make things going (but no avail -- the problem had appeared before though).

Does the log file help you? Or should I try to generate a shorter one with "less noise"?

[legoboyvdlp]

These are all harmless warnings.

Can you please just send the complete file -- looking for a Nasal runtime error?

Edit - found it in your post - sorry.

[legoboyvdlp]

Unfortunately there are none. But I will try and reproduce it.

[eaglerainbow]

Edit - found it in your post - sorry.

😄

Unfortunately there are none. But I will try and reproduce it.

Please let me know in case I can be of help.

[legoboyvdlp]

Unfortunately, I can't reproduce this :(

[eaglerainbow]

Unfortunately, I can't reproduce this :(

Thanks for the info! I will try to reproduce it myself aiming to narrow it further down, e.g. giving more detailed hints. Besides the log file above, is there anything that I can switch on which might help you track down things?

[eaglerainbow]

Just tried out a little bit myself. I suddenly also have issues reproducing it. Will keep on trying...

[eaglerainbow]

Sorry for the delay. It just happened again 😀 I was mainly doing the same thing (LPPT/LPMA) as described initially. However, this time

• I taped it on a video from start till end
• I could get it fixed shortly after takeoff myself - I don't know how I did that exactly.

Also I could save the fsgs logfile. I stumbled over the problem of around 35 mins after start of the simulator. The log file around there looks like this:

 1301.75 [INFO]:aircraft  C:\Jenkins\workspace\Windows-release\flightgear\src\Model\modelmgr.cxx:74: Adding model [unnamed]
 1301.75 [INFO]:aircraft  C:\Jenkins\workspace\Windows-release\flightgear\src\Model\modelmgr.cxx:74: Adding model [unnamed]
 1301.75 [INFO]:aircraft  C:\Jenkins\workspace\Windows-release\flightgear\src\Model\modelmgr.cxx:74: Adding model [unnamed]
 1301.75 [INFO]:aircraft  C:\Jenkins\workspace\Windows-release\flightgear\src\Model\modelmgr.cxx:74: Adding model [unnamed]
 1843.01 [INFO]:environmentC:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:493: NoaaMetarRealWxController::update(): spawning load request for station-id 'LPPT'
 1845.02 [INFO]:environmentC:\Jenkins\workspace\Windows-release\flightgear\src\Environment\fgmetar.cxx:154: 2020/09/03 13:30 LPPT 031330Z 17004KT 090V220 CAVOK 33/07 Q1018 
 1845.02 [INFO]:environmentC:\Jenkins\workspace\Windows-release\flightgear\src\Environment\fgmetar.cxx:158: METAR from tgftp.nws.noaa.gov
 2112.12 [INFO]:flight    C:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:587: 13: GEAR_CONTACT: 2070.47 seconds: NOSE_LG 0
 2114.85 [INFO]:flight    C:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:587: 14: GEAR_CONTACT: 2073.22 seconds: LEFT_MLG 0
 2114.88 [INFO]:flight    C:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:587: 15: GEAR_CONTACT: 2073.25 seconds: RIGHT_MLG 0
 2151.42 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:18: saw departure changed
 2151.42 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:134: creating default GPS FPDelegate
 2154.41 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:101: saw active flightplan cleared, deactivating
 2154.41 [INFO]:autopilot C:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\route_mgr.cxx:799: deactivating flight plan
 2154.41 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:18: saw departure changed
 2154.41 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:39: routing via SID GANS8N
 2154.41 [WARN]:navaid    C:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\procedure.cxx:355: SID GANS8N not for runway 03
 2154.41 [WARN]:nasal     C:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalPositioned.cxx:3289: procedure.route failed for ArrivalDeparture somehow
 2154.41 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:60: routing via STAR LIDR1A
 2154.41 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:87: routing via approach VORV05
 2154.41 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:18: saw departure changed
 2154.41 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:101: saw active flightplan cleared, deactivating
 2154.41 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:134: creating default GPS FPDelegate
 2154.43 [WARN]:general   C:\Jenkins\workspace\Windows-release\simgear\simgear\canvas\elements\CanvasElement.cxx:471: Element::childRemoved: unknown transform: /canvas[0]/by-index[0]/texture[5]/group[0]/map[0]/group[11]/group[1]/text[0]/tf[1]
[... - always repeating the general warning ...]
 2154.44 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/canvas/svg.nas:28: parsesvg: Skipping unknown element 'sodipodi:namedview' [path='D:/spiele/FlightGear 2020.1.3/data/Nasal/canvas/map/Airbus/Images/airbus_vor.svg']
 2154.44 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/canvas/svg.nas:28: parsesvg: Skipping unknown element 'metadata' [path='D:/spiele/FlightGear 2020.1.3/data/Nasal/canvas/map/Airbus/Images/airbus_vor.svg']
 2154.45 [WARN]:general   C:\Jenkins\workspace\Windows-release\simgear\simgear\canvas\elements\CanvasElement.cxx:471: Element::childRemoved: unknown transform: /canvas[0]/by-index[0]/texture[6]/group[0]/map[0]/group[11]/group[1]/text[0]/tf[1]
 2154.45 [WARN]:general   C:\Jenkins\workspace\Windows-release\simgear\simgear\canvas\elements\CanvasElement.cxx:471: Element::childRemoved: unknown transform: /canvas[0]/by-index[0]/texture[6]/group[0]/map[0]/group[11]/group[1]/text[1]/tf[1]
 2154.45 [WARN]:general   C:\Jenkins\workspace\Windows-release\simgear\simgear\canvas\elements\CanvasElement.cxx:471: Element::childRemoved: unknown transform: /canvas[0]/by-index[0]/texture[6]/group[0]/map[0]/group[11]/group[2]/text[0]/tf[1]
 2154.45 [WARN]:general   C:\Jenkins\workspace\Windows-release\simgear\simgear\canvas\elements\CanvasElement.cxx:471: Element::childRemoved: unknown transform: /canvas[0]/by-index[0]/texture[6]/group[0]/map[0]/group[11]/group[3]/text[0]/tf[1]
 2154.47 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/canvas/svg.nas:28: parsesvg: Skipping unknown element 'sodipodi:namedview' [path='D:/spiele/FlightGear 2020.1.3/data/Nasal/canvas/map/Airbus/Images/airbus_vor.svg']
 2154.47 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/canvas/svg.nas:28: parsesvg: Skipping unknown element 'metadata' [path='D:/spiele/FlightGear 2020.1.3/data/Nasal/canvas/map/Airbus/Images/airbus_vor.svg']
 2154.50 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:101: saw active flightplan cleared, deactivating
 2154.50 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:18: saw departure changed
 2154.50 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:39: routing via SID GANS8N
 2154.50 [WARN]:navaid    C:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\procedure.cxx:355: SID GANS8N not for runway 03
 2154.50 [WARN]:nasal     C:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalPositioned.cxx:3289: procedure.route failed for ArrivalDeparture somehow
 2154.50 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:60: routing via STAR LIDR1A
 2154.50 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:87: routing via approach VORV05
 2154.50 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:18: saw departure changed
 2154.50 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:101: saw active flightplan cleared, deactivating
 2164.23 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:18: saw departure changed
 2164.23 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:134: creating default GPS FPDelegate
 2169.16 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:101: saw active flightplan cleared, deactivating
 2169.16 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:18: saw departure changed
 2169.16 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:39: routing via SID GANS8N
 2169.16 [WARN]:navaid    C:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\procedure.cxx:355: SID GANS8N not for runway 03
 2169.16 [WARN]:nasal     C:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalPositioned.cxx:3289: procedure.route failed for ArrivalDeparture somehow
 2169.16 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:60: routing via STAR LIDR1A
 2169.16 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:87: routing via approach VORV05
 2169.16 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:18: saw departure changed
 2169.16 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:101: saw active flightplan cleared, deactivating
 2169.16 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:134: creating default GPS FPDelegate
 2169.18 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:101: saw active flightplan cleared, deactivating
 2169.18 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:18: saw departure changed
 2169.18 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:39: routing via SID GANS8N
 2169.18 [WARN]:navaid    C:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\procedure.cxx:355: SID GANS8N not for runway 03
 2169.18 [WARN]:nasal     C:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalPositioned.cxx:3289: procedure.route failed for ArrivalDeparture somehow
 2169.18 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:60: routing via STAR LIDR1A
 2169.18 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:87: routing via approach VORV05
 2169.18 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:18: saw departure changed
 2169.18 [INFO]:nasal     D:/spiele/FlightGear 2020.1.3/data/Nasal/route_manager.nas:101: saw active flightplan cleared, deactivating
 2240.88 [INFO]:terrain   C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:534: FGTileMgr: at lon = -9.06129deg, lat = 38.75deg, elev = 1288.94m, scheduling needed for:-10:3, 38:5, visibility=53670.8
 2240.88 [INFO]:terrain   C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:320: scheduling needed tiles for -10:3, 38:5, tile-width-m:21704.1, tile-height-m:13914.9
 2240.88 [INFO]:terrain   C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:278: sched_tile: new tile entry for:-10:1, 38:2
 2240.88 [INFO]:terrain   C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:278: sched_tile: new tile entry for:-10:2, 38:2
 2240.88 [INFO]:terrain   C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:278: sched_tile: new tile entry for:-10:3, 38:2
 2240.88 [INFO]:terrain   C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:278: sched_tile: new tile entry for:-9:0, 38:2
 2240.88 [INFO]:terrain   C:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:278: sched_tile: new tile entry for:-9:1, 38:2

(BTW: LPPT03-GANS8A was my SID I had entered).

The problem got "fixed" around 36:39 (that's 2199s after simulator start). At that stage, I was clearing the T/P and its following F/PLN discontinuity from the FMS. Then it switched forward automatically to my first waypoint (MONUR).

Perhaps it might be helpful to tell you that I am using pinto's navdata. The SID there is a little ugly, as it does not have MONSUR in between.

The entire video I recorded is 10GB in size. I tried to reduce it to the crucial minutes of the flight, but to be able to still see something meaningful, an excerpt still has at around 110MB.

Any suggestions on how to proceed from here?

[legoboyvdlp]

I see now what it is.

2154.50 [WARN]:navaid C:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\procedure.cxx:355: SID GANS8N not for runway 03 2154.50 [WARN]:nasal C:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalPositioned.cxx:3289: procedure.route failed for ArrivalDeparture somehow

Your navdata is invalid. To solve this, you should edit the file LPPT.procedures.xml, line 1845, to read

<Sid Name="GANS8N.03" Runways="03">

Then, you can load it correctly. Otherwise, it reads the first GANS8N it finds, which is for runway 35.

This specific error is in FlightGear rather than the A320-family, I will investigate this and see if it can be associated to a runway correctly.

Thank you for identifying this problem!