ATC not giving new altimeter

User Support Hub ATC, Traffic & NAVAIDs
,
1

I’m running into an issue in career mode where for ifr flight plans atc gives me a starting altimeter reading but once I’ve reached cruise it never gives me an updated altimeter and proceeds to fuss at me to either climb to designated altitude or descend to designated altitude. Is there something I’m doing wrong or is it just a bug with the atc

2

Assuming you have the correct keybind (there are 3 now vice 1 in 2020), pressing it even without ATC prompt should align with local altimeter where you are. It works in Free Flight.

3

How are you able to utilize the key binding?

If I do that the altimeter is set grossly incorrectly.

It seems the binding I am using “Set Altimeter” is using the tens, ones, tenths and hundredths places (rather than thousands, hundreds, tens, ones) from the barometer value the sim’s ATC now reports to us.

Is there an alternate that actually works?

4

@NixonRedgrave there’s one that sets MSL below FL180 and then if above, STD. If you can show me all three on the filter list, I can point it out. It took me a whole flight to figure it out LOL. I’m away from my sim atm otherwise I’d post it.

1 Like
5

Right.

Here they are:

  1. Set Altimeter – Set altimeter setting (Millibars * 16)
  2. Set Altimeter – Syncs altimeter setting to sea level pressure, or 29.92 if above 18000 feet
  3. Set Altimeter to MSL pressure – Set the altimeter to mean sea level pressure

Option 2 seems to do what I described in my previous post – set the altimeter to something completely crazy. 99% of the time it puts the Kollsman at the lowest possible setting, which, when on the ground, puts many hundreds of feet below sea level.

EDIT:
Did they fix this issue? It hasn’t been in any patch notes.

There is even an active bug for what I described.

However, I’m sitting in the Beaver and I’m getting a normal result from the second option. Is it because there is no ATIS for this airport and without that the reading doesn’t have hundredths and thousandths?

Chasing these ever-moving targets in the sim is maddening. Are they fixing things at their end that aren’t documented and, yet, fix things at our end? This would be the second issue I’ve seen a behavior change with today.

I’m seriously confused.

EDIT2:

They must have fixed this. I’m at an airport with ATIS and I’m still getting a correct setting when I use the key bind. ATIS is still giving an altimeter reading with tenths and thousanths.

6

So you’re all set?

1 Like
7

Apparently so.

Thanks for the push. I’d have carried on not using the binding as I thought it still bugged.

1 Like
8

What’s the first one doing?

9

I never tried it.

Since, (as we are discussing here and on your thread) option 2 worked for me yesterday, I figured it somehow was fixed, so I didn’t test the other options.

10

same. atc never says the altimeter, hence your altitude will be always wrong.

11

I have been experiencing this issue since three days ago. ATC no longer gives me any altimeter data in their communications.

Before they always gave met the altimeter data when changing contacts. I don’t think I changed any settings, so I’m not sure how to fix this.