Presently, I start up FSX with the MSFS default 172 and the engine running.Even though the throttle is closed, quite often when I start up FSX partial power will be applied when the plane uploads and the plane will immediately begin to taxiAt other times when FSX is started, the RPM will be at the idle state as soon as FS starts up.At other times, the engine has been at idle, but a few moments later the power will advance again to partial power by itself without me doing anything. The first obvious suspect might be the CH throttle, but I doubt that this is the problem as this is very consistant and only appears when starting up FSX. Any other time, the throttle works flawlessly throughout its range with no sign of a glitch.This is not a real problem as I am aware of it, and by virtually just touching the throttle to an advance state and back to idle (CH Yoke), power immediately reduces to idle RPM and stays there until the throttle is advanced. I am curious if anyone else has seen this happen and might know the cause, and/or solution.I have only noticed this after a new i7 upgrade and XPPro 64 bit installation a few months ago.Thanks:RTH

I too have this (or a very similar) issue.I only have a Saitek ST290 joystick but every flight I load up with, if I pan the view around using the hat switch when engine(s) idling, i get throttled up and off we go :( I'm sorry I do not have any sort of solution, and I just "put up with it" by immediately hitting F1 to bring the throttles back - I thought i'd post so that you know you are not alone :( RegardsSteve

Thanks for the reply Steve:Similar, but a bit different.I only see this immediately after FSX startup (and I have the default 172 selected as my default). If I advance my throttle (barely touching it) and be sure it is then closed, I go to idle and stay there. No other buttons or switches affect the power. After doing this everything is normal thereafter.Your problem sounds line a control assignment error to me. Have you checked all of your axis? Sometimes they are scrambled.Good luck:RTH

I too have this (or a very similar) issue.I only have a Saitek ST290 joystick but every flight I load up with, if I pan the view around using the hat switch when engine(s) idling, i get throttled up and off we go :( I'm sorry I do not have any sort of solution, and I just "put up with it" by immediately hitting F1 to bring the throttles back - I thought i'd post so that you know you are not alone :( RegardsSteve

I had the same thing happen to me, as FSX would load to the new airport, no matter what plane I had, it would start to taxi forward, To stop this, as it loaded I would have to keep the brake on the joy stick to keep it from going forward. I just did a fresh install of FSX and no longer have this happen. It seems to me It started after doing an aircraft down load, can not remember what aircraft or what site. I am thinking what ever same aircraft or site we downloaded from it changed the values in the default aircraft. Sorry I can not be more help then that.

IIRC this is a latency issue with the controller, whereby FS on first load does not pick up on the current position of that controller until the controller is moved, when it assumes the then-current position of that control element. The cures are1: Start FS with the throttle very slightly open, than as the screen comes up just jog the throttle back to idle2: At startup hit the `5` key on the numpad (NOT the one above the QWERTY), with numlock OFF. This sets everything to register values, so it centralises all trims and controls, and miinimises the throttle UNLESS the throttle is already slightly open) - use this when launching the sim with aircraft in flight.or 3: Use the functions of calibration available from the payware version of FSUIPC, which independently reads and sets controller positions OUTSIDE of the sim, so bypassing the FS protocols.But I am curious as to how you have eliminated control calibration from the equation? You dismissed it out of hand when it could EASILY be the simple cause of the problem. If the pot is causing an occasional `spike`, especially when it's `read` for the first time on startup, it will give you the result you describe. In fact your symptoms are those of `classic` mis-calibration.BTW, it's also a good calibration idea to check for `full and free movement of controls` when you start FSX. Not only is this replication of Real World procedure, it also has the side benefit of recalibrating within FS... You can see how this works by loading a cold and dark aircraft, then from the VC zoom out so that you have a clear view of yoke/stick, pedals and throttle/prop/mixture. Now move the throttle to the full extent of its travel and note how the first response in the sim is jagged and imprecise. Then repeat the exercise a second time and see how the throttle movement is now smoother and more fluid. Repeat the exercise with the yoke and you will see how the non-linear response curve of the standard FSX calibration causes a sudden change in response rate to aileron and elevator input at about half-full movement. Again, repeat the exercise a second time and the ratio change is no longer anything like as pronounced.Same thing applies to the pedals, although it's not the rate, it's the null zone that you notice most with those.Hope this helps.

Thanks for the reply Snave:All Axis have been calibrated with "the payware version of FSUIPC". However, I will recheck.Thanks again:RTH

IIRC this is a latency issue with the controller, whereby FS on first load does not pick up on the current position of that controller until the controller is moved, when it assumes the then-current position of that control element. The cures are1: Start FS with the throttle very slightly open, than as the screen comes up just jog the throttle back to idle2: At startup hit the `5` key on the numpad (NOT the one above the QWERTY), with numlock OFF. This sets everything to register values, so it centralises all trims and controls, and miinimises the throttle UNLESS the throttle is already slightly open) - use this when launching the sim with aircraft in flight.or 3: Use the functions of calibration available from the payware version of FSUIPC, which independently reads and sets controller positions OUTSIDE of the sim, so bypassing the FS protocols.But I am curious as to how you have eliminated control calibration from the equation? You dismissed it out of hand when it could EASILY be the simple cause of the problem. If the pot is causing an occasional `spike`, especially when it's `read` for the first time on startup, it will give you the result you describe. In fact your symptoms are those of `classic` mis-calibration.BTW, it's also a good calibration idea to check for `full and free movement of controls` when you start FSX. Not only is this replication of Real World procedure, it also has the side benefit of recalibrating within FS... You can see how this works by loading a cold and dark aircraft, then from the VC zoom out so that you have a clear view of yoke/stick, pedals and throttle/prop/mixture. Now move the throttle to the full extent of its travel and note how the first response in the sim is jagged and imprecise. Then repeat the exercise a second time and see how the throttle movement is now smoother and more fluid. Repeat the exercise with the yoke and you will see how the non-linear response curve of the standard FSX calibration causes a sudden change in response rate to aileron and elevator input at about half-full movement. Again, repeat the exercise a second time and the ratio change is no longer anything like as pronounced.Same thing applies to the pedals, although it's not the rate, it's the null zone that you notice most with those.Hope this helps.

Snave nailed it. I have the same problem occasionally with my CH Yoke. And his recommendation to use the FSX interface to recalibrate the yoke every time you start FSX after it loads is also a good one. As he said, a real world pilot always checks yoke and rudder control movement prior to taxiing, so why shouldn't a sim pilot?One other thing you can do, which I did, is go to all you saved flights (including your "default" saved flight) and put FSX in "Paused" status (P key). Then resave the flight. This way, when the flight loads in FSX, nothing will move anywhere. You can then go recalibrate the yoke\pedals, then un-pause the flight, and off you go. Works great, especially if you are loading FSX, the phone rings, you walk away from the computer to answer it, then come back to find FSX has finished loading while you were gone and your aircraft has taxied halfway to your destination airport on you. :( It also works great for setting up saved flights that don't start "stopped", like if you created and saved a flight at the Outer Marker on an ILS approach to practice ILS approaches. Rick

I agree that it looks like Snave nailed it.However, rather than in the FSX provisions, I choose to make my calibration and create a null zone with FSUIPC. I advanced the throttle slightly and Calibrated my closed end at this position, thus I believe creating a slight null zone between my slightly advanced and the totally closed positions of the throttle lever. I would have sworn that I had already done this after my upgrade, but maybe this old memory forgot. (Seem to be becoming more proficient at this talent every day, forgetting that is).So far the power is at idle after multiple startups of FSX (and FS9).Thanks folks:RTH

RTH,What I meant by re-calibrate within FSX every time you start FSX is what Snave was referring to. Even though you may have calibrated the yoke using fsuipc, when you start FSX the yoke may not be being recognized by FSX in the position the levers (throttle, etc) are actually at. I see this many times after starting FSX. If you open up the FSX Options\Settings\Controllers menu item immediately after FSX loads, you may see that even though your throttle is pulled back to idle, FSX thinks it is halfway open or maybe even at full throttle. A simple move of the throttle level will reset it back to where it should be, along with the other two yoke sliders. The x, y, and z axis on the yoke sometimes don't get read correctly by FSX when FSX first starts. Snave and my recommendations about "recalibrating within FSX" after starting FSX solve this. Or, just a simple "move" of the throttle slider will cause FSX to re-read the yoke settings. He does it by going to the VC view and watching the initial inputs made with the yoke and sliders (if I read his post correctly). I do it by actually opening up the Options\Settings\Controllers menu item so I can actually see the display FSX shows (the "red bars" for the three lever axis's) about what FSX "thinks" my yoke is doing, is set at, etc. I rarely go through an entire recalibration using the FSX calibration routine...I just use it to verify what FSX is "seeing" as far as my controller is concerned. Usually, just "nudging" the throttle will reset these red bars, and then I know everything is fine and I can exit the calibration menu and un-pause the flight. That's why I have all my saved flights, including the default startup flight, start in "Paused" status. It allows me to do the quick "yoke check" and let FSX reset itself as far as what it is "seeing" my yoke doing, before the airplane starts doing things I don't want it to do.Rick

Yep, I use the visual option of the VC purely for evidence of the change, it isn't necessary as PART of the calibration - just moving the controllers to their fullest extent will do the job.I believe this is an issue not of calibration or controllers per se, it is a `feature` of USB and one would hope that USB 3.0 will have a fix for this slightly problematic approach. Until then, and assuming no actual hardware problem (could still be a sticking potentiometer, although the fact that the same problem occurs with high-end controllers that utilise digital optics instead of pots suggests it is a ubiquitous issue) the solution is to do as advised.BTW, FSUIPC developer Pete Dowson also mentions the need to move the controllers to the fullest extent... so even using FSUIPC and bypassing the FSX settings you should STILL adopt this approach.