> I am running P3DV4.5 and it's not showing the correct calculations, as screenshot.

I am running P3DV4.5 and it's not showing the correct calculations, as screenshot.

For manual descents, the 3 to 1 rule works greats. Plan to be at 10,000 feet AGL 30 miles from your destination. 3,000 AGL 10 miles out etc. you can even put those fixes into the VNAV page on the FMS

For manual descents, the 3 to 1 rule works greats. Plan to be at 10,000 feet AGL 30 miles from your destination. 3,000 AGL 10 miles out etc. you can even put those fixes into the VNAV page on the FMS

Hi airlinetycoon, do you use by chance a FFTF Dynamic for P3D v5?

If this installation file is the latest and it brings compatibility to P3Dv5.HF1 then I should not be having this problem. I am just taking stabs here, but is it possible this is a registration proble

Here's a screenie of![](http://majesticsoftware.com/forums/uploads/editor

I have downloaded and installed the latest version which I assume is compatible with P3Dv5.1HF1 or NOT. I still can't get the engines to start. What am I doing wrong. I have never had this problem! Is

Thanks for that, I checked my account over at Just Flight and the installer looks like it is the proper version even though it says it is for P3Dv4 (mjc8-400-Pro-1_021_x64-inst.exe). I ssume this is t

I did reinstall the aircraft a while back though. Is it possible this version is not compatible with P3Dv5?

My Just Flight Account says the product download link is for P3Dv4. Is this for P3Dv5 as well? That is the link I used to download and install the Pro version.

I have P3Dv5.1 HF1 installed. After a while of not flying the Q400 I started up a new flight and I have never had this issue, after going through my start procedures. After pushback, I attempted to st

Santa, what I really, really want for Christmas, is to have the the Q400 send haptic feedback through the direct input api of P3D, to an haptic enabled controller. (aka, force feedback). It would be r

Santa, what I really, really want for Christmas, is to have the the Q400 send haptic feedback through the direct input api of P3D, to an haptic enabled controller. (aka, force feedback). It would be r

EVRA 071520Z 14014KT CAVOK M01/M09 Q1022 R18/190095 NOSIG EVRA 071400Z 0715/0815 14015KT CAVOK TEMPO 0715/0716 15017G30KT TEMPO 0716/0722 15017G28KT

Well we are not able to reproduce the issue here in our labs be it on either v4.5 HF3 and v5.1x. It's a bit difficult to chase a ghost, and I don't like pointing fingers at third party add-ons, but a

I'm on Win10 (10.0.19041) 64bit, P3d v4.5 HF3 and Q400 Pro v 1.021 x64.

I reinstalled the plane, same result. I use the Pro-Edition, P3d v5.1 latest Update. Windows 10 latest Update, Nvidia driver latest Update.

3=P0,5,C65588,0 -{BRAKES}-