Have you got any response yet?
It seems like the developers are working with Asobo…but not getting very far.
A quote from the first thread in the link above:
"It is the 4th time in a year and half that it is happening.
This time , a new compilation with last SDK don’t fix the issue so i need to redo from scracth once again all the ILSs , hoping it is not the custom ILS who can’t work on this airportsince SU11.
Can you please take care of this basic when you are doing a sim update."
They would have a look at it 
Glad to have spotted this thread, this is becoming a right pain.
I’ve got to the point that I’m reluctant to buy more additional airports in the sale.
What a crazy game
1 Like
ILS on Beautiful Model of the World Genoa LIMJ is broken for me as well.
Frequency is 109.3 (runway 28) and is working for me. Beware, LOC is 2° offset.
Today you can find an update in the maketplace for EDDK from aerosoft. Should fix the problem. So one out of hundred is fixed…
I’m not sure if this is part of the same problem, but I notice that for a number of addon airports the ILS frequencies are not visible in the APT/freq pages of default GPSs (G1000, GNS530 up to date with AAU1).
In such cases there is no automatic capture for LOC & GS, if approaching via GPS transitions. I can manually switch from GPS to VLOC and then things work fine, so they’re still in there, just not behaving as normal. If I use the stock airports instead of addons, then things work as expected.
I noticed that Asobo’s own EGGP (Liverpool) suffers from this, so I’m wondering if it’s a bug or at least a gotcha which catches out scenery creators. However this applies to default frequencies, not specifically custom, so it may be a separate issue.
I think the topic can be locked since the AAU1 update solved the issue.
1 Like
Thanks a lot for letting us now that it’s actually fixed. I already gave up on the custom airports. No I can fly to them and from them again 
I have a similar issue with the Aerosoft Scenery of EDSB. When I choose a SID in the FBW A32NX it is just a direct to the next waypoint. Deleted the scenery and it works again.
Is this problem really fixed? I still have this problem with the scenery of EDDW from the marketplace.
FlyTampa 26L and 26R still not aligned for me.
First of all, FlyTampa 26L and 26R what airport? I can’t check the actual ILS’s you’re talking about without knowing this.
Second, misaligned ILS’s is a different problem. From what I read above, the problem being discussed previously in this thread was that airports that had created custom ILS data, the waypoint data was deleted. Essentially, choosing to “Delete ILS data” in the airport definition also deleted the approach and departure waypoints as well.
Misaligned or offset ILS’s is a different problem. In some cases, the ILS is actually offset due to obstructions and or where they were able to place the ILS equipment. And I think this feature might also have issues in MSFS itself when you attempt to offset an ILS. Or FlyTampa screwed up in their definition and you should contact FlyTampa. Or FlyTampa didn’t create custom ILS data, and their runways don’t align with the base package runways, or Asobo’s definition of those ILS’s was incorrect to start with.
In any event, there’s no way to help you get to the bottom of this without knowing what airport you are talking about. They’ve created several airports for MSFS.