Just a moment, I’ll take the screenshots again and upload them.
Ok, now it is clear… the signal will be received, but only the DME. You see the ident right of the frequency, so good … you see the DME distance to the VOR, so good … but the VOR portion can´t be loaded because the frequency is not green and you don´t see a green arrow in the rose.
This is a typical scenery issue: any scenery includes this VOR, but not as a VOR, only as DME, and this scenery overrules our data. The root question now is, why are packages still loaded?
Have you bought Marketplace sceneries? Or use scenery from MSFS2020?
Cheers
Richard
Yes, originally at the departure airport, VOR, DME, and ILS were all transmitting and working fine. However, from the moment I started approaching the destination, the reception of VOR and DME was lost and only the frequency was displayed. The ILS also had the correct frequency and course set, but the ILS name was not for the destination—it was still showing the one from the departure airport.
Also, I am not using a Marketplace scenery. I am using a 2020 version scenery placed in the 2024 Community folder, and I currently do not have MSFS 2020 installed on my computer.
It doesn’t really seem like a scenery-specific issue, because this does not happen at the departure airport, and it also did not happen before the AIRAC 2601 update. Since the same behavior occurs with all sceneries, it seems unlikely that this is caused by a single scenery.
Understood, my experience over the past years says the opposite, and I’m still sure this is an issue with any 3rd-party package you have installed because it is isolated on your system.
As I have written before, when it is a general AIRAC issue, we would see a lot more reports like this, and I would reproduce them. But nothing… No reports, nor is it reproducible as you see it in my screenshot.
The only difference between our systems seems to be the installation of 3rd-party packages (scenery and/or aircraft).
Sorry, but my knowledge ends here.
Cheers
Richard
Thank you for your help. I restored all the Community files and deleted the Navigraph-related data, and after flying again, everything worked without any issues.
Thank you, but this is expected because the stock data has always had the highest priority and therefore always works.
But anyway, when you are happy with your “solution” - to remove our data due to a misconfiguration on your system, it is fine.
I only want to clarify that this is not a navdata issue. Thank you for your feedback.
Cheers
Richard