Teschmacher

hi since i got Pilot2ATC i have been exclusively and only flying the FF 320A beta in Xplane v11, since it's private/public release, i did a good dozen of flights learning to use P2ATC, and 'everything' worked almost 'hick ups'-free; and the application is sufficiently intuitive for self learning, the only thing i have noticed is the altimeter (the red numbers on the top row) always remains stuck to standard 29.92 despite i was setting it on the aircraft as instructed by atc, it did still remain STD in P2ATC. Neither i could adjust it from P2ATC ( double click the altimeter setting with the popup window), no matter what i have entered there it still remained as STD 29.92.. because of this, i was constantly experiencing altitude level discrepancies and conflicts with atc throughout the flight, the only work around i have found so far is to use the back up altimeter gauge that is set to STD altimeter on the 320 and adjust my altitude on the a/p according to it. so, it seems P2ATC doesn't detect the altimeter setting from the FF A320U neither it can send the alt setting to it, saying that because COM 1&2 frequencies changes as well as squawk do work just fine. i presume, the FF A320 U is not using xpl's standard datarefs for the altimeter, so XPUIPC can't read them and can't send them to P2ATC.. uhm.. any clues for a possible fix?