I just got the CS C-130 and I've had only sporadic success starting the engines on this aircraft...which obviously is holding back progress. I have been trying to do "cold and dark" starts by first loading the default Cessna, shutting everything off and then switching to the C-130.I have been doing everything by the checklists and I simply just can't get the engines to start when I press the ground start buttons. None of the engine gauges move. I've had a lot of random thoughts about what the problem is, but most have not panned out.The one thing that is consistent and reproduceable though is that if I use CTRL+E to start the engines and then shut them down by a CTRL+SHFT+F1 (mixture full lean), I am able to go back and start them with the ground starts.So my question is--is there anyway to find out what sequence of events CTRL+E is doing to start the engines? I presume this is a default list of actions within MSFS. If I could find this list, maybe I could find the one thing that's missing and fix it. I'd really rather not use CTRL+E to starts all the time...actually ever.

Press Ctrl-Shift + F4 prior to beginning the start up checklist. This will open the fuel valves for you.

Press Ctrl-Shift + F4 prior to beginning the start up checklist. This will open the fuel valves for you.

Well that seems to be helping, as I am more often able to start the engines. It is still a bit "quirky" and not always working. In addition, sometimes when I open the fuel valves with the keyboard shortcut, engine #2 springs to life even though I'm trying to start #3. Like I said, it's a start, but still some ways to go. Anyone else know what CTRL+E is doing behind the scenes?