In the meantime, there is no reason to be putting FS2020 in the same category as P3D or even FSX for that matter and there is NO REASON for Majestic to even look at it, in my CONSIDERED opnion. So far

Upon restarting P3D, the aircraft is now loading up with the flight directors showing on the PFD, and TCS not being there.

2021-06-01 at 14.33.10.png

I am using the Dash 8 400 with P3D v5.1

3. Might I suggest that you have a look in your USER AREA and ensure that you have applied the following patch which is applicable to the PILOT Editions only.

The patch is specifically to address an issue driven by the P3D v5.0 compatibility - so that would be the reason that you do not have a link to the patch in your User account being an FSX user.

I have the Q400 32bit pro edition for FSX, patched to version 1.020b. I am experiencing this issue with the blank syspan application window when trying to run the app on a remote pc (Win10). On my fli

3. The hung closure of the simulator is very likely related to the protection issue being experienced.

I am running P3DV5.1 on Windows 10 platform with latest updates. The MJC Dash8-Q400 installed was purchased through PC Aviator, and it has been updated for P3DV5. The problem I am experiencing is re

i reinstalled once because of the Fs2Crew Ezdokv3 callout bug that i was trying to fix with no results ofc.

OK I am able to appreciate that you are not pleased with some aspect or aspects of the results you are seeing in P3D v5, do bear in mind that the Q400 is an eight year old aircraft originally designed

I know I am a bit late as I have only just started using P3D V5 and put the Dash 8 on, but I can't believe people saying these reflections are realistic. They are not.

Fellow Captains & First Officers,

RUN the CPAN with SIM off and make the change that is needed in the CPAN, click APPLY and this will make the change. I assume that you are running P3D v5. Once you oad the aircraft you should see th

Page 136.

My computer for Flihgt Sim P3dV4.5 does not run anything else.

P3D build is 4.5.13.32097

plugged in. Some BBI-64, some Bodnar BU0836X, a generic card, a throttle quadrant, CH Products rudder pedals and a Honeycomb Alpha yoke.

After restart things remained as they were, so I looked at the 3rd thing you mentioned and sure enough I found a conflict between two input devices sharing the same axis. I removed one of them and res

As I mentioned I have used the Q400 extensively and its only since I reinstalled after updating P3DV4.5 that I have the issue. Im not that familiar with the CPAN calibration as the aircraft has always