Default a320neo
Series X / latest update.
I noticed when I was on approach into Faro that none of the ILS info displayed on the screen after pressing the ILS button, so I could not see the info such as the distance to runway. It did still capture though.
Only addons I have is some liveries by 4simmers.
I tried both ILS approaches to Faro on rwy 10 and 28 in an A320 (XBox) and didn’t get the purple diamonds in both cases thus the ILS approaches failed. Landed manually instead. Tried both approaches quite a few times successfully before WU8.
Thanks for confirming that.
It was runway 10 I was landing, but as said it did still capture the ILS.
Sorry for asking but I’m still new to ILS: what do you mean “still captured ILS”? My assumption is that when you engage “Appr” and “Loc” (and the ILS receiver frequencies are correct) the PFD is supposed to display the purple diamonds for hight and position deviation from hight and Center of the runway. If it does not then for me “ILS is not captured” if that is the right expression.
I’m new as well, so my terms may be incorrect, what I mean is the info such as the purple diamonds on the display do not show, but with the approach button activated it still captured the ILS frequency and started to descend automatically.
Have you made sure the ILS frequency is tuned in the NAV RAD page of the MCDU?
Ah, thanks for the hint! 
I need to check that. That would explain why I neither got the diamonds nor did the descent start automatically.
My assumption is: entering the frequencies in this case could circumvent the problem as the problem stems from the missing frequencies only. The 2nd ILS problem I have is with EDDS (Stuttgart) where I come down offset to the runway: there I do have the diamonds and descent starts automatically but touchdown is offset by at least 300ft to the right (both approaches). I assume checking the frequencies would be good as well but most likely they’r correct and the offset is a real problem that can not be overcome by working something in the cockpit.
I keep forgetting to check that, but in my case if the ILS info and pink diamonds not displaying, yet still captured the glidescope would the ILS freq not have been tuned?
The Question would be: how do you recognise the glideslope being kept?
With help of @Neo4316 
I was able to successfully land in Faro (LPFR) 
These are my observations:
Interesting, sounds like the reason no ILS info displayed for me then with runway 10.
Thanks for the info.
Hmm… I think your google search might have been a bit out-dated. I checked in Navigraph, and Faro has ILS for both sides of the runway. And there are two ILS approaches to RWY 10. ILS Z and ILS Y.
It may not be CAT I/II certified the same way as ILS RWY 28. But it is a certified ILS approach nonetheless. So both needs to be there and not removed.
Thanks for checking and sharing the airport chart. I think you have the more reliable source so I believe you’re correct. Thanks again for checking this.
… one of the two major disadvsntages for simmers using Xbox: they are not so much looking into Navigraph as the XBox doesn’t allow to attach such Tools directly…
You don’t really need to install the navigraph in your Xbox, Navigraph is platform-independent. meaning you can access it using your phone, tablet, or even using your we browser.
But yes, the default NavData that’s loaded from Navigraph can’t be installed in Xbox and that would make it as a disadvantage because navigraph navdata actually fixed a lot of the navdata issues coming from the default navdata such as localiser misalignment, etc.
But charts, wise… everyone subscribed to it can access it just fine. So even on Xbox, you can just open the charts and refer to it for all your IFR flights.
At LECO La Coruña, the information from the ILS on the approach to runway 21 also failed me, before the update it did not happen
Again, did you make sure the ILS frequency is tuned with 109.9 in the MCDU NAV RAD page?
I planned the flight with the FS world map, the MCDU data is supposed to be added automatically.
The last time I flew the default A320neo was before the FBW A32NX was released. Back then, the MCDU data is always blank, regardless of the flight plan that was loaded. And I have to enter the frequency every time. The FBW A32NX automatically fill this ILS frequency as you said, but we’re not talking about the FBW A32NX in this topic.
Usually, checking the MCDU NAV RAD page forms as part of the setting up the approach before you start your descent. So forgetting to check the ILS frequency to make sure it’s actually loaded could be classified as pilot error.
In my case, I was not talking about the FBW A32NX, I fly the FS A320 Neo by default.
Problem might be different if you have tdm scenery design 3rd party airport installed for A Coruna: just checked, ils frequency is set to 109.9 MHz in the mcdu but unfortunately the landing fails neveretheless as the glidepath doesn’t go to the rwy (21) but is offset a good bit to the right. Have to check if this also happens w. the default MS/Asobo airport.
You actually can see the offset in the navigation display: the yellow plane is offset to the right from the green glidepath…
PS: rwy 03 does not seem to have ILS…
So I might sign up as well because I was still searching for good charts and could still enter data manually.
I always fly the default 320 here and set up via world map and leave the approach on automatic, when I have entered the approach in flight it has always entered the ILS freq automatically, in most cases anyway.
My issue was the info not displaying like the pink diamonds on the main display, it still captured the glidescope.
I will check from now on though.
