Hi all. Does anybody else have problems selecting engines? I usually don't have a problem selecting one engine, but then selecting all engines again becomes impossible. I click E and then 1,2 quickly, but dice. I've tried pacing it slower, or faster, but I just can't get both engines selected! I't maddening. It usually results in me ending the flight and restarting. A big pain, really.Anybody else have this problem?

HiIt is a well known problem. You could try assigning a differen set of keys to select all engines again, but your best bet is to use FSUIPC to assign a control to do that... it will be more stablePeter

...or another alternative:Selection Correction gauge by Rob Barendregtrcbse-10.ziphttp://library.avsim.net/search.php?Search...=root&Go=Search

You're not holding the E key down when hitting the other keys are you? You need to hit the E key then the other keys in succession. You don't have to hit them all speed typer fast just normal pace from one from one key to the other. Maybe because I'm more of a hunt and peck typer it works ok for me :) I have never had a problem selecting engines but you can do as others suggested and change the keys or use FSUIPC.Bud

Hi,I thought the way to do it was Ctrl, E, 1,2,3,4 or whatever the number of engines there are. That fires up the propliners I fly about in without problems. Each engine can take a few seconds to fire up and if you bring up the starter pop-up before you start the process you should see the mixture levers and other switches move into position as the engines catch.Andy.

The question isn't about "auto starting," Andy. The OP is asking about selecting which engines are coupled (or uncoupled, as the case might be).If you press E,1 for example, then any further commands will only affect engine 1. If you select E,1,2 then you've "recoupled" the two engines for control purposes.One of the most common causes for this "bad behavior" the OP describes is one or more poorly coded gauges and/or .mdl XML code that is constantly firing a command. This "constant firing" is responsible for a host of user problems, including the ubiquitious "10 degree increment" issue that some aircraft have, the inability to open/close Exit 2, and of course the OP's problem. ;)A registered FSUIPC "fixes" this by simply intercepting the normal keyboard & internal commands, and filtering out the rapidly repeating commands. :)Nevertheless, the only real "cure" is to find/fix the misbehaving gauge(s), or .mdl itself, a task that is most often beyond the abilities of the typical simmer.Doug Dawson wrote a nice diagnostic "gauge" called the "Key Event Logger" that simply captures all the commands during a selected interval and writes a log file, listing all of them.Installing Doug's tool on a panel, then letting it run for about ten seconds is long enough to find out which commands are "constantly firing," which will help to narrow down the search for the problem.

I'll get me coat. I never cease to be amazed at the range and depth of the questions and responses in these forums and in fact cannot work out why you would only want to start one engine, or what 'coupling' is in the sense used here. Probably another good reason for me to post less until I know more, but I love these forums!!Andy.

You want to be able to select and control engines either seperately or in groups. If you do not have a multi axis throttle quadrant, for example, you only have one lever to control all engines. Normal aircraft starting is one engine at a time. You hit E,1 then all of your controls (Throttle/Prop/Mixture) are only controlling engine one. After starting engine one you hit E,2 then you are only controlling that engine. Once all engines are started you hit E,1,2 and now you controll all engines simultaneously. For large jets you may want to use engine thrust during turns, so when turning right you would hit E,1,2 then you are controlling engines 1 and 2 (left wing engines on four jet aircraft) to assist in turning. Just some examples of why you want them together or seperate. Bud