14 hours ago, snglecoil said:

It’s one of the annoying quirks of the MSFS weather system. As you pass between “weather model cells” there are large jumps in barometric pressure with no smoothing. Been that way since launch. Keep that “B” key mapped and handy 😉

It's the same thing with changes in wind direction/speed. Quite annoying.

Add to the list of issues that pop up out of nowhere.....at least I still get decent FPS when it happens......

Today , flying the same general area. no problems at all with Altimeter settings. 

16 hours ago, tgsweat said:

 

Yep had the same happening to me today. Even through off the cj4 on the ils and cause me to be too high on the GS.  Thought it was something I was doing wrong.  

 

A baro shift on approach is a slightly different reason than the ones which happen randomly at cruise. When approaching an airport, at some point the ambient wind, pressure and temperature will shift from whatever the MeteoBlue model has been predicting to the current r/w METAR.

500 foot shifts are back again. 

 

23 hours ago, Bobsk8 said:

I have been flying in the Pennsylvania -Ohio area today and about every 15 minutes I get a change in Altimeter settings of around 500 feet. Anyone else seeing this? 

Why are you setting the altimeter in MSFS?  The pressure stays at 29.92 when I fly.  

Try setting you altimeter to 30.30 and then have the AP level you off at say 10,000......

5 minutes ago, fppilot said:

Why are you setting the altimeter in MSFS?  The pressure stays at 29.92 when I fly.  

Try setting you altimeter to 30.30 and then have the AP level you off at say 10,000......

Because I set the altimeter flying VFR so it is set to the pressure at nearby locations, so I am at the correct altitude. ATC gets PO when you are assigned 4500 feet and you are at 5100 or 3900. 

1 minute ago, Bobsk8 said:

Because I set the altimeter flying VFR so it is set to the pressure at nearby locations, so I am at the correct altitude. ATC gets PO when you are assigned 4500 feet and you are at 5100 or 3900. 

Try setting your altimeter to 30.30 and then have the AP level you off at say 10,000......   or 4,000, or any altitude.  See what happens.

 

also had this in PA today. I think we are noticing it because there is a huge delta in whats being reported. KLOM was 30.52 and KACY was 30.11

Just now, fppilot said:

Try setting your altimeter to 30.30 and then have the AP level you off at say 10,000......   or 4,000, or any altitude.  See what happens.

 

•  

Why would 30.30 have any meaning when the pressure is not 30.30 where you are flying. Frankly I don't practice doing things in the sim, that I wouldn't do flying in real life. 

26 minutes ago, Bobsk8 said:

Why would 30.30 have any meaning when the pressure is not 30.30 where you are flying. Frankly I don't practice doing things in the sim, that I wouldn't do flying in real life. 

I should have said to set the current altimeter setting.  But then again, how do you know what it really is?  ATIS is totally screwed up.  My point is this.  If the actual pressure (REX WF) is 30.30 and you set the altimeter to that.  When you use the autopilot to climb to a target altitude you will not level off at that altitude.  if you then dial the altimeter to 29.92 the autopilot will then take you to the target altitude.  The autopilot is reacting as if the pressure in the sim is always 29.92.   It's like it assumes you are above 18,000 and should be setting based on that rule, even if you are attempting to level off at say 10,000.  It is flawed unless the most recent update fixed it.  I have not flown MSFS since then.  Previous updates did not fix it.  I have never determined which is flawed.  The barometric pressure in the sim, or the autopilot.

Edited March 21, 20215 yr by fppilot

5 minutes ago, fppilot said:

I should have said to set the current altimeter setting.  But then again, how do you know what it really is?  ATIS is totally screwed up.  My point is this.  If the actual pressure (REX WF) is 30.30 and you set the altimeter to that.  When you use the autopilot to climb to a target altitude you will not level off at that altitude.  if you then dial the altimeter to 29.92 the autopilot will then take you to the target altitude.  The autopilot is reacting as if the pressure in the sim is always 29.92.   It's like it assumes you are above 18,000 and should be setting based on that rule, even if you are attempting to level off at say 10,000.  It is flawed unless the most recent update fixed it.  I have not flown MSFS since then.  Previous updates did not fix it.  I have never determined which is flawed.  The barometric pressure in the sim, or the autopilot.

If you are at 5000 feet  Autopilot. and the AP is feeding it's pressure off the altimeter which in the aircraft I fly, it does, and the pressure changes by 500 feet, if you don't reset the altimeter the aircraft is now at 4500 feet and ATC tells you are you are too low. Then you adjust the Altimeter to the correct reading where you are flying, and the AP will limb until the Altimeter reads 5000 feet again. Some APs, you can set the Baro reading in the AP, but in the Arrow, it is slaved off the altimeter.  

7 hours ago, JRBarrett said:

A baro shift on approach is a slightly different reason than the ones which happen randomly at cruise. When approaching an airport, at some point the ambient wind, pressure and temperature will shift from whatever the MeteoBlue model has been predicting to the current r/w METAR.

I had it happened the entire flight, wasn't just on approach.  

I had it all morning in a flight with my JF Arrow. I thought it was only a bug in that flight and that plane but I see its every where. First time I ever saw this bug.

2 hours ago, joe cooper said:

I had it all morning in a flight with my JF Arrow. I thought it was only a bug in that flight and that plane but I see its every where. First time I ever saw this bug.

Yes this just started for me in the last 2 days, and I have not seen it before.