February 8, 200818 yr Flying- EGLL-LSZH, at FL 350, when suddenly " Watch your altitude your assigned altitude is 350". My altituide was exactly 350 (29.92) (1013). A few moments later - " You have busted your altitude again your assigned altitude is 350". At 350 (29.92) (1013). A few moments later- " Pilot Deviation etc" Is there an explanation for this please. Cypilot.x(
February 8, 200818 yr Commercial Member only explanation, is i don't know. i would have to see a .logif you can duplicate the error, follow the steps pinned at the top of the forum, and create a .log, and send it to mejd JD Read my blog
February 8, 200818 yr Moderator If you're certain the altimeter is set correctly to 1013 then the only other possibility is the deviation values have been altered.It's a good idea to allow some leeway for altitude. I think the default is 200ft. What do you have set? 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.
February 8, 200818 yr Ray, This has never happened before I cant understand why suddenly it should occurr. The Deviation for altitude is set at 300 feet, I would have thought that was sufficient. I will monitor the situation, and if it occurrs again I will send a log to JD. Or alter the deviation altitude until it stops. Thanks.John. Cypilot.
February 8, 200818 yr Commercial Member if you don't know when it's going to happen, you'll have to do a log for every flight.you can't turn debug on, in the middle of the flight, when it is happening.though that might be a good option to have in the future :-)jd JD Read my blog
February 19, 200818 yr I have the same problem: RC keeps telling me I've busted the altitude (and ask me if I need assistance. Boy, do I need that!), while my altitude is exactly on the nail!Will try to make a log later this week
February 19, 200818 yr Moderator The rule about altitudes and altimeter pressure setting is very simple. You wouldn't be using the B key to set it would you?That is a big no-no as far as RC is concerned. You must dial the pressure setting on the altimeter.There is one other way of setting standard pressure and that is to assign a button to a command available in FSUIPC's list of commands. The Kohlsmann command can be utilised together with a parameter value to set 29.92" / 1013.2Mb. Have a read of the FSUIPC user guide.Just to reiterate the rule... if you're assigned to a flight level you MUST be on standard pressure. If you're assigned an altitude then you must be on QNH (local pressure). Stick to tjose two rules and you can go wrong! ;-) 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.
February 19, 200818 yr On a couple of my AC, the setting window of the altimeter is either too tiny or the adjustment too coarse to be of much use. I'm stuck with using the B key in those AC.Despite that, I've found that if I'm mindful of the transition altitude where I am, I don't have any problem with RC in descents. (I record the TA from the RC screen during pre-flight.) ATC often provides QNH while you're descending some considerable time before you reach the TA. I just ignore it until the co-pilot says "Altitude Check" and then press the B key. Since few if any places have a TA higher than the 18,000 that FS understands, leaving the B key (and thus the PCA altimeter setting) alone until you've descended below whatever the local TA is keeps you properly set on both sides of the TA while still allowing you to use the B key.Once I figured that out, I've never had another problem with ATC not liking my altitude.
February 19, 200818 yr I just made a flight, without using the B-key...No problems anymore with my altitude busting.Thanks for the tip!
February 19, 200818 yr Moderator <>You're welcome. :-) 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.
February 19, 200818 yr In the US jurisdiction (FAA) the TA and TL is 18,000/FL180. FS that is what the B key is hard coded at. In most other parts of the world TA/TL vary by region.On some gauges, hovering the mouse cursor over the altimeter adjustment knob will show a "hint" of the reading. I have FS hints off but this still occurs on some.
Create an account or sign in to comment