Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Baro/Altimeter Fix Coming?

Featured Replies

The Baro/Altimeter knob on the MCP has some issues when trying to select the proper altimeter. Also, when pushing the STD on button it goes between 2 different readings. This is in 2D panel and the STD bug seems to occur when in EFIS mode.Is there a fix being worked on? If so, sorry for not seeing it mentioned.:)Chris

- Chris

Gigabyte Z790 Aorus Elite AX | Intel Core i9 13900KF | Gigabyte GeForce RTX 4090 24 GB | 64GB DDR5 SDRAM | Corsair H100i Elite 240mm Liquid Cooling | 1TB & 2TB Samsung Gen 4 SSD  | 1000 Watt Gold PSU |  Windows 11 Pro | Thrustmaster Boeing Yoke | Thrustmaster TCA Captain X Airbus | Asus ROG 38" 4k IPS Monitor (PG38UQ)

Asus Maximus VII Hero motherboard | Intel i7 4790k CPU | MSI GTX 970 4 GB video card | Corsair DDR3 2133 32GB SDRAM | Corsair H50 water cooler | Samsung 850 EVO 250GB SSD (2) | EVGA 1000 watt PSU - Retired

Hi Chris, I don't think there is a bug (although I may be wrong). What causes the readout to switch between two reading (I assume you mean in. Hg vs. milibars) is that you click on the click spot that changes the readout between the two settings. You will also notice a little black mark on top of the knob going from one to the other. What other issues are you seeing?Thanks,BoazEKCH

Hey all,How about the issue that altitudes are reported incorrectly when in standard mode and the local altimeter setting is NOT 29.92 (1013)? To explain a bit, say you are using a local alt seting and pass transition altitude, you switch to STD. The local setting can still be seen below the word STD on the PFD and the altitude on the tape will read correctly for standard pressure, however if you are passed onto a new controller (this is using FS ATC btw) when you report your altitude it'll report it as if you are still using the local setting.The only way I've found to stop this is to make sure that the local is set to standard aswell. I should say that it doesn't affect your flight or the ATC, it's just a pain in the a$$Also the backup altimeter reads incorrectly, I'm always showing about 400ft difference.I'll make a screen shot later and post it to clarify.Cheers,David

You're european.You're used to varying TLs according to local conditions.In USA the TL is fixed at 18000.That's why your pilot use the actual pressure.BRClaudio

"Also the backup altimeter reads incorrectly, I'm always showing about 400ft difference."Instrument errors on the real aircraft often cause a discrepancy between the main instruments and the standby instruments. However, 400' may be beyond the limits of acceptability, depending on your current altitude (on the real aircraft).Does anyone have some tolerance values for the NG Standby Altimeter?Cheers.Ian.

BonjourI think the problem is when pushing the STD button the internal value in FS is not changed to 29.92.RegardsClaude Troncy

Hey all,Claude is spot on, that one sentence has explained my whole babbling :)Claudio, In FS, the ATC doesn't allow varying TL's, the whole world is Americanized (seems to reflect reality nowadays. Oopps, a little too political there :)) to use 18000ft for transitions. I could get away with using aerodrome specific TL's if there is a small enough variance between local and standard pressure. If there is too much difference then I wouldn't get to the correct assigned altitude, in FS ATC eyes at least, so I wouldn't get clearance to climb/descend to a new altitude. Instead I'd get continuous 'expidite climb/descent' instructions.As for the standby altimeter... I'd think there should be very little difference between them, after all you're expected to be able to fly and land on them. I'd be worried if there was >50ft difference.It is as if the needle (indicating hundreads of feet) 'zeros' at the wrong position. I can't recall if it only does this at altitude or if it shows this behaviour at sea level aswell. Next time I fly I'll find out.CheersDavid

Hi,I think it is not too complicated to fix.trigger_key_event(KEY_BAROMETRIC,29.92) must be added in the gauge code when the STD button is pushed.But may be it is not in the PMDG priority list, and there could be a side effect that I do not know.RegardsClaude Troncy

>Claudio, >>In FS, the ATC doesn't allow varying TL's, the whole world is>Americanized (seems to reflect reality nowadays. Oopps, a>little too political there :)) to use 18000ft for transitions.That was what i was saying...Altough i wrote it really bad :(I said "In USA etc..." to say that they made USA the whole world :(Claudio

>Bonjour>I think the problem is when pushing the STD button the>internal value in FS is not changed to 29.92. ?When i have an external pressure different then 2992, pressing STD the altitude tape clearly shifts.What are you talking about?Claudio

Hey all,It seems the discrepancy between the altimeters is only present at altitude, at ground level they even out to the same reading.Claudio, The altitude tape on the PFD does indeed shift accordingly when pressing the STD button, however the button doesn't seem to change the pressure that the FS ATC system uses to read your altitude.Here's an example. If the difference between local pressure and standard pressure was very large, let's say the equivalant to 500ft, the following would occur:- You pass TL and press the STD button... the alt tape on the PFD jumps accordingly- The aircraft will now fly correctly using standard pressure (1013) and will level out at the correct cruise altitude.- The FS ATC system will not have 'seen' you hit the STD button, in their eyes you are still using local pressure thus they see you as being at the wrong altitude.Due to the large difference in pressure (I made it 500ft here to prove a point) ATC will start yelling, saying you are 500ft above/below your assigned altitude. You are not. The aircraft is perfoming as it should.A picture to illustrate. The situation: I'm flying at FL340 EHAM-EGPF and have just been passed over from London Center to Manchester Control. I am on STD pressure with the local setting still 'holding' as seen on the PFD (it is actually active in FS ATC eyes which is the root problem). This is what happens:http://forums.avsim.net/user_files/76723.jpgDO'h :-rollNow if I went ahead and changed the local setting to 29.92 but leave the altimeter in STD mode it'll report altitudes correctly.Which brings me neatly to my next picture and problem. In this pic you can see that I have done exactly as I said above, reset local baro to 29.92 but left it in STD mode. However take a gander at the standby altimeter... FL344 ?!? Also before anyone mentions it, the hundreads on the standby are supposed to only read 000, you read your hundreads from the needle.http://forums.avsim.net/user_files/76725.jpgHope that helps explain things a bit better :)CheersDavid

Hi David,>A picture to illustrate. The situation: I'm flying at FL340 EHAM-EGPF and have just been passed over from London Center to Manchester Control. I am on STD pressure with the local setting still 'holding' as seen on the PFD (it is actually active in FS ATC eyes which is the root problem).http://www.hifisim.com/images/as2betateam.jpg

Hi Claudio,When you push STD button yes the altitude tape shifts correctly but may be the altitude it is not coded related to the internal FS token.I am nearly sure of that as I wrote a small gauge which display the internal token {KOHLSMAN_SETTING_HG} and it doesn't change when I press the STD button.Also if you look at the standby altimeter which I think use the internal FS token , when you press the STD button there is no change.Only the man who wrote the code could explain this behaviour.Best regardsClaude Troncy

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.