legoboyvdlp/A320-family

Bug - system state after improper/unintended AC loss on ground

Closed this issue · 1 comments

Honu4 commented

Describe the bug
I'm not sure exactly what happens, but I vaguely recall some weirdness happening before. This may not be specific to this aircraft. Could be a FG general bug.

If I forget to start APU and begin pushback, ground service power is disconnected and power is lost to aircraft, and pushback is continued in darkness. If during this pushback I start the APU, it appears that some settings will "lock" and won't change even if it looks like the change is made in MCDU. Specifically, on this last flight, ILS nav frequencies did not actually change even though the MCDU display showed the change.

I don't know what's supposed to happen in real life, but I would assume that either all settings should be wiped clean and I would have to re-enter all data for flight, or all data for flight remains and I should be able to change it as necessary.

System (please complete the following information):

  • OS: MacOS 10.15.7
  • FlightGear version: 2020.3.8
Honu4 commented

Okay, I may have jumped to an incorrect conclusion here. KJFK has some pretty bad runway data. Threshold locations & ILS frequencies are suspect.