ALERT! 3rd Party Airports are missing ILS Freq in MFD

[Noel 4,563]

I purchased three, KPDX and KSBA, and both are missing the ILS frequencies accessible thru the MFD's Airport Info, Frequencies page.  All the default airports I've flown into all over the world contain these and you can select them and make them Active as you know for your ILS approaches.  As a test, I deleted KPDX Flightbeam, so the default KPDX then becomes active and ILS frequencies appear as they should.  I zendesked this several weeks ago, they tagged it as SOLVED, and yet despite reinstalling KPDX Flightbeam just two days ago to see if they communicated this missing data field to Flightbeam, but for whatever reason the ILS frequencies remain missing.

If you're contemplating purchasing one you might hold off to help get their attention--check it out yourself and do a zendesk ticket so this can be addressed before all 3rd party airports forever are leaving out the ILS frequencies.  Seems like a classic oversight.  If this was from only one developer then I would be contacting them, and still may have to since MS/Asobo deemed my original ticket as misdirected to them, presumably because they think onus is on the developer to fix the omission.  I'm guessing the SDK for airports simply left out the ILS freq fields.

Edited November 18, 2020 by Noel

[united001 126]

I have KPDX by flightbeam. They have all of the classic ILS frequencies intact and usable, I have many, many times. That does not mean that the Flightbeam product is working properly otherwise, however. It is not. For me, It defers to runways 3-21 always and never to any of the 10-28 runways ever whether for take-off clearance nor for approach no matter wind directions. Nor does not allow blue taxi arrows ever even to 3-21. Remove Flightbeam and everything works normally. I logged this problem with Flightbeam weeks and weeks ago and despite saying they would fix it, they have not. I am imagining that the lack of a full SDK is holding up fixing many such things. I have not reported this to Zendesk, however and probably won't. Good luck!
United001 

[Noel 4,563]

Just now, united001 said:

I have KPDX by flightbeam. They have all of the classic ILS frequencies intact and usable, I have many, many times. That does not mean that the Flightbeam product is working properly otherwise, however. It is not. For me, It defers to runways 3-21 always and never to any of the 10-28 runways ever whether for take-off clearance nor for approach no matter wind directions. Nor does not allow blue taxi arrows ever even to 3-21. Remove Flightbeam and everything works normally. I logged this problem with Flightbeam weeks and weeks ago and despite saying they would fix it, they have not. I am imagining that the lack of a full SDK is holding up fixing many such things. I have not reported this to Zendesk, however and probably won't. Good luck!
United001 

Ok very good to know thanks.  What plane are you using to demonstrate this so I can duplicate, perhaps this is an issue w/ the TBM930 which is my default plane.  Same same for KSBA.

[Nyxx 6,994]

ALERT!

Fightbeam KPDX and Orbx KSBA all work fine for me. ILS info from Navigraph charts work perfect.

Edited November 18, 2020 by Nyxx

[sd_flyer 6,087]

15 minutes ago, Noel said:

I purchased three, KPDX and KSBA, and both are missing the ILS frequencies accessible thru the MFD's Airport Info, Frequencies page.  All the default airports I've flown into all over the world contain these and you can select them and make them Active as you know for your ILS approaches.  As a test, I deleted KPDX Flightbeam, so the default KPDX then becomes active and ILS frequencies appear as they should.  I zendesked this several weeks ago, they tagged it as SOLVED, and yet despite reinstalling KPDX Flightbeam just two days ago to see if they communicated this missing data field to Flightbeam, but for whatever reason the ILS frequencies remain missing.

If you're contemplating purchasing one you might hold off to help get their attention--check it out yourself and do a zendesk ticket so this can be addressed before all 3rd party airports forever are leaving out the ILS frequencies.  Seems like a classic oversight.  If this was from only one developer then I would be contacting them, and still may have to since MS/Asobo deemed my original ticket as misdirected to them, presumably because they think onus is on the developer to fix the omission.  I'm guessing the SDK for airports simply left out the ILS freq fields.

Before you make an assumption you have to figure out a cause! All airport you listed do have ILS frequencies which works fine. However, there is inconsistency  with certain aircraft which auto tune ILS frequencies when desired approach is selected. It works for default airport, but for 3rd patty airports one has to dial frequencies manually. In any case it is a good habit to cross check approach frequencies and brief approach prior landing  

[mtr75 653]

29 minutes ago, Noel said:

I purchased three, KPDX and KSBA, and both are missing the ILS frequencies accessible thru the MFD's Airport Info, Frequencies page.  All the default airports I've flown into all over the world contain these and you can select them and make them Active as you know for your ILS approaches.  As a test, I deleted KPDX Flightbeam, so the default KPDX then becomes active and ILS frequencies appear as they should.  I zendesked this several weeks ago, they tagged it as SOLVED, and yet despite reinstalling KPDX Flightbeam just two days ago to see if they communicated this missing data field to Flightbeam, but for whatever reason the ILS frequencies remain missing.

If you're contemplating purchasing one you might hold off to help get their attention--check it out yourself and do a zendesk ticket so this can be addressed before all 3rd party airports forever are leaving out the ILS frequencies.  Seems like a classic oversight.  If this was from only one developer then I would be contacting them, and still may have to since MS/Asobo deemed my original ticket as misdirected to them, presumably because they think onus is on the developer to fix the omission.  I'm guessing the SDK for airports simply left out the ILS freq fields.

Have you tried manually dialing in the frequencies? If so I would agree that this is a problem. If not, try it. I bet it will work.

Edited November 18, 2020 by mtr75

[wthomas33065 994]

I can confirm, that it's not that the airports are missing the frequencies, it's that the FMC or avionics don't autotune to the frequency when you choose the appropriate approach and load it in. 

This could be a bug in the scenery or it could be the way that the avionics fetches the ILS frequencies and autotunes the radio.  I am not a pilot so I am not sure if the real FMC's/Avionics suites do this for the pilot or if this is just a function of the sim trying to simplify things for the pilot, or a bug in how the AI copilot automatically tunes radios.

In any case, can we retitle the thread to actually describe the issue being discussed without the 911 Alert to stop buying all third party airports?

Really guys, the histrionics are getting a little out of hand......ALERT!!!!! ALERT!!!!! DANGER WILL ROBINSON!!!!

Edited November 18, 2020 by wthomas33065

[roi1862 611]

Haha from the title i was sure im gonna see something like: "MSFS coming to life end in 2 days..." lol 

Edited November 18, 2020 by roi1862

[Manny 1,293]

This issue is frustratiing. I had to buy SimPlatesUltra so I can type in the frequency especially non non US Airports where approach plates are hard to comeby on the internet.

I am not exactly sure who the cultprit is, Many of the Addons do have missing ILS Frequency not poping up on my FMC. Some pop up on the B787 but not the A320 Neo (Modified)

So not sure who to blame... 🙂

[leprechaunlive 1,861]

STOP telling us to STOP. 

[duckbilled 310]

2 minutes ago, leprechaunlive said:

STOP telling us to STOP. 

Stop telling us to stop telling us to stop

[icewater5 181]

lol, what a thread🙃 Might help to know what planes this happens with ( i think someone already said that). Otherwise Navigraph or something, until this gets fixed.

Edited November 18, 2020 by icewater5

[mtr75 653]

36 minutes ago, leprechaunlive said:

STOP telling us to STOP. 

Not to mention impugning 3rd party developers for something that isn't their fault. 

[leprechaunlive 1,861]

16 minutes ago, mtr75 said:

Not to mention impugning 3rd party developers for something that isn't their fault. 

Yea, i facepalm a lot lately reading some people 😄

[mtr75 653]

1 hour ago, leprechaunlive said:

Yea, i facepalm a lot lately reading some people 😄

Yeah and if you saw the initial thread title, it said “don’t buy third party addons.”