First off let me say that I have FSUIPC (paid version ). My controls are being operated by FSX.In my default Cessna 172, the engine will shut down without warning about one minute after I start. This seems to occur everywhere ( which is ORBX Global ), except My home airport which is Greater Cincinnati Airport ( which is Mega Earth Ohio ). My default Caravan doesn't have that problem, but after start before take off , I'll check the controls and sometimes they all work, but right after take off the ailerons and elevator won't work, but the throttle and rudder always work. Sometimes the ailerons and elevator won't work from the start. I'm thinking My FUISPC is conflicting with My FSX Controls. If that's the case how do I disable the commands to FUISPC ? I haven't check my PMDG 737 NX yet, but when I get the time I will. Thank's in advance.

Just checked My PMDG 737 from Jackson Hole and no controls, just like the default 172.

Also no controls at my home airport, but eventually can get them.

The Cessna 172 idle is a bit low - need to nudge the throttle forward a bit, especially if you are at a higher altitude airport - I believe this is a separate problem from the controls issue.

 

I run all controls through FSUIPC (and recently found a very cool set of Lua scripts that you can drop in and quickly configure FSUIPC to allow you to enter the frequencies for COMs, NAVs, ADF and transponder using your keyboard's number keys - just hit the numbers).  You need to be sure that you are only doing one (controls through FSUIPC) or the other (controls through FSX), not both.

 

Occasionally (I believe this has something to do with the sequence of starting up my computer, starting FSX, plugging in controls, phase of the moon and presence or absence of one of the cats when firing things up) my controls will not respond.  I simply open FSUIPC and (in each of the sections - keys, buttons and axis) and hit the 'Reload' button.

 

If you are having problems with controls it may be due to a 'dual assignment' thing - and I have found that FSX likes to randomly re-assign things (for some strange reason and not predicatably ...  I suspect the involvement of a cat here also) to run through FSX even though I had deleted these sometime in the past.  Another issue I have heard of is (when someone experiences loss of response to controllers after a period of time) that the USB port the controller is plugged into "goes to sleep" - apparently can be fixed by going into the control panel and clicking the Properties section of each of the offending USB ports and telling it never to sleep.

Thank you so much TXHills. It all makes perfectly good sense and will try it out later tonight when there is more time.

There is a huge thread here about control problems with Windows 8.

 

Dave