October 14, 20241 yr Hi Nico, I'm doing some plane spotting at Mexico City MMMX, RealTraffic is showing the correct METAR with a QNH 30.48, but PSXT is showing 1017 instead of 1032. That makes approaching traffic land before the runway. When QNH matches correctly, traffic lands on the correct runway spot. Thx. Jaime. Monterrey, Mexico
October 15, 20241 yr 14 hours ago, jcuellar said: I'm doing some plane spotting at Mexico City MMMX, RealTraffic is showing the correct METAR with a QNH 30.48, but PSXT is showing 1017 instead of 1032. Hi Jaime, RealTraffic does not work with PSXT ... Do you mean PSXTraffic?
October 16, 20241 yr Author Hi, This is the scenario: I run just PSXT as usual without RealTraffic. It started with the correct QNH according to the METAR; after a few minutes, around 10, PSXT changed the QNH to 1017 and there was no change on the real METAR. I supposed it was an issue from RealTraffic, so a exit PSXT and open RealTraffic in Spotter mode, METAR was correct at 30.48 in. So there was no error with RealTraffic. I exited RT and opened PSXT and started with 1017.
October 16, 20241 yr You cannot look at the Realtraffic app to compare your QNH in PSXT with. PSXT does not get his QNH from the RT app, but from the RT API ... So you cannot conclude that RT had the right QNH. Most likely it was a problem in the RT API. Did you check the Log for QNH reading problems? I've just visited MMMX (with PSXT) and the QNH matched the one published here: METAR, TAF and NOTAM decoder for all 68,188 airports (metar-taf.com) Edited October 16, 20241 yr by kiek
October 16, 20241 yr I have not seen any issues with QNH in PSXT v8.5.1; the QNH in PSXT matches the METAR at the airports I have visited. CPU: AMD Ryzen 7 9800X3D | GPU: NVIDIA GeForce RTX 4080 Super | MoBo: ASUS Prime X670-P WIFI | OS: Windows 11 Home 64bit| RAM: 64GB 6000 MHz DDR5 | HD: 2TB Samsung 990 PRO M.2 PCIe SSD, 1TB Samsung 990 PRO M.2 PCIe SSD | MSFS 2024
October 16, 20241 yr Author 10 hours ago, kiek said: You cannot look at the Realtraffic app to compare your QNH in PSXT with. PSXT does not get his QNH from the RT app, but from the RT API ... So you cannot conclude that RT had the right QNH. Most likely it was a problem in the RT API. Did you check the Log for QNH reading problems? I've just visited MMMX (with PSXT) and the QNH matched the one published here: METAR, TAF and NOTAM decoder for all 68,188 airports (metar-taf.com) I tested once more today; the first image was at 8:38 am (1438z), the second one changed QNH to 1013 at 9:12 am (1512z) in PSXT, but QNH remains the same. https://ibb.co/KFWkkGm https://ibb.co/56gvKK1 Edited October 16, 20241 yr by jcuellar Missing info.
October 16, 20241 yr 2 hours ago, jcuellar said: the second one changed QNH to 1013 PSXT shows 1013 (the STD QNH) if no QNH is coming from RT.. It looks as if there was a problem with RT weather. Does the Log file not show any messages about that?
October 17, 20241 yr Author On 10/16/2024 at 11:41 AM, kiek said: PSXT shows 1013 (the STD QNH) if no QNH is coming from RT.. It looks as if there was a problem with RT weather. Does the Log file not show any messages about that? I'll test today once more to have a new log file.
Create an account or sign in to comment