August 11, 20214 yr (I put this in another thread, but figured I'd post it as a new thread so it does not get lost...) Here's how I've been handling it (in the FBW A320NX)... Cruise is set to FL350 in the flight plan. ATC clears me to climb to FL220. If I get to 21820 feet and have not heard from ATC, then I know ATC thinks I'm at a lower altitude. I bump the altitude dial up 300 feet. If I still don't get further clearance, I bump it up another couple of hundred feet. Usually, ATC will give me that further clearance within 1000 feet of additional altitude. Sometimes, ATC will think I'm at a higher altitude that I am. In that case, I'll get the next clearance a bit early. No worries, just set the new altitude and continue on. If I have reached my cruise altitude and ATC tells me to expedite the climb, then I know (again) that ATC thinks I'm lower than I actually am. Again, I bump the altitude up a couple of hundred feet at a time until ATC stops nagging me. If I have reached my cruise altitude and ATC tells me that I'm X feet above my assigned altitude, then I just lower my altitude by that amount. I pretty much do the same thing when descending. Yes, it's not realistic, but it works for me until the bug is fixed. ...jim ASUS Prime Z790-E, Intel i9 13900K, 32Gb DDR5 Ram, Nvidia 3090 24Gb, Samsung 970 EVO Plus 500 GB and 1 TB, Samsung Odyssey G9 Ultrawide 49" G-SYNC Monitor.
August 11, 20214 yr I do similar.. if my flight plan is FL350 then I know that whatever clearance I am given, that as soon as I get close to it, I will be given another instruction to go higher. So as I depart, I dial in my max alt of FL350... Clearance is to FL200 what I do then is wait and see near FL200 when I get the next raise... that generally means I am about 200 ft below or above what they asked me to climb to... I keep watching and checking so I know how many feet out it is recording... on my final ascent to FL350.. I add or subtract the differrence (and 100ft) that I have been seeing and dial that in on the Alt. To date, that has worked and I havent heard the "you are x00 ft above/below" etc. Actually it works on lower levels as well.. generally anything with a flight plan above 10,000ft is going to be out sufficiently for ATC to start warblling 🙂 Graham Edited August 11, 20214 yr by Moria15 System specs... CPU AMD5950, GPU AMD6900XT, ROG crosshair VIII Hero motherboard, Corsair 64 gig LPX 3600 mem, Air cooling on GPU, Kraken x pump cooling on CPU. Samsung G7 curved 27" monitor at 2k resolution ULTRA default settings.
August 11, 20214 yr Author 1 hour ago, Moria15 said: So as I depart, I dial in my max alt of FL350... Clearance is to FL200 what I do then is wait and see near FL200 when I get the next raise... One small issue with that... If you are using live traffic and it is busy, you may not get ATC clearance to the next level until you are well past the current clearance. In that case (in my experience) ATC will tell you to descend to the current clearance before giving you clearance to the next level. YMMV ...jim ASUS Prime Z790-E, Intel i9 13900K, 32Gb DDR5 Ram, Nvidia 3090 24Gb, Samsung 970 EVO Plus 500 GB and 1 TB, Samsung Odyssey G9 Ultrawide 49" G-SYNC Monitor.
August 11, 20214 yr 28 minutes ago, JimBrown said: One small issue with that... If you are using live traffic and it is busy, you may not get ATC clearance to the next level until you are well past the current clearance. In that case (in my experience) ATC will tell you to descend to the current clearance before giving you clearance to the next level. YMMV ...jim true Jim, but even with live traffic on, I have only had this happen once in about 20 flights, but your warning is aposite and I agree with you. Perhaps this is because I fly mainly in the UK and we are still low on flights because of Covid 🙂 Graham System specs... CPU AMD5950, GPU AMD6900XT, ROG crosshair VIII Hero motherboard, Corsair 64 gig LPX 3600 mem, Air cooling on GPU, Kraken x pump cooling on CPU. Samsung G7 curved 27" monitor at 2k resolution ULTRA default settings.
August 11, 20214 yr 2 hours ago, Moria15 said: I do similar.. if my flight plan is FL350 then I know that whatever clearance I am given, that as soon as I get close to it, I will be given another instruction to go higher. So as I depart, I dial in my max alt of FL350... Clearance is to FL200 what I do then is wait and see near FL200 when I get the next raise... that generally means I am about 200 ft below or above what they asked me to climb to... I keep watching and checking so I know how many feet out it is recording... on my final ascent to FL350.. I add or subtract the differrence (and 100ft) that I have been seeing and dial that in on the Alt. To date, that has worked and I havent heard the "you are x00 ft above/below" etc. Actually it works on lower levels as well.. generally anything with a flight plan above 10,000ft is going to be out sufficiently for ATC to start warblling 🙂 Graham Assume you have set altimeter to 29.92 above 180. So is this perhaps an issue with the barometric pressure injected by live weather? Is ATC using a barometric pressure from weather instead of using 29.92? Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener. Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126 "I will never put my name on a product that does not have in it the best that is in me." - John Deere
August 11, 20214 yr 1 minute ago, fppilot said: Assume you have set altimeter to 29.92 above 180. So is this perhaps an issue with the barometric pressure injected by live weather? Is ATC using a barometric pressure from weather instead of using 29.92? I understand from the release notes that part of the "improvement" to weather in SU5 did include a change to Barometric pressure which is the reason behind this bug. Graham System specs... CPU AMD5950, GPU AMD6900XT, ROG crosshair VIII Hero motherboard, Corsair 64 gig LPX 3600 mem, Air cooling on GPU, Kraken x pump cooling on CPU. Samsung G7 curved 27" monitor at 2k resolution ULTRA default settings.
August 11, 20214 yr One of the WT devs posted what is happening, I don't remember in what thread now, but yeah the ATC is still connected to old pressure system or something, so it is seeing your altitude as wrong when it isn't. Edited August 11, 20214 yr by Tuskin38
August 11, 20214 yr This sim is an IFR flyer’s dream. LOL. Edited August 11, 20214 yr by Virtual-Chris
August 11, 20214 yr I tried the similar approach to OPs, but the difference I had was too great, and would require me to fly at too high altitude for aircraft. So now, I get clearance to desired cruise altitude. Then either, a) wait until you receive a hand-off, at which point you can acknowledge the hand-off, retune but don't contact new controller. This means you remain on IFR plan with no ATC. When it comes time to descent, contact controller and then carry on as normal. Or (b) retune to empty channel and go silent. This will obviously work, but likely find your IFR plan cancelled. Not a big issue and there's usually the option to retry IFR clearance once you tune back in later. This approach goes back to old FSX days and still works. Just goes to show the ATC implementation is taken directly from old FSX with little or no change since. I'm sure it will get updated one day as there's so much that could be done to improve it. Anyway, that's an entirely different, and lengthy topic.
August 12, 20214 yr Author 18 hours ago, AlexJBerry said: I tried the similar approach to OPs, but the difference I had was too great, and would require me to fly at too high altitude for aircraft. Another possibility is if your flight plan has you flying the plane at its max ceiling, but ATC wants you to climb further (because it thinks you have not reached the flight plan altitude, but you really have) then you could request an altitude decrease by 1000 or 2000 feet from the ATC dialogue, but continue to fly at your flight plan altitude. ...jim ASUS Prime Z790-E, Intel i9 13900K, 32Gb DDR5 Ram, Nvidia 3090 24Gb, Samsung 970 EVO Plus 500 GB and 1 TB, Samsung Odyssey G9 Ultrawide 49" G-SYNC Monitor.
Archived
This topic is now archived and is closed to further replies.