Hello since cycle 2410 when tuning ILS on any pmdg 737 model there is no ils reception
After investigate the issue it seems that the problem is in main MSFS navdata installation from navigraph, when i remove the installation and only the PMDG navdata installed the ILS is working.
1 Like
Looks the same for me with SWS PC15 and TBM850 so far. It worked yesterday since I don’t have any bush trips installed
Hi @ezman1980,
Welcome to Navigraph - thanks for the report. Please let me check this …
Also, thanks @KaptenEk, for your confirmation - I will look at it immediately …
Cheers,
Richard
1 Like
Guys,
I can confirm this. I’m just checking the code and will build a second revision. Sorry for that mistake, and thanks for the hint, folks - it’s much appreciated. I will inform you here when the AIRAC is updated.
Cheers,
Richard
3 Likes
I can confirm the ILS issue with both, Blacksquare Duke and stock Cessna 152, with and without 3rd party GPS units. Uninstalling base packages is a workaround (similar to AAU3 issue).
Timelines crossed 
Thanks for the quick reaction!
1 Like
Great for quick respond and action 
AIRAC 2410 revision 2 is out now … this should fix the missing ILS information in the MSFS data!
Please go into the Hub and re-install the cycle again.
Please can someone confirm that it´s fixed
Sorry again!
Cheers,
Richard
PS: I have changed the title/subject a little bit to make it clearer - hope that’s ok
1 Like
ILS seems to be resolved. I’m still having trouble with regular VOR ranges, but that could be a 3rd party issue. Thanks again for the quick response! 
Thanks for your fast response!
As far as I know, these ranges are static/fixed in the MSFS, which means the MSFS uses only a default value. I’m not sure what it is, but we have tried something with Navaid and ILS ranges without success.
Cheers,
Richard
It could be a feature (not a bug) of the Duke I just used for testing. I’ll have to x-check with a stock Cessna and the DC-6. I remember MSFS being a bit odd with ranges (coming from X-Plane) but in either case it should be unrelated to the ILS issue. I have to leave now, but I’ll look into it later tonight or tomorrow. Thanks for the background!
1 Like
Confirm that the update as well work fine for SWS PC12 and BS TBM850
1 Like
Thank you very much, @KaptenEk, for your feedback. It is much appreciated, and I am sorry for my mistake. There were a few long nights in the past few days
Cheers,
Richard
1 Like
problem solved , thank you very much for the quick solution
1 Like
I came here to know about this, becuse flying in FBW A320 I had that issue in Geneva.
And, it seems to be solved.
Thanks a lot!
1 Like
Thanks, folks, for all your confirmations. This is precisely why I love my job (sometimes, no very often 
)—the direct contact with you, the community, and our users. Thanks again!
Cheers,
Richard
1 Like
Can confirm the latest revision seems to at least ‘bring my needles’ back to life, so to speak. But I’m not sure if there’s something else going on: if you tune into KSLC RWY16R, 111.90, the instruments indicate correct localiser/GS deviation again. However, at least using the stock WT GNS430/530, the station identifier IUAT is never shown or indicated. I don’t know what causes this issue.
Yes I noticed that ILS was not present in 2410 at GMMH airport today. It was ok 2 days ago. (I was using 2409 Airac)
ok I thought I was going nuts. Flying PMDG 777-300ER into LOWW ILS 34 yesterday no ILS. Just now flying into Lagos 18L, no ILS.
Updated to Rev.2 hope I have better luck flying into Warsaw on Saturday.
@NAVDataOld Wouldn’t an email to users have been a good idea with a problem of such magnitude? I just spent several hours trying to isolate the problem.