Mixture causing engine to fail

[johnbla 31]

Guys I am pulling my hair out. My mixture keeps going to idle, causing my engine to fail. This could happen every few seconds or every few minutes. If I put it into automixture, the engine fails but comes straight back on, not very realist. If I have automixture off, I have to restart the engines.

I have tried everything to no avail. I have carefully looked at my axis's and have no conflicts. I do not have mixture enabled in FSUIPC. It happens to every aircraft. It happens if I disengage the joystick. I have even deleted the command for mixture to idle. I have deleted my P3D.cfg file. I am running P3D ver 4.1. Any help is GREATLY appreciated.

Many thanks

John

[ErichB 3,638]

Which aircraft are you using, or does it happen with all aircraft?  An uncommanded axis movement is usually a sign of a conflict somewhere.

Which sim version are you using?

[johnbla 31]

Hi EnrichB

 It happens to every aircraft.

[vgbaron 3,510]

If you start a flight with the engines running and touch NOTHING after you hit enter to start the sim - does the engine quit or keep running? Again, touch nothing, no keyboard, mouse or yoke, etc - just let it run.

Vic

[MartinRex007 390]

Might try reinstalling the driver for your joystick?

[Bert Pieke 7,584]

Are you running FSUIPC or JoinFS or such..

They have been known to send commands that sets your mixture to zero..

[johnbla 31]

Just reinstalled my joystick driver, no luck. Thanks for the suggestion.

Bert, I am running FSUIPC. I deleted the ini and dll files, but still no luck After about a minute, the mixture levers drops to zero, the manifold gauge drops and the engine drops out. It's very frustrating and is making P3D virtually unusable. As it happens to every aircraft, I am thinking that it must have something to do with the core of the programme.

Any more assistance is GREATLY appreciated.

John

[lownslo 592]

Did you try Vic's test?  You mustn't touch anything when the flight starts... just observe.  Also, as another test you might try removing FSUIPC completely.

Good luck,

Greg

[johnbla 31]

Yeh, I started it and did not touch a thing. I removed FSUIPC with the same result. I have just rebuilt my P3D.cfg file and will report back.