I have noticed over the past few updates and so far consistent for me that when flying the A320NX on a flight plan with an ILS approach into a payware airport like KMIA, KSAN, or KPDX, that the ILS is not captured.  In a smaller aircraft, I would be putting in the frequency but with the flightplan loaded in the airbus, shouldn't be required.  I have flown ILS approaches plenty of time with the A320 into stock airports just fine.  Is there a database or something not getting updated when the payware airports are installed that doesn't allow for the ILS frequency to be populated in the MCDU.  Has anyone else experienced this with there payware airport addons?

You need to input the ILS frequency manually on the RAD/NAV page when approaching to payware airports with the A320NX. I hope that this behavior will be corrected in the future.

Patric

I submitted a zendesk ticket on Oct 11, they say it's 'solved' but apparently it must not be.  Here's what I sent them, but I haven't gone back yet to those two payware airports to see if ILS freq were now listed:

October 11, 2020 17:14

I purchased FSDT's KPDX-HD thru the Marketplace, and ORBX's KSBA through their Orbx Central. Both installed fine. But in the TBM930's MFD, Airport Information panel, when you choose Frequencies there are no ILS entries, nor cells to enter them in. Fortunately, after deleting KPDX the ILS frequencies reappeared. Please investigate why BOTH products, from different developers have the same problem. I will be sure to not purchase addition airport enhancements until this is addressed. Also, I did purchase Tacoma Narrows, but haven't had a chance to see if it's a problem too. Thanks

I will go back and check on those two payware airports next time up.

Now that you mention it, I have had this issue with a payware airport too, FALE by Gaffer Simulations. A320X definitely has issues capturing LOC and GS. I have been meaning to contact the dev about it but not got around to it. Maybe a more common issue than a add-on dev mistake then. I do enter ILS frequency and course into the FMGC. Usually ILS frequency is correctly loaded automatically based on flight plan but course is not.

To be clear, I don't think this is a developer issue at all.  I believe this is an Asobo issue.  Payware airports from lots of developers integrated ILS information seemlessly in  P3D and FSX into the navigation and autopilot databases.  There is clearly a bug in the program itself that needs to be fixed, and is not the product of many developers leaving ILS information out of their products.  I know the workaround is to manually add the frequency prior to approach, but shouldn't have to do that.

2 hours ago, bszuch said:

To be clear, I don't think this is a developer issue at all.  I believe this is an Asobo issue.  Payware airports from lots of developers integrated ILS information seemlessly in  P3D and FSX into the navigation and autopilot databases.  There is clearly a bug in the program itself that needs to be fixed, and is not the product of many developers leaving ILS information out of their products.  I know the workaround is to manually add the frequency prior to approach, but shouldn't have to do that.

Yes this ^^^^

Hm, I yesterday observed that the 320nx didn't capture ILS on runway 25R in EDDF. Not payware but stock airport. Original 320NEO does capture. I forgot to look in the rad/nav page if the frequency was entered but this also is a 320nx issue at least partially.

On 11/18/2020 at 5:57 PM, bszuch said:

To be clear, I don't think this is a developer issue at all.  I believe this is an Asobo issue.  

Well, it's common to at least the three airports I bought, one thru OrbxDirect, and two thru the Marketplace in-sim.  This suggests something in the SDK is missing, like ILS data fields that map to the MFD Frequencies page, or something is misleading in the SDK that would lead to all three different 3rd party developers to make the same mistake.  Doesn't seem like a big deal to troubleshoot, but getting someone's attention is an entirely different story.  I went to Orbx first, weeks ago, and they haven't really responded yet.   A kneejerk response from a MSFS forum administrator (I believe he was representing MS/Asobo) was this was a problem w/ the 3rd party developer--so he completely ignored my careful clear message to understand all three different developers created addon airports w/ the same anomaly.  Oh well, I tried.

Here's the statement frome someone who knows...

And acc. to today's development update not to be fixed with the coming world update.

Edited November 20, 20205 yr by Tom_L