Since the last update ATC has become a lot less useful, and immersive.  I tend only to fly simple GA flights, with a basic A-B route. However, lately the whole thing has changed for the worse. If I did a “cold and dark”, which is my preference, previously my automatic comms would crackle into life and contact ATC with request taxi to runway X, hold short, request take off etc, and the banter would all happen as expected. Apart from dubious runway/wind choices, but that’s a whole other topic. And as I progressed through the flight there would be a handover as I left my departure ATC zone, and fresh comms entered into as I neared my destination.  Then I would get instruction to exit runway, contact ground etc upon arrival.
 

But now, I do my start up and get no radio chatter springing into life. So I have to make my own way to the runway, and announce my intentions by way of the comms menu. I’ll get a response sometimes, sometimes not. Then, even though the route is shining bright on my sat nav, it’s like my intentions are a complete mystery. No hand-off or approach dialogue. And pulling up the comms menu will give me nothing concerning my current flight, no tune to ATIS for my destination or anything. Just a nearest airport option, or request IFR flight. And, as we all know, an IFR flight will cue the ATC to try and put me into orbit, which, in the Piper Arrow, isn’t really an option. So when I come into land now, it’s like I’ve turned up with no flight plan at all, like a total maverick. Consequently, there is no dialogue upon landing anymore either. 
 

Just to clarify, the voices are working, so it’s not a hardware, or configuration issue. It just seems that my flights are no longer recognised, and picked up by ATC. And my automatic comms aren’t bothering to announce anything either. Has  anybody else experienced this? Any tips to get back to normal again?

I still use the default ATC a lot, though not all of the time.  It's never just started up on its own (I have to initiate it with a communication).  As I usually fly IFR, I access the communication module, listen to ATIS, then "file" IFR.  ATC responds and we're off to the races.

Sounds like you may have turned off the option for your copilot to handle radio communications possibly?

If I fly from airfields that are not controlled, I can file an IFR plan. However, thereafter I am on my own until after I take off. Then I can contact xxxx Centre and all runs smoothly until descent. If I have an ILS approach, ATC is usually pretty good at getting to the right altitude at the right time. But...if I am using an RNAV approach then ATC insist that I stay at height. If (while on an IFR flight plan) clearance is for a visual approach  "and expect vectors", ATC never give me a vector and no altitude changes are permitted.

When I can "legally" cancel my IFR F/P, I do so. Ignoring Flight Following, I choose my destination when it shows up on the nearest airfield list. If it is uncontrolled you are on your own, especially if there is no ATIS when you have no idea of which runway to use.

If flying VFR from take off, I rely on the nearest airfield list.

If you know the radio frequency of your destination, you could try tuning in. I often do this to use ATIS to be able to work out my approach. I then select this in the G1000 in my DA62X whilst airborne. Sometimes I use a F/P from LNM to do this but my planned approach is to guaranteed by ATC.

I've never done a flight without default ATC and never had an issue "communicating". When I load into the plane cold and dark I get the red and white box saying that I have to turn the electrics on before atc will work. As soon as the plane is fired up, it works as expected. I don't use the copilot function, though. 

You should post a short video clip so we can see what's going on on your end. 

Edited April 29, 20215 yr by Ricardo41

8 hours ago, Wnuk said:

Sounds like you may have turned off the option for your copilot to handle radio communications possibly?

No, it still works, but much less often. And even flying from the same airfields can yield both comms on and off lately.

I used the MSFS ATC a lot this week and the only issue I got was when flying over mountains, where I was ask to climb - descend - climb - etc...  

ATC tends to do ok in flat terrain, as soon as mountains come into the equation all bets are off. Then it's time to cancel IFR and bust out the charts. It is what it is. Just like everyone else, I'm waiting for someone to produce an ATC-addon that is as easy to use and looks as good as Chaseplane. 

I think I'll be waiting a very long time.

 

5 hours ago, Ricardo41 said:

ATC tends to do ok in flat terrain, as soon as mountains come into the equation all bets are off. Then it's time to cancel IFR and bust out the charts. It is what it is. Just like everyone else, I'm waiting for someone to produce an ATC-addon that is as easy to use and looks as good as Chaseplane. 

I think I'll be waiting a very long time.

 

You'll be waiting forever, I'm using pilot2atc which, while not perfect is a LOT better than the default. Gave up with that a long time ago.....

 

G

Indeed, if you are depending on the default ATC to give you proper clearance over terrain you're going to have issues (and probably a collision).

When you create your flight plan, set your cruise altitude to safely clear all obstructions (maintaining a proper Minimum Altitude for your flight route).  When you do this, ATC will, for the most part, assign a match to your flight plan cruise altitude selection and will many times give you proper ascend and descend notifications (though not always),  Keep track of your location and the altitudes needed and request changes when required for safe passage.  It's also not uncommon for ATC to not begin the descent soon enough.  Calculate this ahead of time and request it at the appropriate point if ATC has not called for a descent.

For the approach, ATC will do a decent job (sometimes) of following the published approach you've chosen in your flight plan. If it begins to assign improper altitudes/procedures, ignore them and fly the approach on the chart.  Free resources such as Simbrief, SkyVector and little NavMap will help you do proper flight planning and can even import flight plans into MSFS.  ATC will then follow those plans (for the most part).

The best thing an armchair pilot can do for him/herself is to learn how to read departure, enroute, and approach charts. Trust me, it'll open up a world of possibilities. 

An approach chart is kind of a mini-map guiding you to the runway, with lots of signs that say "there be dragons there". 

58 minutes ago, RandallR said:

It's also not uncommon for ATC to not begin the descent soon enough

...requiring you to stuka dive bomb the descent at 5000 feet pm. Again, this is where the charts come in handy. 

Speaking of ATC, have you noticed that ATIS is mute, I just have a breath but no voice just the text.

Edited April 29, 20215 yr by guibru

Stopped using the "ATC"  months ago. It's even worse than the nonsense they had in FSX.

I only ever turn it on to check the ATIS but most of the time that's wrong as well!