Do you have any add-ons in your Community folder? If yes, please remove and retest before posting.
No
Are you using Developer Mode or made changes in it?
No
Brief description of the issue:
Everything is the same and starting last week 787 can’t or won’t detect ILS at any airports. But other aircrafts are normal.
Provide Screenshot(s)/video(s) of the issue encountered:
Nil
Detail steps to reproduce the issue encountered:
set up the flight plan as usual and then start the flight. Everything is normal until the last 20 nm . No ILS could be detected or Appr system could be activated.
PC specs for those who want to assist (if not entered in your profile)
GTX 2080 super
Build Version # when you first started experiencing this issue:
Before the last update
Are you on the Steam or Microsoft Store version?
Steam Did you submit this to Zendesk? If so, what is your ticket #?
No
Is that a Mandela Effect or what? Because I never need to do that before as it was 100% able captured the ILS every time but maybe I’ll try to do what you told me. Thanks. But do you think it’s normal for this kind of issue or I just woke up from my dream?
AFAIK, the auto tune feature has been (partially?) disabled since the previuos update because it tended to sometimes incorrectly tune in the opposite runway ILS.
What we call simulation means to simulate or to get more close to the reality. But if I have to input the ILS Frequency into the FMC of a 787 every time before it takes off, is that reality or something me can call it a flight simulator?
You don’t put the frequency in before takeoff.
Usually before starting the descent when you know which runway you are landing on.
Only newer aircraft can autotune the ILS.
Even if it is autotuned you have to recheck the frequency and inbound course IRL (and in the sim)
Yes, but this was something never need to be conducted before. So what’s the change for and I don’t know if this is an upgrade or downgrade of the sim.
I’d never been able to tune ADF/ILS on my home airport but I heard other humans were doing fine at least with all other beacons. I’d put a ticket in Zendesk with it, but it was closed half year ago. Maybe there are bugs with some beacons, or radio receivers for some values in general.
