Suddenly all airports are missing atc control, I just did a quick flight in the Islander from EDDH to EDDW and both airports were uncontrolled. Checked some other airports too. Has anybody got an idea why this is happening?
By any chance did you remove Navigraph recently? And was it through NavCenter utility?
I havent used Navigraph for some months now, still have it installed, but not updated.
so I have to pay for navigraph now to access navdata center only to delete the navdata and hope this maybe solves the problem? because msfs suddenly out of the blue decided “oh you know what worked really well for a long time? the atc! lets randomly change something so it doesnt work anymore” …
It’s a likely possibility that it’s a Navdata conflict. Nothing else really explains a loss of AIRAC data like that.
I think so too, makes sense. Anyway thanks for your kind anwers!
fixed by re-subscribing to navigraph and updating the airac-cycle…
well… partially fixed. after takeoff and changing frequency from tower to center, after acknowledging squawk code, atc ignores me for the whole flight. I can hear atc talk to ai traffic though.I am also missing in-flight atc options, like cancel flight following and nearest airports etc. Only after landing and leaving the runway, tower contacts me again for ground handoff… what is happening
If you take off VFR, then the last person you are typically required to talk to is the departing Tower (or if no tower, Unicom).
It is ten up to you, if you want VFR Flight Following, to contact an appropriate controller, and make your request.
Hopefully, MSFS ATC menu gives you those options,
- Clearance into Class B
- Flight Following
- Get IFR Clearance
plus a few more options, like nearest Airport, talk to its Tower, etc etc
ATC menu is a massive compromise, between supplying sufficient options, and also not displaying a massively long list that exceeds 9 options, ie 1,2,3,–,8,9
Hopefully, ATC will be improved in 2023, especially if enough requests to do so come from the MSFS Community.
To me, its a great shame that an ATC SDK can not be opened up for 3PD developers.
Imagine someone with the skills & dedication of the Developer of “Little Nav Map”, making an ATC system for MSFS !! ( “Big ATC” ? )
How amazing would that be !!
I dont get any of this. I typically did and used flight following for VFR flights just because it was less boring. When entering/exiting control zones etc…I have an idea it might be because of the transponder from the C414 which I flew exclusively the last days…atc wont recognize the xpdr code itself, as standard msfs aircraft. you have to ackowledge it in atc menu (i have a keybind for this and other atc options on a fip) will double check that later with other aircraft.
This is far too complex to explain in a forum,
IF you want to educate yourself about this subject, then I would suggest doing some Google searches, to find some well written, official documentation on VFR Communications with ATC.
One I easily found with a quick Google search is
Depends on how deep you want to get into this, but it might help to know how this works in:“Real Life”, before trying to figure out what MSFS 2020 ATC is doing, or not doing.
thank you and as helpful as that possibly is, Im not looking for real life communication in msfs. I just want it to work as it did before
see, this is the last message I get and no other option available. somethign is definetly off but no clue what… I even resubscibed to navigraph even tho I dont really need it as I fly mostly short vfr around. so if I want to land somewhere how do I get to contact them? now I have to just do an approach without clearance… no fun â– â– â–
just tried with the islander and works fine. so its the c414 transponder…
I figured it our after a while lol the 414 transponder does not match the msfs default transponder so I had to write a script for the transponder switches and states in spad.next to get things working.