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.

RC4 doesn't dig on high baro pressures

Featured Replies

  • Moderator

Hi Dave,I've flown this route without problem. Rather than go through your points I'll just describe how I did it and perhaps it will help.To start with I didn't know the Transition Altitude of each airport so I opened m4.csv (in the RC4\data folder) using Notepad (never Excel) and searched for each. GUSI is 3000ft and GULB is 6000ft. Looking at the initial Transition Altitudes supplied by RC4 of 40 and 70 it is clear it adds 1,000ft to those but that initial clearance is dependent on local QNH so don't take that as gospel.I should add that knowing what the TAs are isn't really essential. You just follow what Clearance gives you. So if you're cleared to Flight Level six zero you would switch to standard pressur soon after take-off whereas a clearance to five thousand feet you would stay on QNH.My Cruise Level would be FL130, not 13000ft and shortly after take-off I was cleared to FL130. I set standard pressure and remained at cruise until 93 miles from GULB when I was cleared down to FL120 in 30 miles or less. Note that we're still on Flight Levels here so standard pressure of 29.92 / 1013.2mb is kept.I tweaked the winds for a Rwy 06 landing and after contacting APP 40 miles out I was cleared down to FL80 followed later by FL70. All this time I remained on standard pressure as Flight Levels were enunciated.Shortly after I was cleared down to 5000ft and the QNH of 1027 was given in the instruction which was my signal to adjust the altimeter to local (or QNH) pressure. I landed shortly afterwards with no nags from RC.I'd recommend you always fly an aircraft that has an altimeter that allows you to set the altimeter pressure with reasonable ease. If you have a registered version of FSUIPC here's how to assign a button that will set standard pressure:-1) Open FSUIPC and select the Hot Keys tab. Press Set against "Set Standard altimeter pressure" and assign CTRL+SHIFT+B assuming that combo is available. Press OK.2) On FSUIPC go to the Buttons and Switches tab and press a button you wish to assign to this command. On the left of the display check "Select for key press" and then press Set. Press CTRL+SHIFT+B, ensure "Key press not to be held" is checked and press OK.That will ensure a single button press will give you standard pressure globally when required. Note this is the correct way of assigning standard pressure and not the B key which only works correctly in the US.You could assign two buttons to Kohlsman Dec and Kohlsman Inc which will allow you to adjust QNH very precisely. If you don't have two buttons available you could assign the commands to two key combos or failing that use the panel button supplied.The important things to bear in mind are to be aware of when you are assigned an altitude and when you are assigned a Flight Level and to be able to easily adjust the altimeter pressure quickly and accurately to keep RC happy.Give me a shout if you need clarification on any of the above.

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

Guys,Sorry for the delayed responses. Between work and travel I haven't had much time to deal with this. I altered the buffer altitude from 300 feet to 500 feet in the RC4 options and the issue seems to have corrected itself. I know this isn't the best way to fix it, but it has helped considerably. As for my set up, I discontinued using ASE/AS6 in favor of REX Overdrive which has it's own wx generator (although I've had the high baro issues off and on with either application, so it's not unique to AS or REX it seems). I'll dig around to see if there's a smoothing option for baro pressures later tonight and then reset the buffer back to 300 feet and try again.

  • Moderator

el_kab0ng,I didn't mention in my test flight that I used AS6.5 with FS9. But I feel that is irrelevant. I've flown FSX with ASE down at Pete Dowson's and we never had any altitude issues with RC4.I suggest you reset the altitude deviation in RC4 back to its default of 300ft. I think this nagging by RC of you being at incorrect altitudes is down to incorrect setting of the altimeter. Are you sure you have adjusted the altimeter correctly? I'm sorry if this appears to question your skill but we tested this to destruction and it works as intended.Why not try a flight with no separate wx program and set the pressure in Advanced Weather inside FS to something very high like 30.70". Then try your flight again knowing the pressure will remain uniform throughout the flight and see how that goes. You could try it twice, one below 18000ft and another at FL200 to test your adjustments to/from QNH are working okay.

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've been using the B key to auto-set the pressures when instructed by RC4. I've even dialed them in by hand and had the same effect. Can someone point out exactly what the variance in altitude (the default 300ft) does? I would assume it's a setting to allow for a sort of buffer before RC4 starts complaining about altitude busting, but I wanted to understand why leaving this setting at 500ft is not a good idea.

  • Moderator

el_kab0ng,Taken from P115 of the manual...In the frame „Deviations‟ you can set the allowable deviations from assigned heading, speed, and altitude. In the picture, the screen shows the default values. For instance, regarding altitude, this means that when you are assigned 16,000 feet, you will not be busted if you fly between 15,700 and 16,300 feet.The larger you make that value the less realistic the simulation becomes. You could make it 3000 and probably ignore setting the altimeter pressure completely but that would negate the whole point of using RC.JD has asked you to create a log before a short flight where you encounter this altitude problem. That will tell him exactly what is going wrong. Can you please do this otherwise you won't get an answer to your problem.Later: I'd recommend that you don't use any weather program if you try this flight. Go into Wx settings in FS and set a fixed barometric pressure. I'd suggest something well away from 29.92. Try 30.70. That way there will be a significant difference in altitude when switching to/from QNH. If you still get the problem of RC nagging you it cannot be related to any change in pressure - only what you have set the altimeter to. Only when you have flown a successful flight would I revert to an external wx program.

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

  • Commercial Member
I've been using the B key to auto-set the pressures when instructed by RC4. I've even dialed them in by hand and had the same effect. Can someone point out exactly what the variance in altitude (the default 300ft) does? I would assume it's a setting to allow for a sort of buffer before RC4 starts complaining about altitude busting, but I wanted to understand why leaving this setting at 500ft is not a good idea.
stay away from the "B" key. it doesn't work rightdo not change the altitude deviation, it will only mask/hide what the real issue is. we need to find out what the problem is on your machine. i need a log to do that. be sure to click debug before loading the plan. instructions for the creation of logs, is pinned to the top of the forumjd

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.