Hi,

The weirdest thing has just happened. The fuel flow in the engines in all my turbo props (from whichever third party) stops soon after they are fired up. It could be 1 min, 30 secs, or 5 mins later. Pure jets and reciprocating engines are still fine. The last time I landed I whacked it into reverse thrust using a mapped key on my Saitek Pro X52. Since then I can't get any turbo prop going. Has anyone any ideas on how to identify where this issue would actually lay ?

I've "repaired" all three .exe install files from Lockheed Martin and I'm wary of having to do a complete uninstall/ re-instrall.

Thanks

My first guess would be spiking/noise or a phantom controller assignment on the mixture axis.  Just a momentary spike down to zero will shut down a turbine/turboprop.  Check every controller listed in the P3D controls menu, and FSUIPC/AAO if you're using one of those utilities. 

Thanks for the reply w6kd. It is a Ctrl+Shift+F1 command that's doing it. I've just got to track down where its coming from.

I deleted the Ctrl+Shift+F1 mapping on all devices within P3D and it still happened.

I had been trying to complete a (lucrative) task in AH2 from EKRA and had that application running on my other networked PC during all my efforts. If I changed airports (within P3D) the issue was still there. I've now cancelled the AH2 task and my issue has disappeared (I hope, I have been premature in my hope before).

I doubt if I will ever get to the bottom of this but this is the weirdest issue I've had (so far) with FSX/P3D where it would appear that a SimmConnect(ed) application produces a spurious signal/command that shuts down the turbo

I'm not sure what leads you to conclude that there's a spurious key command.  One way to check out your theory would be to remove or reassign the key assignment in P3D from Ctrl-Shft-F1 to something else and see if it still occurs.

Again, I recommend you go thru the axis assignments on *every* listed device in the P3D controls menu.  Often a game controller or other device will have its axes automatically assigned by P3D when it's detected (or re-detected if it's plugged into a different port).  Any noise on such a "phantom" axis will make unwanted inputs to the sim.