QNH does not change to correct value at destination

[Robert_LH]

Hi kiek,

I`m using PSXTraffic and on my last two flights (EBBR-EIDW and KJFK-KBOS) I noticed that the QNH from the departing airport in the UI is still the same value at the destination airport which results in too high or too low landings by AI traffic.

Even if I restart PSXTraffic on approach the QNH value from the departure airport is indicated wrongly again.

Has it always been like this and I didn`t notice before or is this a bug?

Thanks for clarification.

Edited January 4, 2024 by Robert_LH

[kiek]

If you are using PSXTraffic you can check the QNH in the UI with the QNH in the RealTraffic app window. They should be similar. Check that first, please.

EDIT: did a quick check with PSXTraffic for MSFS at KBOS and KJFK and I did not see problems.

Only if you see a fixed 1013 it would be suspicious, because that's the default value PSXtraffic shows if there is no input from RT.

Edited January 4, 2024 by kiek

[Robert_LH]

Yes, the QNH value at the origin airports are absolutely correct in the UI and match with both real METAR data and RealTraffic data.

What I mean is:  I depart from my origin, letˋs say KJFK, there the QNH is correctly set for example at 1016. 
Now I fly to my destination where the actual QNH is for example 1002. But even on approach at the other city the QNH in PSXTraffic UI stays at 1016 (like it was at my departure) and does not change to the correct arrival location value. 
This results in all arriving traffic flying at a wrong altitude.

Just out of interest, at which point should the UI be changing the values? I have PSXTraffic running the whole flight. 

Edited January 5, 2024 by Robert_LH

[kiek]

But you are saying that the QNH matches with RT... Is not that the case at your destination then ?

The QNH is read from RT every 2 seconds....

 

[Robert_LH]

6 hours ago, kiek said:

But you are saying that the QNH matches with RT... Is not that the case at your destination then ?

The QNH is read from RT every 2 seconds....

 

For some reason, today everything worked and the QNH changed values as supposed to.

Must have been a temporary glitch the last two days.