Clumsy

More of a feature request for a future update. Would it be possible for the plane to also update the default sim variables, those which are being looked at by XPUIPC and other interfaces? At the moment, Pilot2ATC, which uses XPUIPC, is not able to detect the correct altimeter setting set in the PFD. It's also not getting the right indicated altitude. It is able to detect something, but with slightly different values, so I'm guessing the plane does update those variables but maybe before it does any of the fancy temp compensation calculations? Would it be possible to get the final indicated altitude, etc, and feed those into the variables? On a smaller note, it seems the battery/avionics variables are also not being updated (i.e. P2A cannot detect if batteries/avionics are on). I'm not technically savvy enough to know which variables these are, or if they even exist, but having the plane update the default variables can help with integration with 3rd party applications and lessen the issues raised due to inconsistency. Sorry, I know a lot of assumptions here, so clarifications and corrections are more than welcome.

Sure thing. Please see attached for the FMS file. Here's the full route: KAVL/35 DCT VIEWS DCT COLZI DCT FAK237020 DCT FAK DCT BUKYY DCT JAYBO DCT SIE DCT KACY/31 I see in the fms file that this VORradialdistance format is present as well. If you start a new flight in simbrief and enter KAVL to KACY, that is the first route that it will recommend you. KAVLKACY01.fms

Ah yes, thanks! That helps. Those commands aren't compatible with the analog axes themselves (the custom curves aren't respected), but I was at least able to assign the move/rotate view commands to the d-pad and X,Y,A,B buttons, respectively.

I had this issue in one of my flights (others worked just fine) but I think a different rootcause. When I looked at the simbrief route, it seemed like there was a VORradialdistance waypoint (looked like XXX27020) in the route. I tried entering this manually in the fms and it didn't accept this format. Could this also be causing the rejected message?

When changing the checklist procedure hint to show on the "Left Screen Edge", it works for that session, but the setting does not get saved and reverts to the default "Right Screen Edge" setting the next time the sim is launched.

I turned off the "Do PM Checklist Actions" on F/O Assists. I assume that prevents him from actually manipulating switches? However, it seems he still skips through the items and doesn't wait for me to handle the switches myself before moving to the next item.

I'm trying to use my xbox controller for walking around the FBO but it seems like the default camera axes mappings don't work. Is there an alternate way to make them work on the controller?