2)why was the wrong altitude 9500ft calculated for the point WI103?

The FMS is NOT expected to guide you in 3D to the 50 ft (CATIII) in every case. For this, one really have to use the HGS

Since you are using FSX the CPNA should work as intended.

What version of P3D are you using?

I have tried it in P3dv5 and in v4 with the same result - at td the sim pauses and as soon as “p” is pressed it automatically pauses again - as noted in the earlier post.

In my case I have "Spoiler Axis" selected and nothing happend. The plane... more or less tries to do the curve but not a 90º turn. If I select "mouse" and use the 3D tiller the pla

Hello, always good hearing news from majestic, I just want a little clarification on what is meant by “Cockpit edition”?... Is the pertaining to the Q400 or Q300?

This issue has just appeared on my flight sim and like the other users it only appeared after a reinstall of Win10 version 2004 OS Build 19041.45, P3D and Q400 Pro (1.020b). I can concur that the &qu

This new Gauge does not require the concurrent installation of either XMLTOOLS or FSUIPC, hence "Standalone", and should therefore work in all simulator versions from FSX to P3Dv5.

I was wondering will there be windshield effects like True Glass and PBR added to Dash 8 for P3D 4.5?

This new Standalone Version (1.6SA) does not require the concurrent installation of XMLTOOLS to manage the tabular data, but instead uses polynomial expressions to model the relationships encapsulated

https://dropbox.com/sh/ly3vz0dohpj7bt9/AAD12m9lMAc3XSr69H1zVg7Ma?dl=0

* If the runway is not on approach path (offset path), one can not use the FMS 3D approach for the final approach leg. Either one should switch to the ILS, or fly the leg visually

"Did you maybe select both the VAPA1G arrival and the ROBVO transition for the RNAV runway 34 approach?

I'd like to know what's going on in this matter.

I am using Win7 - Majestic Q400 PRO - Prepar3dv4.5 - Latest patches and AIRACS.

This is with Win 7 - P3DV4.5 - MJC Q400 PRO - AIRAC 2020.09.

32 = 2 31 = 1 20 = blank 35 = 5 32 = 2 20 = blank So you are sending the datagram (21 52 ...) but Arduino converts each digit into the ASCII hex representation.

I have finally bought the Q400 Pro edition for P3d V5 while waiting on the Training / Cockpit edition ( no I am not asking when ) The aircraft looks fantastic and I am looking forward to learning t

After stopping the graphic card software AORUS Graphic engine I didn't experienced more crashes with 1.021 in P3DV5.