Description of the issue:
When I tune to ATIS to get weather in 2024, the barometric pressure is given in 6 digits. The first 4 do not appear to set the altimeter correctly.
If applicable, which aircraft is experiencing this issue:
C172
FREQUENCY OF ISSUE
Every time
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
I loaded free flight at KLNA
Tuned to ATIS on 119.975
Pressure is reported with 6 digits
[END OF FIRST USER REPORT]
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:
•
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes
Provide extra information to complete the original description of the issue:
• In my example, ATC reported an altimeter setting of “Two niner eight four decimal zero one” (2984.01)
If relevant, provide additional screenshots/video:
• N/A
To display hPa to the inHg on the G1000 you have to make following:
On the PFD press PFD soft key.
Press ALT soft key.
Click the IN soft key to switch to inHg units.
The same applies if you’d like to display it in hPa units, just press HPA soft key instead of IN soft key in the previous step.
Agree. The altimeter should be read with only four digits. In the US, the decimal is after the second digit and it is often implied. The current altimeter in the sim is being read with six digits, and the decimal is being stated after the fourth digit. The last two digits are superfluous.
This is confusing to a pilot - we tend to listen carefully to the last two digits in real life, but those are now the third and fourth digit. So if we follow the last two digits as stated in the sim, we will set the wrong altimeter setting, which is dangerous.
Example - real life: “Altimeter three zero one three” = 30.13
Current sim: “Altimeter three zero one three decimal two five” = 30.13.25 (or 3013.25)
Pilot hears “decimal two five”, enters 30.25 in the Kolsman window. However, the actual altimeter setting is 30.13, so the altimeter reads 120 feet high and the aircraft is dangerously (120 feet) lower than they think.
Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.
2 tags are required - add them in the tag section next to the title above:
Feel free to delete this quote section after adding your appropriate tags.
ISSUE DESCRIPTION
Description of the issue:
Tuning to automated weather stations in Colorado, USA gives very strange altimeter readouts.
Examples:
KBJC ATIS gives altimeter of “2970 decimal 01” but the Tower reports altimeter of “29 decimal 70” as expected.
KBDU has an AWOS on 118.825, but game reports the frequency is not in use
KEIK AWOS reported an altimeter of “296754” without any “decimal” at all.
KLMO reported an altimeter of “297101”, again without any decimal.
If applicable, which aircraft is experiencing this issue:
C172 G1000
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
Fly around, tune into automated weather stations in Colorado, Denver metro area.
Listen to the funky altimeter readouts from the automated stations.
Be confused.
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using, if relevant:
Honeycomb Alpha yoke
Saitek Flight Pro Rudder Pedals
FlightSimStuff (throttle, propeller, trim controller, etc.)
[PC Only] Are you using Developer Mode or have you made any changes to it?
No.
[END OF FIRST USER REPORT]
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:
•
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes
Provide extra information to complete the original description of the issue:
• Ah, I think I did notice this yesterday and just forgot about it. I believe I was at KPGA, Page, AZ. Tuned ATIS in the TBM and heard some weird dialogue during the weather and I think this was it.
If relevant, provide additional screenshots/video:
•
Agree. The altimeter should be read with only four digits. In the US, the decimal is after the second digit and it is often implied. The current altimeter in the sim is being read with six digits, and the decimal is being stated after the fourth digit. The last two digits are superfluous.
This is confusing to a pilot - we tend to listen carefully to the last two digits in real life, but those are now the third and fourth digit. So if we follow the last two digits as stated in the sim, we will set the wrong altimeter setting, which is dangerous.
Example - real life: “Altimeter three zero one three” = 30.13
Current sim: “Altimeter three zero one three decimal two five” = 30.13.25 (or 3013.25)
Pilot hears “decimal two five”, enters 30.25 in the Kolsman window. However, the actual altimeter setting is 30.13, so the altimeter reads 120 feet high and the aircraft is dangerously (120 feet) lower than they think.
Could this be related to the fact that QNH in hPa IS given in decimal numbers where it should not be? ATC seems to be correct but yesterday in the ATIS I got 1019.78 hPa instead of QNH 1020.
For anyone who wants to contribute on this issue, Click on the button below to use this template: