January 6, 201511 yr I am getting random shut downs on either engine. It can happen before and during taxi, on takeoff, and in flight. It will do this even when I have selected "random engine failure probability" to never, and "engine handling" to forgiving. I noticed that on one shutdown (right engine) the right condition lever had reset itself to cutoff without me touching the engine controls. After that I have been watching the throttle quadrant closely and sure enough either condition lever will often suddenly momemtarily go to shutoff and then snap back to where it was set. The affected engine will shutdown every time and it is on only one engine (could be either one). I use dual Saitek throttles and although they are sometimes twitchy, this is the only plane in my fleet that does this. Don't know where to go from here. Any suggestions? Jim
January 6, 201511 yr Just to be clear...are you using FSUIPC for your controls? If so, do you have your FSX controls turned off? Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
January 6, 201511 yr Try switching the quadrants. Which one are you using as throttle and left condition? I know someone that had this issue but with throttle. He was using the ps2 style one for throttle and left condition and the usb one for right condition and mixtures. Ive always had them opposite. When I suggested switching quadrants it fixed it for him. Ethan Edelson
January 6, 201511 yr Author Hi, I'm using FSUIPC for all of my controls, and the controls are all turned off in FSX. As far as my Saitek throttle quadrants are set up - the left one (the ps2) controls the LH and RH throttles and the LH prop. The right one (USB), controls the RH prop, and both mixtures (condition levers). In other words, they are set up just as they are viewed in the cockpits. I may go ahead and switch them to see if that helps. Just can't figure how only the V2 Duke has the problem. Never had it in the V1 Duke or any other planes. Thanks for the suggestions. Jim
January 6, 201511 yr Just can't figure how only the V2 Duke has the problem. Never had it in the V1 Duke or any other planes. One thing I would do is check to make sure you don't have anything else assigned to that same function...probably another axis. I've had that before and the result was very much like you're describing. Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
January 6, 201511 yr Author Hi Gregg, Yeah, I rechecked and found no other axis or button assignments in conflict. Just flew an hour flight and had no problems at all this time. Go figure. Jim
January 6, 201511 yr The only other thing that comes to mind is that one time, because of throttle spikes, I had to completely uninstall FSUIPC, reinstall it and reconfigure everything. And then everything was fine. Dunno what caused it or why it worked. Not sure it'll help you or not. Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
Create an account or sign in to comment