Altimeter Setting Incorrectly Displayed in Window of Various Altimeters

:wave: Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons?

Yes & No. Tested both.

Brief description of the issue:

Altimeter window setting doesn’t align with altitude setting as indicated by tooltip and/or when pressing “B”. Certain models of altimeter are far worse offenders than others.

Provide Screenshot(s)/video(s) of the issue encountered:

Here you can see with this model of altimeter (seen here in the DA40 TDI, but utilized by most Asobo steam gauge aircraft), the indication is off by .01 In. Hg.


This is the worst of the Asobo aircraft – ICON A5. 30.00 doesn’t even show in the window, at all.

Second party MS/Carenado aircraft are unique in that they have two 30.00 settings, each displays a different reading of the needle. Most settings have a single value, but there are some that have two. The V35B has two for 30.12, for instance.
Model 17



Model 18


V35B

3rd party aircraft are no exception.
Big Radials Goose is the worst and the one that led me to this issue. They claim that this hadn’t come up in testing.

247D is unusual in that the tooltip isn’t the same type as the other aircraft with the setting displayed.


PMDG got it right in the DC-6

Detailed steps to reproduce the issue encountered:

Set a fixed value of 30.00 In Hg in the Weather. Turn on tooltips. Load into an aircraft with a steamgauge altimeter (steamgauge backup gauges do this too). Note the discrepancy between the setting and the displayed value in the window of the altimeter.

PC specs and/or peripheral set up if relevant:

N/A

Build Version # when you first started experiencing this issue:

1.24.5.0


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

I feel like I’m the only person flying this simulator who is actually setting their altimeter via the setting in the window rather than just pressing “B” or by using the tooltip over the altimeter knob (I have tool tips off all the time other than for illustrative purposes in screenshots).

I’m finally getting into the helicopters included in the 40th Anniversary Edition and they are out of sync with what they are supposed to be reading.

Why has such a basic aspect of one of the most important instruments in the entire aircraft been completely overlooked by the developers and those responsible for marking bugs “Feedback logged” or “Bug logged”?

No? No one else is perplexed and/or bothered by this?

It’s just me and two others based on the 3 votes.

Here’s the altimeters from the G2 and 407. The G2 is basically accurate at 29.92, but as it is moved further away from 29.92 it grows exponentially more inaccurate. The 407 is just plain inaccurate.

1 Like

Yes and unless I remember real-life altimeters incorrectly the adjustment knob works back to front on the MSFS ones.
I remember turning it clockwise to reduce the height shown and anticlock to increase it in real life . But its opposite in the sim

Standard pressure, AD elevation should read 1417ft, altimeter is off by 300ft!

But what is even worse, is that the altimeter setting works in the opposite way as it is supposed to be!

Here, I increased the barometric reference by 10hPa, so the altimeter readout should increase by 300ft, but it drops by 300ft!

How can one get such a basic and fundamental function wrong?

I think this bug should be reported with msfs-2024 tag. Otherwise this will be just ignored.

Added 2024 tag to thread here, because it won’t let me in the title and flagged moderators to add it to thread.

msfs-2024

3 Likes

Thank you for the bug report.

We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.

There’s now 3 variants of the Altimeter Baro command. I had to map the correct one to my GA Panel. It works like FS’20 but I wonder if the B key is now pointing to a valid (but differently performing) one.