PSS A320 and Altimeter Penalty

[Luis Altamuro]

Hi,
I usually fly A-320 from PSS, and no matter what I do, I always get an altimeter penalty, in spite of changing qnh to standard at transition
altitude. My co-pilot never forgets to advise it ;-)
You all know that pressing B don't set qnh in PSS. Has it something to do this this special behaviour of PSS panels?

Thanks in advance for your assistance.
Regards.

[SWAFO]

That's odd. I thought "B" worked universally.

[Dutch64]

No idea, i usually just click the button with the mouse and it seems to work because i don't get those penalties...

[Dutch64]

Just popped up in mind, did you check your panel configuration utility? There you can assign several keys. Is it set up correctly?

[Luis Altamuro]

Hi,
That is a default key config for PSS Airbuses. Letter B sets or unsets qnh from local to standard and viceversa, it does not sets qnh to the
right figures, as it does I think on the rest of panels... In fact, when you fly, lets say, default B737 panel, if you get a message from FS
telling that you have an incorrect qnh setting (thou you are below transition altitude), pressing B corrects the problem.
But the question is (maybe I have to tell PSS support), why when I set my qnh to STD (not 1013 / 29.92, I don't know which value sets
internally) I alwasys get an altimeter penalty.
I dislike to disable any penalty, so any suggestion/help will be welcome.
Thanks,

[snakeboy]

Letter B does not set the altimeter with the PSS Airbus's.

[SWAFO]

snakeboy wrote:
Letter B does not set the altimeter with the PSS Airbus's.

Yep, that was already made pretty clear.

Why not simply assign a different (non-used) key to set the altimeter to the current setting? Wouldn't that work just fine?

[Luis Altamuro]

Let's try! I am sure that it will give me a correct setting for qnh, but (I told you) my impresion is that STD setting is not correspondant with
1013/29.92, or maybe there's a gap in FS because in the USA transition level is at 18000, and here, in Spain, is 6000ft (you never
know...). Let's talk with PSS support to discover which figures are hidden behind that STD.
Maybe understanding (in a few words, of course) in which way FSPassengers decides to apply that penalty, it could help...

Thanks again.

[SWAFO]

FSP applies the penalty simply if you do not set the standard altimeter setting above the transition altitude, and the current altimeter
setting below the transition altitude. Nothing difficult to understand there.

[Luis Altamuro]

Ok, Brad. But the question is: Does FSP check qnh for 1013 (29.92) setting when my aircraft crosses 10.000 ft? If FSP simply checks that
value, then I would be forced to think that setting PSS gauge to STD does not really set qnh to 1013 (29.92). Then, the workaround will be
to set manually qnh to 1013 (29.92) crossing 10.000ft. That will lead to a blinking message in my HSI, but....
Could you confirm FSP does things the way I have told you? In that case, I could contact PSS support for a solution. If not, do you know if
there is any special variable that FS sets to know when your aircraft is above or below 10.000ft?

Thanks for your help.