Could you please share which variables in the XML-Interface (Pro Version/P3D v5.3 HF2) are controlling the rotary and the STD push button of the standby altimeter?

So... you tested and everything works fine, then it can only be the difference between your hard- and software and mine. I'm on P3Dv4.5 Windows10 (updated). So if you are on v5 and W11... that might b

PILOT: v1.023

It seems as though there may be some issues with the airport since the release of P3D v5.x

Like you, I'm running the latest version of P3D 4.5 with no third party shaders. My Q400 is the PRO Edition (v1.024) without the Visual Package.

As I wrote in one of my earlier posts, I am currently left with the internal P3D settings to disengage my autopilot (see the screenshot) ... and, hence, that is why that semi-colon is currently there

My suspicion is that having my joystick's button 1 set within P3D under "Autopilot master (On/Off)" is the thing which may be causing the interference you speak of. But, I have that setting

The surface normals (surface angle) of the Prepar3D are integrated into the Q400 FDE, allowing for the correct visuals and physics when operating on addon runways with a slope

In that screenshot, I had bloom on. However, I tried various combinations of HDR, bloom, and dynamic lighting. The issue persists, regardless of settings. This is on the latest version of P3D 4.5, so

Jax, yes, I have checked my P3D settings for duplicated assignments in P3D. I have fallen for that trap before. I even double-checked them again when I could not get this to work -- there's no dupl

I do realize the the answer does not satisfy the problem but P3D/FSX has had this underlying issue whereby with extremely low visibility the ghost image of the HGS becomes visible on the windscreen.

have a duplicate assignment for your controls. P3D will auto-assign functions to your controllers. These need to be deleted.

I was hoping that someone could help, I am running P3Dv4.5 and windows 10. I have recently updated my flight controls to the HOTA's Rhino, I have mapped the throttle unit to control the engines indepe

Sorry to raise this thread again, but has this been resolved? I am using the P3D V4.5 sim, with the latest installer which I believe is1024, I have also down loaded the latest visual pack and on my f

https://www.google.pt/maps/@45.3202698,-75.6674114,107a,35y,39.5t/data=!3m1!1e3

So, I want to use the fire button on this joystick to disengage the autopilot. If I remove the autopilot keyboard commands out of P3D and assign J2_b1 in the ini file, then the autopilot disconnects

the "Z" key within FSX/P3D as it had the capability of causing issues with the Dash 8 autopilot. Perhaps the sim is actioning the setting from within P3D, instead of actioning the ini file

We have "disabled" the "z" key for autopilot disconnection within FSX/P3D as it has the capability of causing issues with the MJC AP (this was done since v1.009). If you use the &

I have been flying this wonderful aircraft since I first purchased the PILOT Editon for FSX back in January 2015. I am now flying the PRO Edition in P3Dv4.5.

It really should not prevent the functionality as I have conducted one of the 3 flights that you provided without issue.