so then I hear all traffic even from other airfields and atc gets spammed
when uninstalling navigraph cycle 2506 through navigraph hub, frequencies go back to normal, atc offers right frequency, 135.155
happens also at other untowered airfields
I have the same problem,with another airport. Not to say many. With the latest airac cycle, all untowered airports default to 122.900… in msfs2020 and 2024. navigraph charts shows 135.25 but in sim is only 122.900. so I hear all the traffic from all airports around me… there is somethign wrong with the navdata.because when I remove airac cycle through navigraph hub, all frequencies are back to normal
Hi again,
I have checked the frequencies of your example EDKB, but we don´t have 122.900 as a frequency in our data. I have also checked this in the MSFS2024, and I see the correct frequencies:
So, it must be any other issue on your system. Do you have any 3rd party scenery installed, especially for EDKB? It could also be a 3rd party scenery issue because the frequency does not exist in our data …
Have you tried to set the priority according to our FAQ?
Yes I am using 3rd party scenery.I tried with the default scenery but same. 122.900 seems to be unicom standard in msfs20/24 which might be realistic in remote US regions with low to no traffic but not in central europe with its hundreds of active airfields… But I dont think it was like that until the su2 update. If I turn on com1 I can hear all the traffic from all airfields. It wasnt like that before. Before I tuned into 135.155 and only heard the traffic tuned to the same frequency at EDKB, before tuning to center after takeoff. This is another fail from asobo, nothing I can do.I reinstalled the entire sim, navigraph, to no avail. It seems its just the way it is now in MSFS
I completely reinstalled windows just for the sake to solve this, however as soon as I install navigraph latest airac cycle, the frequencies on some airports just disappear and are stuck on 122.900. but not on all airports. as soon as I remove navigraph-navdata from community, all frequencies are back. So it has to be a fault in the navdata. there are als other reports on other forums about this that date back to 2022. also happens in msfs2020 so its not a msfs2024 or su3 beta thing. something is missing in the airac cycle package
I also dont have the “unicom” frequency for EDKB on the world map when having navigraph installed. Without navigraph, everything normal. Has to be a problem with the navdata. Frequencies are just missing for some airports. as you can see, on other airports (here EDGS Siegerland) all frequencies show up correctly.This is all with only navigraph installed.
Hi,
I will check your example airport, but I’m pretty sure this is not a data issue, but a package order issue with your scenery. One package “overrules” another package, which you see here.
Please upload your content.xml file here so I can check your scenery.
Also, have you tried the data in a vanilla state of the sim without any 3rd party scenery? When not, please try it to check if the frequencies are there or not. I will do the same and will post the result.
After that, you can add one scenery by object to identify which scenery is the culprit or must be re-ordered in the loading order. Again, this is nothing we have in our hands; this is a logical thing in the sim. Therefore, ASOBO offers the re-order tool, so that the end user can re-order the loading order themselves. I’m sorry that this is not very user-friendly. We must use the tools and logic from the sim.
I will try your examples and get back to you here.
Thanks for the quick reply. Here is my content.xml
In default scenery with empty community folder the frequencies are there.
In default scenery with navigraph-navdata-base installed in community, frequencies are missing. The same goes for 3rd party scenery.
As you can see in my previous post, it does not affect all airports, thats why Im confused. If it was a navdata priority problem it should affect all airports?
Sorry, I see everything is disabled in my content.xml something must have went wrong uploading, here is the correct current content.xml Content.xml (92.5 KB)
Hi again,
I have re-checked EDKB, and we have only one com frequency, 135.155, in our data. I have shown you the screenshot before, showing that we offer the same frequency in the data. We don´t have any other frequency, so it must come from somewhere—possibly third-party scenery, but not from our data.
When it would be a navdata issue, it wouldn´t show up correctly either. So it must be any other issue, as I wrote before. I´m nearly 100% sure that any 3rd party scenery overrules the navdata packages.
Hi Andy,
I have changed your content.xml file slightly. Can you please try this file on your system? Please make a backup of your original file first.
I have added the priority attribute to load our navdata package
as the last package.
Thank you, I tried but the problem is still there. I only have navigraph-navdata-base and navigraph-nav-jepp in my community folder right now so I dont see which 3rd party scenery should overrule the navdata package… I still only get “tune EDKB traffic on 122.900” in atc even though in world map it shows FSS 135.155. It just doesnt make sense xD Thats why I thought maybe the right frequency is just missing in the navdata, because in default vanilla state its there (123.525).
Andy, is it possible that your community folder is on an different location? Can you check your community-folder path in the sim? Is the community folder really equal?
I ask because it could be possible that you look into the wrong folder …
I suppose It is something ASOBO did with the atc logic… because even in complete vanilla state, I get the correct frequencies, but I can hear all the ai traffic all around me from other airports. Probably have to wait for SU3 final release and see if its better. Like this the sim has become useless for me now, at least for vfr flying