ATC below assigned altitude bug returned?

Hi all.
Is anybody else seeing the return of the annoying MSFS ATC bug where you are constantly told you are below your assigned altitude? I am using preset weather with the love weather turned off. Live traffic turned on and no external programs other than FS2crew a32nx and self loading cargo. Many have reported on here that the bug has been cured but I am still seeing it. Content manager has been checked and all updates are installed.

1 Like

Same here…had to turn off the atc voices before my head exploded. :slight_smile:

1 Like

I’ve had the same issue when I fly with live weather turned on using an Xbox Series S. I don’t get any updated altimeter readings when ATC says I’m above or below my assigned altitude, so I turn the live weather off and adjust the altimeter to the standard settings. I don’t hear from ATC about altitude after that. I thought that if you are flying above or below an assigned altitude, ATC would update you on the altimeter readings when contacting you, but I guess there is a bug in the software.

Hmm… I haven’t had that bug anymore recently. I make sure I’m always on the right altimeter setting all the time.

Had it too. It seems the bug happens with high pressure weather (above 30.30) when below trans alt.

I’m not at my sim now but I don’t think they do this currently…

They should add a barometer value to the message:

“You are xxxx feet above/below your assigned altitude. Descend/climb and maintain yyyy feet. Altimeter zz.zz.”

That would be very useful information and likely solve lots of issues.

1 Like

I assume the baro setting is actually ‘correct’ / the same with ATC. But the numbers are calculated wrong (in the background).

Yeah, that may very well still be the case, which my suggestion wouldn’t solve. But it would solve the issue where you don’t know the value and/or can’t get local ATIS.

High Pressure weather is when I’m getting it too. I’ve noticed if the qnh is anything over 1020. It’s terribly annoying. I thought using a preset would work around the bug but obviously not.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.