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.

Not at assigned altitude

Featured Replies

  • Moderator

Krytrn,

 

That could be very helpful. How about "Pressure problems with Radar Contact".

 

Is there a knob on the altimeter you can use to adjust pressure? You could then use it to manually change to 1013.2hPa when required and to local QNH, again, when required.

 

There must be a way to do that so you can adjust to correct pressure at the start of a flight.

Ray (Cheshire, England).

System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant.

Cheadle Hulme Weather website.

chlive.php

  • Replies 38
  • Views 4.3k
  • Created
  • Last Reply

Top Posters In This Topic

  • Author

Ray,

  I have place a new topic on the PMDG 747 forum.

 For my next flight I will set an initial low QNH and then, at TA, manually change it to 1013. I'll not press the STD button and see what happens. 

  • Moderator

Kryten,

 

I searched that forum for pressure problems and found others where the STD button didn't work. A reinstall fixed it for one person.

 

But for now, manual adjustment should satisfy the RC controller. I hope it isn't me! :-)

Ray (Cheshire, England).

System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant.

Cheadle Hulme Weather website.

chlive.php

  • Author

I tried a flight where the QNH was 989. At TA I used the altitude pressure knob on the EFIS to manually set 1013 (I didn't press STD). The assigned altitude problem was still there. 

  • Moderator

Kryten,

 

When you adjusted the pressure to 1013.2 did you see a change in the value displayed in the title bar where you are monitoring the pressure? As you adjust the pressure that value should be changing. Is it?

Ray (Cheshire, England).

System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant.

Cheadle Hulme Weather website.

chlive.php

FWIW:

 

I just brought up the FS9 PMDG B738 parked and worked the QNH both on the MCP and the standby altimeter down to 989 and above 1013 bpth with STD on and off.

 

Of note, the standby altimeter mb reading stayed fixed, no matter what. I hope that was fixed in the FSX NGX. The .in Hg varied. Using STD the standby altimeter and the PFD readout in. Hg changed whether using BARO hot spot or the standby altimeter QNH knob all in sync.

 

I restarted with the logging details enabled. In either STD or normal QNH mode offset 0330 varied with the BARO QNH setting. Setting 989mb gave me the value 15824 which is correct by your formula. So offset 0330 does not follow the STD or QNH mode setting. I am not experiencing the difficulties with the STD button as described in the FS9 B738NG so I am not sure that offset takes into account reporting theSTD/QNH mode reporting. However the aircraft performs as specified in Euro areas that use HPa mb. I've never experienced a problem with that.

 

(The offset is the same for FS9).

 

I looked at the FSX list of controls and that yields;

BAROMETRIC STD PRESSURE
66846

 

but I do not know how that translates  to the FSUIPC offset. There is an offset that allows the standby altimeter to use QNH when STD is set.

 

Summary:

 

Even though 0330 varies with QNH setting (in FS9) with STD set my PMDG B737NG flies correctly at low QNH in actual flight in the past. QNH 989 returns the correct 0330 reading.

 

Hope this helps.

 

P.S. I notice that the fsuipc logging features enables writing to the fsuipc.log so it may be worth enabling to examine the offset during flight of the conditions encountered.

  • Author

Ronzie

 

 So are you saying that when you fly the PMDG B737NG with a low pressure of 989 you do not have any problems with Radar Contact assigned altitudes or are you just referring to low QNH and STD settings. If the latter perhaps you could try flying with RC and see what happens.

  • Moderator

Ron / krypton,

 

I'm away from my FSX PC until Friday so cannot investigate further until then.

 

Kryten, can you try the same test with the default 737-800 and change pressure using the knob. Avoid the STD button please. I'm convinced this is a problem with the PMDG 747 panel and not RC.

Ray (Cheshire, England).

System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant.

Cheadle Hulme Weather website.

chlive.php

Ronzie

 

 So are you saying that when you fly the PMDG B737NG with a low pressure of 989 you do not have any problems with Radar Contact assigned altitudes or are you just referring to low QNH and STD settings. If the latter perhaps you could try flying with RC and see what happens.

 

Not in a position to try right now but never had a problem with the FS9 version.

 

There have been no other reports to my knowledge on this forum regarding the B737NGX series.

 

As Ray suggested test with a default aircraft.

  • Author

I started threads on both the PMDG 747 and RC forums as I do not know which is causing the problem, It may even be neither, just me doing something stupid (but there isn't a forum for that). Later in this forum I suggested that it might be useful to post a thread on the PMDG 747 forum with Radar Contact in the title to try to get someone using RC to try to replicate my problem.

 

 

 


That could be very helpful. How about "Pressure problems with Radar Contact"

 

I did so and now I'm getting flak on that thread for starting a second thread on the forum. It's all starting to get me down. Originally I thought that the solution would be simple but after many replies from people making suggestions, and which I appreciate for them spending their time, I seem no nearer to a solution. If the problem is inherent in the RC or 747 software I could spend years trying to find a solution without success. I have spent so much time trying to solve the problem I haven't had an enjoyable flight for weeks. I have to switch RC off every flight because it keeps going on about the altitude and will not shut up. I can fly perfectly happily at a STD QNH and will do that in future.

 

 

 


Kryten, can you try the same test with the default 737-800 and change pressure using the knob. Avoid the STD button please. I'm convinced this is a problem with the PMDG 747 panel and not RC.

 

I tried to do this but the default 747 does not seem to has an EFIS and I don't know how to fly the 737.

  • Moderator

Kryten,

 

I see on the PMDG forum it has been suggested you reinstall the 747. Try that for starters. It's disappointing that the support team haven't chipped in.

 

I can assure you RC is not the problem. You don't have to be an expert with the 737. Just use a simple flight plan, get up to cruise level with a QNH of 989 or similar and see if RC is happy after you press STD. It doesn't have to be a pretty flight. You're just testing a situation.

Ray (Cheshire, England).

System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant.

Cheadle Hulme Weather website.

chlive.php

  • Moderator

Kryten,

 

Now that I'm home I can better help with this problem. Please indulge me and load the default FSX 747-400.

 

Locate your aircraft at your preferred airport / runway and go into Weather / Advanced Weather and set pressure to 989. Obviously do not run any weather program.

 

Set up the logging in FSUIPC for offset 0330 and for it to output to the title bar.

 

Press B. You should see the value 15824 in the title bar. Dividing that by 16 gives us 989. Check the pressure shown in the altimeter bottom centre on the 2D panel. It should show 989 / 29.20.

 

With RC running take off and climb to cruise. When you pass the Transition Altitude manually adjust the altimeter to 1013 / 29.92. As you do this you will notice the altitude on the tape on the PFD increases. The FSUIPC readout in the title bar should be 16209 or 16214. The difference is 9ft which will not matter to RC.

 

Let me know how you get on. If that works on the default 747 then use that as a guide when you switch to the PMDG one.

 

LATER: I'm at FL310 in the default 747 and RC is quite happy with my altitude. No nagging. The problem has to be with the PMDG altimeter setting. I would be very surprised if it needed to be changed on more than one instrument (the captain's).

Ray (Cheshire, England).

System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant.

Cheadle Hulme Weather website.

chlive.php

Ray and Kryten,

indeed, there seems to be something wrong with the PMDG 747X.

I did a very "quick and dirty" flight (not even using RC4) with it setting QNH to 989. At TA I pressed STD, nothing happened, the FSUIPC readout was still 15821. Manually adjusting the altimeter to 1013 gave the correct 16208. Pressing STD then, it remained at that value. The standby altimeter you have to set manually anyway.

Actually I never noticed that behaviour. Maybe it has to do with the initial low pressure, and hopefully it will be fixed in PMDG's version 2.

Regards,

Andreas Gutzwiller

  • Moderator

Andreas,

 

Thank you for your feedback. It's a mystery to me given the usual excellence of PMDG products why such a simple and important action fails to work.

 

Do you have any way of reporting this to the PMDG support team?

Ray (Cheshire, England).

System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant.

Cheadle Hulme Weather website.

chlive.php

  • Moderator

I have spent so much time trying to solve the problem I haven't had an enjoyable flight for weeks. I have to switch RC off every flight because it keeps going on about the altitude and will not shut up. I can fly perfectly happily at a STD QNH and will do that in future.

 

kryten,

 

The above was the last thing you posted 4 days ago. Since then, silence. I have spent a fair amount of time trying to resolve this problem for you so I hope you haven't given up. The problem clearly lies with the STD knob on the PMDG747 as Andreas has kindly confirmed.

 

I notice you're not even subscribed to this thread so won't be notified of new posts. A response would be appreciated.

Ray (Cheshire, England).

System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant.

Cheadle Hulme Weather website.

chlive.php

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.