July 31, 20205 yr In this video, the PFD captured the glidescope during descent, but why did the glidescope disappeared at frame 1:48 Does this happens in the the real world? Edited July 31, 20205 yr by Billcoke
August 2, 20205 yr Billcoke, When you get the NO AUTOLAND, I notice that the ILS identifier on the PFD changes (even though the DME readout remains consistent). This is an indication that the NAV is now picking up a different ILS, thus preventing the system to continue on LAND 3. If you did not change your NAV1 frequency by accident at that time, I would then look at your installed sceneries around that airport for conflicting ILS frequency. Out of curiosity, what airport is it (default or add-on) ? Normand Intel i7 14700K @ 5.6 GHz / Asus ROG STRIX Z790E Wi-Fi / 64GB DDR5 6400 MHz / MSI RTX 4080 / PSU 1000 Watt / FS2020+FS2024 / Windows 11
August 3, 20205 yr Author 1 hour ago, NBouc said: Billcoke, When you get the NO AUTOLAND, I notice that the ILS identifier on the PFD changes (even though the DME readout remains consistent). This is an indication that the NAV is now picking up a different ILS, thus preventing the system to continue on LAND 3. If you did not change your NAV1 frequency by accident at that time, I would then look at your installed sceneries around that airport for conflicting ILS frequency. Out of curiosity, what airport is it (default or add-on) ? This video is from another flight simmer. I encountered similar "No Autoland" for Heathrow RW27R, only happened once. couldn't replicate the problem again.
Archived
This topic is now archived and is closed to further replies.