On 4/19/2021 at 6:02 PM, Av8ing1 said:

No idea what's going on but thought I'd mention this just in case. At one point awhile back and not in the Baron, my aircraft autopilot would hold above or below the altitude selected. I realized that I had not set the standby altimeter to the correct local setting, it was at standard 29.92, so I adjusted it. The autopilot then held the correct altitude as displayed on the PFD. The autopilot was using the standby/secondary altimeter setting and thus the error. Now I set both instruments, like you are supposed to and have not had a problem. No idea if this is the case on the G1000 in the Baron. I think I was flying the A320. Obviously this condition is not normal. Must have been a bug, I have not tested it of late. 

I think this is the most likely error here.  The 'B' key sets both instruments to the same value.  The one instance where I got the Baron AP to stop at an incorrect altitude was when I changed the Garmin barometer setting on the PDF, but not the standby barometer setting.

I could see this being very confusing, and why some people think there is an issue here and some think there is not.

I don't know how this works in real aircraft.  Seems like the Garmin AP would read from the PFD?

At any rate, if you're going for more realism by manually setting the values, don't forget the standby instrument.

Edited April 23, 20215 yr by marsman2020

1 hour ago, marsman2020 said:

I think this is the most likely error here.  The 'B' key sets both instruments to the same value.  The one instance where I got the Baron AP to stop at an incorrect altitude was when I changed the Garmin barometer setting on the PDF, but not the standby barometer setting.

I could see this being very confusing, and why some people think there is an issue here and some think there is not.

I don't know how this works in real aircraft.  Seems like the Garmin AP would read from the PFD?

At any rate, if you're going for more realism by manually setting the values, don't forget the standby instrument.

Are you talking about the altimeter on the CoPilot's side (just above and a little left of the yoke stem?

I rechecked by loading a default MSFS Baron G58.

Both altimeters PDF and Copilot's are synced.

Changing either changes the other.

MSFS Option?

 

 

Edited April 23, 20215 yr by vonmar
added info text

On 4/22/2021 at 6:35 PM, vonmar said:

 

Have you had the posted problem with the default MSFS Baron G58, Longitude or the Beechcraft Bonanza G36 ?
Do you normally dial the Baro or do you use the keyboard key?

All of my first series of tests have been done by dialing the ATIS Baro.

I could reproduce the bug. I did something similar to what you showed in the video, placed the Baron G58 on the runway of KSEA, set 30.42 in the weather settings (no live weather), set my altimeter to 30.42, dialled in 3000 feet for a VS climb in the AP, and it went straight to  3500 feet instead.

Then I pressed the B key to auto-adjust the altimeter, both the altitude and the altimeter pressure stayed the same as before, but the AP immediately began to descend and took the aircraft down to 3000ft. 

I also took a look at the steam gauge altimeter on the very right side of the instrument panel, close to the right yoke, and to my surprise, the atmospheric pressure I dialled in on the Garmin always showed up in the mechanical altimeter. (Edit: As I saw just now, you already mentioned as both instruments being synced). My first suspicion was that for some reason (bug) the AP might be coupled to the separate instrument, which to my knowledge shouldn't change with the inputs to the glass cockpit.

Anyway, hope this helps to add some useful information to your bug report in zendesk. For the time being I suggest to use the B key for setting the altimeter reference. 

Edited April 23, 20215 yr by pstrub

@vonmar Could you please comment on whether or not this solves your problem? Or is it alleviated at least using the suggested workaround? This way the thread remains useful in the future when someone encounters a similar problem...

Hi everyone. I have the same problem with the altimeter, flying B748 from Samara UWWW to Kigali HRYR. altimeter 29.92. FL420. the simulator's computer traffic also has the same problems with the altimeter. the dispatcher says the same thing to everyone without stopping. 
 

Spoiler

 

 

and there was also a thunderstorm, but I managed to get past))

Spoiler