Engine dies after startup?

[Rhine Muller]

On all my planes in MSFS just after engine startup it will start smmoking and dies. Clt E will not start it back.Real World Fighter Pilot, know how to start engine.

[Kapustick]

Are you using A2A aircraft? If so, you'll need to run the 012615 update for your accusim aircraft. If you don't, your planes will start off default in seriously bad mechanical/unflyable shape. You'll have to press Shift+7 to go to the hangar and click on complete overhaul before flight. You'll then probably also want to repair your SimConnect by running the msi file in your SDK directroy.

[Rhine Muller]

I AM useing several A2A aircraft. I tried what you suggested no luck! shift+tab said engine was in great shape.

[Kapustick]

Sounds like the next step would be to:
- Uninstall your A2A Aircraft via Control Panel
NOTE: you have to also manually delete the A2A folders from both your Documents folder and your FSX folder. If you don't, your reinstall will keep the "broken state of aircraft" due to the "persistant state" data that A2A aircraft use.
- Then re-install each aircraft:
1) Aircraft
2) AccuSim for the aircraft
3) repeat for each A2A aircraft
4) Finally, run the core update - the 01_26_15 update - to auto update each A2A aircraft
5) I suggest to repair your SimConnect to make sure your controls are set (unless you're using FSUIPC - I don't have that, so I don't know if that could be an issue.
6) Reboot

- Verify your control settings in FSX to make sure each listed control is mapped to only one item. i.e. FSX will set your throttle control to your stick, throttle, rudder, and whatever else you have hooked up at the same time. Or, unintended mixure or magnito setting changes during starup. Or, rudders simulateously causing aileron input. Or even, rudders simulateously causing aileron input.

- If the reinstall doesn't work, it's time to dig deeper in their support forums or contact A2A. Thier stuff works, even in the Beta version of FSX. They can fix you up for sure.

I hope you get you setup running. I remember how distraught I was during the two days that I couldn't use my CIV P51, due to similar issues that you're having.

In the end, after reading their support forum, I chaulked it up as part of their hard core simulation immersion factor. I told myself, "Wow, they simulated that I couldn't afford to buy a P-51D in "great shape". I had to buy one that needed to be fully restored. After a lot of hard reading and a few clicks of the mouse to simulate the restoration...BaDaBing...a fine ship indeed." Anyways...that kept me from punching a hole in my brand new monitor.

[xxxstefxxx]

lol , once i had an issue like that , ctrl e does not set the fuelSELECTOR to all . go in a cessna and set the fuel sellector to all press ctrl e ; if does not start then see for a red pull switch fuel cut off . if it starts then save the flight and check it as default flight.

[Rhine Muller]

Thanks you guys, I am 74, started flying a ww1 camel at 12 , (crop dusting) those were a piece of cake compared to flying on a computer.

[Morag]

Ok, in your first post you said 'all your planes' - is it all of them or is it just the A2A ones? If we get a grip on exactly what the problem is we can get you flying, promise.

[Kapustick]

Here's a check to identify between a software installation/configuration problem and possible bad controller setup:

1) Unplug all your controllers from your computer
2) Start FSX:SE in any aircraft and location on the ground
3) If using an addon aircraft such as A2A, make sure you do a complete overhaul prior to "Auto Start" (Ctrl+E)
4) Press Ctrl+E to see if your plane starts and runs. (I just tested using this method, and my A2A aircarft start and run without any controllers attached - although my plugs got fouled because my RPM was so low. I didn't know what the keyboard throttle controls were)

This test will help you identify if your controllers are sending inputs that you don't want. If your aircraft still doesn't start and run, then you surely have a software installation/configuration issue.

If any of your default aircraft don't start and continue to run using this test method, it's time to either Verify Game Cache in the Steam game properties and repair SimConnect, or consider uninstalling everything and starting with a "fresh" install of FSX:SE and reinstalling SimConnect.
_____________________________________________________________________

NOTE 1: A2A aircraft require (at least on my system: 172, 182, CIV P51 AccuSims) you to manually install the FSX:XPACK SimConnect.msi file that is not installed (but included) with the default FSX:SE installation or via verifying integrity of game cache. It is already included in your game installation directory, but not installed by default. It is located here:

[Your FSX:SE drive location]:\SteamLibrary\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK

Run the SimConnect.msi file located in the above directory. None of my A2A aircraft will run without it. Also, any time I install a new addon, it seems to cause SimConnect to malfunction. I have to go back and REPAIR SimConnect each time.

NOTE 2: Don't uninstall SimConnect from your Windows Control Panel. Doing this caused me to have to reinstall FSX:SE at least twice - it completely broke everything. Select the "Repair" option by right clicking on the SimConnect.msi file if it's already installed. Double-Clicking it would probably do the same thing.

NOTE 3: There are two other folders in the "Legacy Interfaces" directory: FSX-RTM and FSX-SP1. They are the SimConnects for the previous successive updates of FSX over the years. You don't need them unless you use older addons or default aircraft, I think. I had to install them to get my default 737 functional, so I could pass my FS Commercial and Airline Pilot Checkrides. For some reason, my A2A aircraft wouldn't run with FSX-RTM and FSX-SP1 SimConnects installed. I removed them and repaired my FSX-XPACK and lib SimConnects.

The default SimConnect installed by FSX:SE appears to be the one located in the "lib" directory - within the "SimConnect SDK" dircetory. All of this SimConnect MumboJumbo is probably why most people purchase FSUIPC to manage their controllers.

NOTE 4: All of the information I know is from reading the posts on this site and the archieves of people who experienced the same issues we have, but several years ago.

[Rhine Muller]

Thanks everyone: Have screwed everything up, willl need to reinstall MSFS ect. In answer "I only fly A2A planes.

[Kapustick]

When you uninstall FSX, be sure to delete all the FSX folders it doesn't delete. Also do this for A2A folders. This will ensure there are no files left over from the previous install.