NO ILS or VORs working

Since updating the MSFS 2024 data to AIRAC 2611 I now have no VOR or ILS data working for any aircraft within the sim. The data has installed correctly into the FMCs of two add on aircraft I have installed (PMDG 737-700/800), but none of the aircraft within the sim are able to receive any ILS or VOR signal.

I’ve tried uninstalling and re-installing multiple times, hasn’t made any difference!

Hi,
Any other 3rd-party packages/scenarios installed in your community folder and/or via the Marketplace?

If yes, remove/disable them for testing, reinstall our cycle, and try again. In 99% of cases, it is an incompatible package.

I can’t reproduce it - I have no 3rd-party packages installed - using the stock scenery only.

Cheers
Richard

Sorry to say I am having the same problem. With Navigraph navdata 2611 Rev. 3 installed, none of the default aircraft (A320 neo V2, A330, etc.) are able to tune any VOR or ILS frequencies. The problem also affects add-on aircraft like the Aerosoft CRJ-900, the FSS Boeing 727-200 and the Inibuilds A350. Only the Fenix A320 works fine.
If I de-install the AIRAC cycle through the Navigraph Hub (as well as the add-on package for the CRJs), all aircraft are able to tune ILS and VOR frequencies again.

I have been trying by setting the aircraft on the runway at VABB and tuning BBB VOR as well as different VABB ILS frequencies.

Hi,
And you can confirm you have done (when you have any 3rd party packages installed) what I have written in the posting above your posting?

MSFS2024 1.9.21.0 - stock scenery - stock G1000 - VABB ILS 27 - AIRAC 2611 rev. 3 installed:

… VOR BBB:

Cheers,
Richard

Hi Richard,
I just did a comprehensive test - let me add that it causes a lot of pain to clear out my community folder, because I have a lot of add-ons (all of which were working fine with Navigraph up to cycle 2610). However, I do understand the need for a clear baseline.

Anyway: this is what I get in MSFS24 1.9.21.0 with nothing in the community folder but the Navigraph add-ons (including AIRAC cycle 2611 Rev. 3) installed through the Navigraph Hub (Default Cessna 172 with G1000):

As you can see, neither the VOR on 116.6 nor the ILS on 110.3 is recognized by the aircraft.

I then exited the flight simulator and de-installed only the Navigraph navdata through the hub. I restarted the sim and set up the same situation (VABB Rwy 27). This is what I get now:

You can see that now both the VOR and the ILS are recognized, and the distance is displayed correctly. In addition, NMB VOR on 117.8 is also tuned on NAV2.

Having removed everything else from the community folder, it is hard for me to assume the cause of this is anything else than a bug in AIRAC cycle 2611. I just wonder why you can’t replicate it.

So now I’ll go back to restoring the community folder the way it was…

Hi,
Next time, to avoid some manual work:

  1. Rename the community folder
  2. restart the sim → the sim creates a new empty community folder → close the sim
  3. go into the Hub and install the AIRAC cycle
  4. Restart the sim and do your tests

When finished, remove the community folder and rename the old community folder back to its original name. That’s it - 1-2 min of work. Just in case you need it again …

Back to your issue:
No, there is no bug in the data - it seems you are also a customer who is affected by an (at least for us) unknown bug.

I have explained my concerns, along with the official API link, in this posting.

We have now collected several different situations, and all seem to be related to this facility API (caching, reorg, … whatever we don´t know). It is clear that when you remove our data, everything is back because the SIM also includes data, and it can´t be deleted or replaced.

Something is happening behind, but we have no clue what… Yes, as you can see, it is working on my system, and honestly, I have never reproduced this issue on it. That is bad, of course, because where should I look when it happens only on a few systems?

What should I say? No idea at the moment, and we are waiting on the fix from ASOBO/MS, which should solve this on every system (hopefully).

Cheers
Richard

PS: What we can see is that, in most cases, users with a lot of 3rd-party packages are affected - I have nearly zero 3rd-party packages installed - so that could also be a reason.

I understand it is hard for you to do anything if you can’t replicate the bug.
Thanks for the tips on renaming the community folder - I will definitely try that next time.

In the meantime, I guess I’ll be reduced to flying the Fenix A320, as somehow that is not affected.

I am somewhat reluctant to assume that having many 3rd-party packages is the cause of the problem. If it were so, why would it still not work after removing all those packages? And why was everything fine until recently? the 3rd-party packages haven’t changed in the last few days.

Anyway, I’d appreciate if you can continue to keep your eyes open for any possible solutions that might come up. Last, but not least, you might have some contact at MS/Asobe where you can place this issue as a dev, where I as a normal user would never get…

Regards,
Christian

Hi Christian,
Thank you very much for your kind words - yes, we will keep the ball rolling, and I will keep you informed here. It is also frustrating for us that we can’t dig deeper into it …

But here’s exactly what I mean. Fenix uses an external database – BUT it needs the SIM signal, and that signal comes from the BGLs installed (stock or our data). I.e., if there is no VOR in the SIM but there is in Fenix, it wouldn’t work. So, there seems to be a signal – the VOR/ILS is there in the SIM, but for some reason it can’t be addressed or activated via this internal facility API.

That is what I don´t understand … you can receive it with an external add-on, but you can´t receive it with a stock aircraft - the external add-on uses its own logic, its own access; the stock aircraft uses the internal API.

Something is strange here …

Unfortunately, this is a misconception in the community. We have the same status as you as a normal user. Microsoft rejects a cooperation with us or is not interested in one. Unfortunately, we are not an official partner and therefore do not enjoy the same advantages as some other 3rd party manufacturers. All this makes it a lot more difficult for us, but we have found a solution for everything so far – so we will succeed in this case as well.

Cheers
Richard

I’ve managed to get it working again, not sure if this step was a coincidence or actually solved the problem but it’s been fine since…

Settings>General Options>Experimental

Package re-order tool - ON

Reset default package order - YES

Haven’t had any issues since.

WOW, great info, Martin :clap::clap::clap::clap::clap:

Well done, great job, and thanks for sharing your solution … what great news!
Thank you very, very, very much …

It looks like deleting the content file and re-creating it through the SIM is not enough. Therefore, this information is extremely important!!! valuable…

BRAVO :clap:

Enjoy your evening,
Richard

@WernerAir … can you test the solution from Martin

  • Settings → General Options → Experimental
  • Package re-order tool - ON
  • Reset default package order - YES

Does this fix your issue also? Finger crossing …

Cheers,
Richard