Thanks so much for your advice. Paragraph 1 solved it. Somehow, trim was also assigned to my rudder pedals - buttons 3 and 4. Never thought to check rudder pedals. Where these buttons are are anybody’

First things first. The 125 Hz configuration is something that we did implement for the PRO version of the Q400 due to P3D's sluggish input device response.

Here is a llink to a tool that helps configuring it - http://majesticsoftware.com/forums/discussion/36/125-hz-pro-controls-config-tool-wizard

My hardware background is Windows 10, P3Dv4 and Saitek Yoke and Rudder. I think the easiest way to help me would be a picture of how my ini should look, then I could simply change my ini respectively

F2 and F3 move the power levers gradually allowing for incremental adjustments which would be best for initial takeoff power. The Q400 is not like an Airbus where to you just push it into the takeoff

2. This is not a common one and should not even be possible, but this behavior can be exhibited when the autopilot is active on the ground but use of the P3D's default "Z" key. In most cas

Why would it be that in P3D 4.5 with the latest hotfixes the pitch trim is stuck all the way UP and there is nothing I can do to move it down? Sometimes it is there on sim startup. Sometimes it’s in t

https://edition.cnn.com/2020/03/04/business/flybe-collapse-2020/index.html

The reason the 64bit may not be installing is because you are attempting to use the credentials for your 32 bit installation. Search you emails or the vendor from which you purchased the 64 bit versi

I am with the PRO Q400 P3Dv4.5 latest patch and AIRAC up to date. No weather.

I diid now the same flight as FraPre with the 64-bit Q400 P3D 4.5 latest HF and with the actual AIRAC. And the same result: VNAV worked perfectly down all the waypoints (although with CFS at 10.000ft

One idea for the different behavior of VNAV between the approaches of John and FraPre. Are you both on the same version of the Dash? As far as I remember from another discussion about AIRAC database f

either as you are going to have a VS of about 3000 Ft/mn. At 180 Kt (GS) with a 3° angle your VS should be around 900/1 000 Ft/mn.

https://www.airservicesaustralia.com/aip/current/dap/CFSVO03-158_07NOV2019.pdf

Hi

Thanks for the input. Speaker config seems to be fine and I'm not using Prepar3D, I'm on FSX:SE.

There however could be a user induced issue if you are using a tweak implemented via the Prepar3D.cfg: Set HideInfoText=0 in the Prepar3D.CFG file. Currently this setting can not be used with our Q400

What caught me out once was the one-button-offset. So for instance button no. 3 in your windows control panel becomes button no. 2 in the ini file. See here: http://majesticsoftware.com/forums/discuss

I'm running P3Dv4.5 hf2, and 1.020b of the Q400 Pro

If I take KERAX as a reference point, the TOD is calculated in 93 NM shortly after TAMEB, if I take DF411, if it is 126 NM before SOLVU, if I take DF422, if it is 155 NM behind GED, also if I take IF