Command pods with engines firing on load

[Tokamak]

I'm having the weirdest problem, and it extends across lots of mods. 

Whenever I use any command part (manned or unmanned) that has engines incorporated into it, they always immediately fire when I try to launch the craft. That is to say, when it loads on the launchpad or runway, the engines of the command part fire, regardless of how the staging is set up. LF/O, monoprop, solid fuel, it doesn't matter. The craft loads, and those engines fire. Sometimes I can work around it with action groups and quickly killing the throttle, but that doesn't help with solid fuel engines.

I know it's not just a staging thing, because is it ONLY parts that have command AND engines.

I know it's not a specific mod, because it happens with every part of that sort I've found: Tundra Exploration (and any other Dragon replicas), Contares, Taurus HCV, and a bunch I can't remember at the moment. Since it's not one specific mod, I don't even know where to start looking for a fix. Nothing useful comes up in the log, either.

And here is the REALLY weird thing: I recently got a new computer, did a fresh install of kerbal on it, re-downloaded every mod... and the problem has followed me. Obviously the one thing that did carry over was the LIST of mods I use, but none of the actual files or configs that might have gotten broken on the old system could be here, because everything is fresh.

So yeah. A big old what on this one. Has anyone run into this?

[Streetwind]

2 hours ago, Tokamak said:

I know it's not just a staging thing, because is it ONLY parts that have command AND engines.

It may be just a staging thing, in the sense that maybe the game auto-stages command pods upon load (so that they are considered active and working). In doing so, all the functions of said part get staged, and if it includes an engine module, then voila, the engine is now running - after all, the throttle starts at 50%.

Of course, this is speculation of mine, but it would neatly explain your issue.

[Tokamak]

23 minutes ago, Streetwind said:

It may be just a staging thing, in the sense that maybe the game auto-stages command pods upon load (so that they are considered active and working). In doing so, all the functions of said part get staged, and if it includes an engine module, then voila, the engine is now running - after all, the throttle starts at 50%.

Of course, this is speculation of mine, but it would neatly explain your issue.

I suppose it would, but it wouldn't explain why everyone else doesn't have the problem. Taurus HVC, Contares, and Tundra are quite popular, and I expect they wouldn't be if they were broken for everyone. 

[SpannerMonkey(smce)]

7 hours ago, Tokamak said:

I'm having the weirdest problem, and it extends across lots of mods.

So yeah. A big old what on this one. Has anyone run into this?

HI i've seen this a lot and 9 times out of 10 it's caused by an error,  try alt f2 (cmd f2) and see if anything is reported there, check the log especially find the parts that are misbehaving and check that all modules and animations are being found correctly. If you can;t make sense of it post a log (not pastebin, use dropbox or something so you can post the complete zipped log) and I'm sure someone will  be able to find your problem or likely causes.

Is every single mod you have installed compatible with 1.1.3 or whatever version you are using?  (be aware that using updated for 1.1.3 mods on old pre 1.1.3 installs is likely to cause lots of problems)