Did a KADS-KCRP flight with RC4 today and pressures were at 30.33, causing RC4 to bark at me about altitude busting. This is the second such flight this has happened to in the span of a month. Is there some hard coded setting somewhere in RC4 that can be adjusted to allow for such pressures? Has anyone else seen this sort of behavior?

Did a KADS-KCRP flight with RC4 today and pressures were at 30.33, causing RC4 to bark at me about altitude busting. This is the second such flight this has happened to in the span of a month. Is there some hard coded setting somewhere in RC4 that can be adjusted to allow for such pressures? Has anyone else seen this sort of behavior?

were you above FL180 or below?what was your altimeter set to?jd

Below 18000 and set to what RC told me to: 30.33. I ran a second flight from KADS-KSAT where pressures were as high as 30.28. I noticed if I set my altimeter to what RC4 asks, it gets out of wack on the altitude. If I manually set the barometer below 30.20, RC4 would indicate what the altimeter should be (30.28), but at least it quit barking at me about the altitude being off.

Read the RC43 manual section on transition levels and transition altitudes and how to set standard or local altimeter pressure as needed. Pages 105 and 106 give some detail. Page 37 describes it in terms of airspace.If RC commands to an altitude expressed as flight level then you must place a reference of 29.92 in (or 1013 mb) in your altimeter. If the commanded altitude is expressed in feet then use use local altimeter pressure. Local pressure is usually stated in the RC command for changes below flight levels. Some aircraft panels have a convenient altimeter switch that transfers it to the fixed standard pressure and back to local pressure (that has been entered in the altimeter Kohlsman pressure reference window).

Thanks.. but that really doesn't apply to what is happening here. I'm using RC4 as I have over the past 2 years and only when the pressure (which in the US is set to something other than 29.92 below 18000 feet (unless the pressure at that time is 29.92 which is RARE in my case)) is above 30.20 does RC4 freak out on the altitude. And what I mean by freak out is, say I'm given a flight level of 12000 feet as part of my descent phase with an altimeter of 30.28 by RC4. When I level off at 12000 feet, with the altimeter set to 30.28, RC4 thinks I'm not at the proper altitude and barks at me repeatedly. If I fudge the altimeter and decrease it to, say, 30.17, I'm within the 300 foot range (apparently) and RC4 stops barking. It repeats the altimeter as 30.28, but if I set it (usually by pressing b or manually setting it on the dial for my baro setting), RC4 then barks about the altitude being incorrect. This usually results in RC4 lecturing me on busting altitude and all that nonsense.It's hard to really explain unless you manage to fly in an area where the pressure is above 30.20.

Check your General option and tell us what you have set for Altitude Deviations. The default is 300ft. If yours is the same I suggest you make a log and send it to JD. He'll be able to tell from that what is going on.Incidentally, it may have just been a typo but 12000ft in the US is not a flight level. It's an altitude. There is a big difference. :(

Below 18000 and set to what RC told me to: 30.33. I ran a second flight from KADS-KSAT where pressures were as high as 30.28. I noticed if I set my altimeter to what RC4 asks, it gets out of wack on the altitude. If I manually set the barometer below 30.20, RC4 would indicate what the altimeter should be (30.28), but at least it quit barking at me about the altitude being off.

rc doesn't care what the pressure is. it could be 32.00, and it would correctly calculate your altitudeare you using a weather program? is there something in there for pressure smoothing? it sounds like something is causing your pressure in fs to vary widely, quickly. in the real world, that wouldn't happen. if you are, maybe turn off the weather program for one flight, and see if the problem persists.at this point, the only way for me to know what is happening on your machine/setup, is for you to make a log, and send it to me. be sure to click debug before loading the plan. duplicate the problem, and send me the .log file zipped. i can tell you what is happening, and what rc is seeing. then we'll know where to look for the problem.jd

If you are using AES with the latest service pack modes and you have set in FSUIPC.ini the special statements dealing with correcting for global weather, please note. Check the hi-fi sim support forum here on AVSIM.For FSUIPC you need base versions and interim updates as noted:---------------------------Get the base FSUIPC version from:http://www.schiratti.com/dowson.htmland then interim update from the modules link on this page:http://forum.simflight.com/forum/142-download-links/FSUIPC now self installs initially based on your registry entry for your FS path. Check that with this free utility:FSX/FS9 Registry Repair Tool (36KB) from http://www.flight1.com/view.asp?page=library----------------------------First try FS and RC without weather running and make a log. It can be a short hop that takes you up around FL280 for a couple of minutes. If you don't have this problem then try it with your weather add-on running again starting a log.To keep your first log from being overwritten go into the RC4 folder and rename the .log file. Then if you do a second log you can rename that if you wish to save it.If the flights are set for the same time and .pln you could zip up both in one zip package to send in. I'm thinking of settings for AES and FSUIPC.If you search this forum for AES you'll find references to the changes but I recommend you get them from the hi-fi sim forum.I'm just wondering if RC might be getting the destination pressure instead of local pressure at your present position within the 40 nm approach range with these AES and FSUIPC options enabled. The options I'm referring to correct for AES global weather mode as used in DWC in FSX so when you request destination weather you get that and not your present position weather pushed onto the destination which is what global mode does.

Did a KADS-KCRP flight with RC4 today and pressures were at 30.33, causing RC4 to bark at me about altitude busting. This is the second such flight this has happened to in the span of a month. Is there some hard coded setting somewhere in RC4 that can be adjusted to allow for such pressures? Has anyone else seen this sort of behavior?

Hi.Yes, I've seen something very similar, but in my case it was missed crossing restrictions when flying at the correct altitude or flight level... I never did find out what was causing the fault. I just gave up and worked around the problem by never using that qnh. It happened consistently between several airfields in central Africa and between a pair of airfields in Brazil. I suppose I may have avoided some more since then by not using that qnh. Take a look at this thread from last summer:http://forum.avsim.net/topic/287747-creating-a-log/I'm glad it's not just me!I'll have a go at your KADS - KCRP in the next few days with 30.33 in Hg to see what happens.Regards,D

Yes, I've seen something very similar, but in my case it was missed crossing restrictions when flying at the correct altitude or flight level... I never did find out what was causing the fault. I just gave up and worked around the problem by never using that qnh. It happened consistently between several airfields in central Africa and between a pair of airfields in Brazil. I suppose I may have avoided some more since then by not using that qnh.

Dave,Would you provide a FS flight plan for one of these problematical routes please? We tested all aspects of RV4 and I'd be amazed if there were any bugs for this problem.Thanks.

Dave,Would you provide a FS flight plan for one of these problematical routes please? We tested all aspects of RV4 and I'd be amazed if there were any bugs for this problem.Thanks.

Hi Ray,I can't believe it's a bug either. If nothing else, RC's been around long enough for such things to be noticed and ironed out.No problem providing a plan. Just... what format do you want? Should I mail the .pln to the same address as a log would go to or just describe it here. Or, after half a second's thought, maybe I can open a pln with a text editor.Oh, such difficulty caused by having to be at work!Regards,D

Hi Dave,If you can open the Flight Sim plan with Notepad and paste the contents here that would be fine. I should be able to fly it at the weekend. I'm more curious than anything.

Hi.Ray, the relevant *.pln is at the end of this post. Some more thoughts occurred as I played last night… I can set the altimeter most accurately by starting the flight with…[Gauges.0]KollsmanSetting=29.92...in the *.FLT file and comparing Shift+Z altitude with what's shown on the panel altimeter. For weather setting of 1003 hPa this gives a difference of about -302 feet. Part of the pre-flight then involves resetting the altimeter to local pressure by winding the kollsman window up or down until the altimeter matches Shift+Z. (Setting 1027 hPa or 30.33 in Hg gives a difference of +404 feet).When at cruise level I can use that same difference, in conjunction with Shift+Z, to adjust the altimeter from local to standard (?) setting by flying at Shift+Z altitude = (FL × 100) - 302 which for FL130 gives(130 × 100) - 302 = 12698 feetIf I cruise at Shift+Z = 12715 feet all is well and I hear no criticism from ATC.When I am ordered to cross 40 nm at FL120 I ought to fly at Shift+Z = (120 × 100) - 302 = 11698 feet. However, if I am a few feet higher at Shift+Z = 11715 feet, I am given a delay vector, and consequent critical remarks in the flight critique. I wonder if for some reason the 300 foot envelope is not being applied to the crossing restriction, or if the crossing is still judged according to qnh on account of FL180 having made its way somewhere into a calculation.trans alt dep = 3000trans alt arr = 6000trans level dep =FL50trans level arr =FL80I had a look at the relevant *.rc4 and think I recognise three of the first few numbers:, 0 , 0 , 0 , 300 , 1800 , 600 , 1300 ,,,, 0 , 0 , 0 , 1 , 0300, 600 and 1300 make sense (unless it's just coincidence) but what is the 1800 entry? Whatever the cause, it happens consistently on a few flights, and never (to my knowledge) anywhere else.The flight:IFR GUSI to GULB, no intermediate waypoints.FS9 internal weather only. Setting for the flight: clear all weather then customise by changing local pressure to 1003 hPa.I flew a freeware BAe Hawk to save time but the problem occurs also in the stock Mooney and C172, so I suppose in all aircraft.Below is IFR gusi-gulb.PLN[flightplan]AppVersion=9.1.40901title=GUSI to GULBdescription=GUSI, GULBtype=IFRroutetype=0cruising_altitude=13000departure_id=GUSI, N11* 23.93', W9* 10.88', +001295.99departure_position=30destination_id=GULB, N11* 19.79', W12* 17.23', +003395.99departure_name=Siguiridestination_name=Tatawaypoint.0=, GUSI, , GUSI, A, N11* 23.93', W9* 10.88', +001295.99, waypoint.1=, GULB, , GULB, A, N11* 19.79', W12* 17.23', +003395.99,El_kab0ng, I also flew KADS to KCRP, IFR direct at FL260, again with MSFS-only clear weather except for qnh = 1027 hPa = 30.33 in Hg. From FL260 I had a PD down to 13000 then ordered down to 12000 for crossing to RY35. I flew at 12010 feet and had no abuse for it. I know this is rather patronising but do you check your altitude with Shift+Z as well as the altimeter. At 12000 feet you will have set local pressure so the altimeter should match Shift+Z. If you don't habitually do it, try the flight again, but don't take a look at it until you get the bollocking, to see what FS9 or FSX thinks you are at.Any chance of having the KADS to KCRP plan, and a description of any other weather you had? I'll fly it again then.Regards,Dave

Hi.Ray, the relevant *.pln is at the end of this post. Some more thoughts occurred as I played last night… I can set the altimeter most accurately by starting the flight with…[Gauges.0]KollsmanSetting=29.92...in the *.FLT file and comparing Shift+Z altitude with what's shown on the panel altimeter. For weather setting of 1003 hPa this gives a difference of about -302 feet. Part of the pre-flight then involves resetting the altimeter to local pressure by winding the kollsman window up or down until the altimeter matches Shift+Z. (Setting 1027 hPa or 30.33 in Hg gives a difference of +404 feet).When at cruise level I can use that same difference, in conjunction with Shift+Z, to adjust the altimeter from local to standard (?) setting by flying at Shift+Z altitude = (FL × 100) - 302 which for FL130 gives(130 × 100) - 302 = 12698 feetIf I cruise at Shift+Z = 12715 feet all is well and I hear no criticism from ATC.When I am ordered to cross 40 nm at FL120 I ought to fly at Shift+Z = (120 × 100) - 302 = 11698 feet. However, if I am a few feet higher at Shift+Z = 11715 feet, I am given a delay vector, and consequent critical remarks in the flight critique. I wonder if for some reason the 300 foot envelope is not being applied to the crossing restriction, or if the crossing is still judged according to qnh on account of FL180 having made its way somewhere into a calculation.trans alt dep = 3000trans alt arr = 6000trans level dep =FL50trans level arr =FL80I had a look at the relevant *.rc4 and think I recognise three of the first few numbers:, 0 , 0 , 0 , 300 , 1800 , 600 , 1300 ,,,, 0 , 0 , 0 , 1 , 0300, 600 and 1300 make sense (unless it's just coincidence) but what is the 1800 entry? Whatever the cause, it happens consistently on a few flights, and never (to my knowledge) anywhere else.The flight:IFR GUSI to GULB, no intermediate waypoints.FS9 internal weather only. Setting for the flight: clear all weather then customise by changing local pressure to 1003 hPa.I flew a freeware BAe Hawk to save time but the problem occurs also in the stock Mooney and C172, so I suppose in all aircraft.Below is IFR gusi-gulb.PLN[flightplan]AppVersion=9.1.40901title=GUSI to GULBdescription=GUSI, GULBtype=IFRroutetype=0cruising_altitude=13000departure_id=GUSI, N11* 23.93', W9* 10.88', +001295.99departure_position=30destination_id=GULB, N11* 19.79', W12* 17.23', +003395.99departure_name=Siguiridestination_name=Tatawaypoint.0=, GUSI, , GUSI, A, N11* 23.93', W9* 10.88', +001295.99, waypoint.1=, GULB, , GULB, A, N11* 19.79', W12* 17.23', +003395.99,El_kab0ng, I also flew KADS to KCRP, IFR direct at FL260, again with MSFS-only clear weather except for qnh = 1027 hPa = 30.33 in Hg. From FL260 I had a PD down to 13000 then ordered down to 12000 for crossing to RY35. I flew at 12010 feet and had no abuse for it. I know this is rather patronising but do you check your altitude with Shift+Z as well as the altimeter. At 12000 feet you will have set local pressure so the altimeter should match Shift+Z. If you don't habitually do it, try the flight again, but don't take a look at it until you get the bollocking, to see what FS9 or FSX thinks you are at.Any chance of having the KADS to KCRP plan, and a description of any other weather you had? I'll fly it again then.Regards,Dave

it might be wise to delete any or all .rc4 files in the directory where the .pln files are.let's start fresh. with a new .plnand make a new log, something shorter, 100miles would be great. debug, before loading the .pln. and send the zip file to mejd

Thanks for the plan Dave. Providing I manage to stay healthy over the weekend I'll give it my best shot and report back. I feel like I'm going down with something and hope it's not swine flu. :unsure:I'll fly it in the default Learjet in FS9.