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.

PF3 Altitude Issue

Featured Replies

Hello,

I've been using PF3 with MSFS 2020, and for the most part, it has worked very well.

However, during an IFR flight (between KSDF & KFFO), with a cruising altitude of 15,000 feet, I kept getting an ATC instruction to maintain 15,000 feet. I was already at 15,000 feet and my barometer was set correctly (pressing the B key).

I kept getting the nag from PF3 ATC until I set the barometer to STD (29.92). Once done, the nagging stopped.

NOTE: I am using the latest MSFS 2020 beta, which is working very well for me.

Of course, the transition altitude is 18,000 in the US. I also checked and set Options 1, Trans ALT & Alt Baro Calls settings correctly by making sure the TA is 18000 (and Alt Baro pressure in Millibars is UNCHECKED).

It appears there is an issue with PF3 where I have to set STD barometer below the Transition altitude to stop PF3 from nagging me to climb.

Does anyone else run into this problem when flying in the US, between say 10,000 and 18,000 feet?

PC: AMD 9850X3D, RAM 64GB, Geforce GTX 5090 (32GB), MSFS 2020, MSFS 2024, Pimax Super 50PPD, Quest 3

50 minutes ago, flyblueskies said:

Hello,

I've been using PF3 with MSFS 2020, and for the most part, it has worked very well.

However, during an IFR flight (between KSDF & KFFO), with a cruising altitude of 15,000 feet, I kept getting an ATC instruction to maintain 15,000 feet. I was already at 15,000 feet and my barometer was set correctly (pressing the B key).

I kept getting the nag from PF3 ATC until I set the barometer to STD (29.92). Once done, the nagging stopped.

NOTE: I am using the latest MSFS 2020 beta, which is working very well for me.

Of course, the transition altitude is 18,000 in the US. I also checked and set Options 1, Trans ALT & Alt Baro Calls settings correctly by making sure the TA is 18000 (and Alt Baro pressure in Millibars is UNCHECKED).

It appears there is an issue with PF3 where I have to set STD barometer below the Transition altitude to stop PF3 from nagging me to climb.

Does anyone else run into this problem when flying in the US, between say 10,000 and 18,000 feet?

I use PF3 and I am not sure if this is a PF3 issue or a MSFS barometer issue. I will be flying at 8,000 on the Altimeter with B key setting barometer, and PF3 will tell me to climb to 8000. It seems to be 500 to 1000 feet off sometimes. 

 

 

 

  • Author

I reported this to PF3 forums and one of the answers came back as:

Hi Dave,
I do not actually believe this is a bug in MSFS and therefore is never going to be fixed.

In recent days I have seen threads that providers of online ATC like VATSIM have been having discussions on trying to handle what is actually a change implemented in MSFS that actually makes the air pressure in MSFS a lot more accurate.

https://forums.flightsimulator.com/t/vatsim-altitude-disagree-with-in-game-altitude/489150/19

In summary MSFS now calculates air pressure using air pressure, temperature & humidity and not just air pressure, which explains why I have had PF3 be as much as 1500 feet out of sync with MSFS and on other occasions be completely in sync with MSFS

Edited by flyblueskies

PC: AMD 9850X3D, RAM 64GB, Geforce GTX 5090 (32GB), MSFS 2020, MSFS 2024, Pimax Super 50PPD, Quest 3

10 minutes ago, flyblueskies said:

I reported this to PF3 forums and one of the answers came back as:

Hi Dave,
I do not actually believe this is a bug in MSFS and therefore is never going to be fixed.

In recent days I have seen threads that providers of online ATC like VATSIM have been having discussions on trying to handle what is actually a change implemented in MSFS that actually makes the air pressure in MSFS a lot more accurate.

https://forums.flightsimulator.com/t/vatsim-altitude-disagree-with-in-game-altitude/489150/19

In summary MSFS now calculates air pressure using air pressure, temperature & humidity and not just air pressure, which explains why I have had PF3 be as much as 1500 feet out of sync with MSFS and on other occasions be completely in sync with MSFS

I find the same thing, sometimes PF3 is spot on with the altitude, and then a day later it is off by 500 or more feet. 

 

 

 

What is the solution?  Fly at 8,500 feet instead of 8,000?

Rhett

7800X3D 96 GB G.Skill Flare  Gigabyte 4090  Crucial P5 Plus 2TB

15 minutes ago, Mace said:

What is the solution?  Fly at 8,500 feet instead of 8,000?

Increase the value for "Altitude deviation" under Misc Options in PF3. I have set mine to 500ft and very rarely get a wrong altitude nag, you can go up to 900 if necessary.

Alternatively you can increase the "ATC Alt Nag" time to 900 under the Advanced Options in PF3, so you will not get nagged more often than every 15 minutes.

 

What I do is hit the hotkey for either higher or lower altitude, and hit the zero key. Then whatever altitude PF3 thinks you are at, it OKs you to maintain  that altitude. 

 

 

 

Archived

This topic is now archived and is closed to further replies.

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.