I only speak from my fligh sim experience regarding other FMSes, ie. 717, 737, 777, 747.

Be sure to uninstall the installed version be sure to delete any remaining files within the P3D root folder "mjc84q00". If you have changed the default location of where the Q400 is intende

The best way is (on the OFP) to enter the last SID WPT and the first STAR WPT and to add the relevant distances difference. Here +10Nm for the SID and 30 Nm for the STAR. However, I am not sure if you

Approaching GCXO from the North I see on the MFD a waypoint West of the airport denoted 5500. After RW30 my flight plan shows after 2.4NM FP and next (5500FT) without a distance, but from the MFD I es

LPPD VSM9R VSM H104 ETROX DCT 3420N DCT ABALO/N0362F250 DCT ORTIS ORTI1L GCXO (STAR via TFN).

OK so you should look somewhere else to find what is wrong on your side.

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

I just plan the same route with PFPX and entered it in the FMS and both results are the same: 837 Nm.

I just plan the same route with PFPX and entered it in the FMS and both results are the same: 837 Nm.

GVAC/01 PISPU1A PISPU B623 IPERA UN873 LOMAS DCT CANDE DCT GCXO/30

Hi folks,

Hi folks,

So, I reinstalled p3d and the dash but still the same issue.

Some additional information helps us to possibly address possible issues. Whilst you are using the PRO edition, it is on a 32bit or 64 bit platform and if so which one.

Some additional information helps us to possibly address possible issues. Whilst you are using the PRO edition, it is on a 32bit or 64 bit platform and if so which one.

Unfortunately there will not be an update for 32 it users of the Q400 as we stopped updating the 32bit version upon the release of Prepar3D v4.x.

I'm running the 32 bit version.

Are you running the 32bit or 64 bit version of the Q400?

I have read all the threads about Prepar3d v5 perhaps changing the ordering and hence the numbers assigned to each controller, which is why I decided to try every possible number that could have been

I have the same issue ad EDDM (sim-wings pro, version 1.1.2.0; P3D4.5) since the latest version of Q400 Pro (1.024):