FS9/737800NGI've been at flight simulator for quite some time flying payware aircraft for most of it and have encountered a problem that I just can't seem to lick with the 737-800. I go through the normal procedures for the aircraft, and either prior to taxi or prior to entering the runway, I engatge the autothrottle. After a few seconds, the engines spool down to idle and no control inputs from the throttle are accepted (Saitek yoke/throttle). If I disengage the A/T switch, I can controll it again. Every once in awhile, the aircraft works exactly as expected. Then the next flight, exact same thing. I went through today and deleted all game controllers and reconfigured them in FS9 just in case something was locking down the F1 button.Strangely, if I get the bird in the air without using TOGA/Authothrottle, I can get it to fly, kind of. It no longer follows the Flight Director cues, and climbs and descends at will. I love the PMDG offerings and fly the 744 and 1900 religiously. This one, though, has me beat. Any thoughts?Thanks in advance!Brian Ethington

Try using the F1-F4 keys when it acts up to see if you have throttle control from keyboard. Might help isolate the problem.VNAV will not work with A/T off.

Try using the F1-F4 keys when it acts up to see if you have throttle control from keyboard. Might help isolate the problem.VNAV will not work with A/T off.

Yes you are correct that VNAV does not work with A/T off. I don't have any issues engaging A/T once airborne when this situation occurs. However, the aircraft will not follow the FD.In regards to the Function keys, they do not respond when this situation occurs.

Yes you are correct that VNAV does not work with A/T off. I don't have any issues engaging A/T once airborne when this situation occurs. However, the aircraft will not follow the FD.In regards to the Function keys, they do not respond when this situation occurs.

A screen shot could help.

I broke the 737-900 out tonight. one perfect flight, followed by a not so perfect flight. Here are screens from the not-so-perfect flight before the aircraft crashed. AP enabled, AT enabled, VNAV and LNAV enabled, and the aircraft is descending, and accelerating. Notice the magenta bars are trying to properly direct the aircraft, but the MCP is ignorning them.

Hi Brian,I assume no "beginner's" problem (ie generators left off, flight plan not "executed", incorrect autopilot mode etc) but it might still be worth checking the overhead panel.Maybe going to the /pmdg/737NG/failures/ menu and resetting everything would help?Or removing the FS9.cfg file and letting FS build a new one (a WAG since probably your other aicraft work OK)?Sorry. No better idea at the time.Bruno

Hi Brian,I assume no "beginner's" problem (ie generators left off, flight plan not "executed", incorrect autopilot mode etc) but it might still be worth checking the overhead panel.Maybe going to the /pmdg/737NG/failures/ menu and resetting everything would help?Or removing the FS9.cfg file and letting FS build a new one (a WAG since probably your other aicraft work OK)?Sorry. No better idea at the time.Bruno

Hello Bruno, Thanks for the suggestions. I don't believe there are any beginner's issues here. I follow the checklist religiously (have for years). I'll try resetting failures, and considering replacing fs9.cfg (it's been customized for optimization, etc.) and post back how it goes.thanks again!Brian

The problem existed a long time before these shots were taken, CLB power? Were you climbing out from takeoff or descending from cruise? What is on the LEGS page of the CDU?

am having the same problem and its driving me crazy

The problem existed a long time before these shots were taken, CLB power? Were you climbing out from takeoff or descending from cruise? What is on the LEGS page of the CDU?

As Dan mentioned this looks like something is wrong in the FMS. You should be in climb power. Screenshots of the vnav and legs pages would be helpful. Also are you enabling auto throttle on the ground before takeoff? If not try that and see if things work better.

Just noted that the Stby IAS is about 256 on the last screen grab. They seem to be about 40kts different on the others as well. I'd check for mud-dauber wasps and make sure your probe heat is on. :)

Sorry guys, I work pretty long hours during the week and the weekends are the only times I can get to this. I took a bunch of screen shots tonight. The earlier ones were on climb out. These were taken on the runway, first flight on the simulator this week. The only page I did not grab is VNAV. Here is what I did to lead up to this moment:1. Configured the airplane as follows: First Class=Full, Steerage=127 pax. Cargo ~8000lbs2. Performed the following: a. Master battery on b. Standby battery on c. Emegency Lights on d. Ground power on c. Packs to auto d. Cabin Utility and Seat Power on3. I setup the FMS, initial position KAUS (even though that isn't "modeled" here), set the route from KAUS to KIAH, departure via CWK4/ILEXY transition, Arrival RIICE2/ILEXY transition, Activate, EXEC4. FMS performance: ZFW set to 124.7, Reserve set to 10, Cost Index set to 100, FL set to 23000 - EXEC5. Set the MCP speed to V2+20, Altitude to FL230, RWY and CRS to 353 and hit the Flight Director Switch6.Turned on all fuel switches7. Started the APU and engaged the generators for the APU, and turned the APU bleed on, closed the isolation valve. Lights on. Window Heat on, Probe Heat on, Yaw Damper on, Hydraulic Switches ELEC on (A and :(8. Push back using SHFT-P9. Stopped, engaged parking brake10. Right Engine starter engaged. Monitored N1 and engaged fuel lever at 18%. Waited for valve to return to off11. Left Engine start engaged. Same deal.12. Once valves were off I released the brakes, turned on the taxi light and started down the taxiwayAt the runway, I did the following:1. Engaged the TCAS and clicked TFC on the MCP2. Engaged the lights3. Took the runway. As I did, I flipped on the AutoThrottle and noticed immediately that it had locked in the throttles so that I couldn't move them anymoreAnd that is where it ended.In line, you'll see what I'm point out...In this first screen shot, I have captured Auto-throttle engaged, N1/TOGA engaged in the HSI and the engines at idle:Here I have pressed F4 to force the throttle to full, and notice that N1 is being forced to idle by the autothrottle:Overhead panel. I needed to change the cruise altitude to 23000 feet but don't believe that is the issue here:The remainder are from the FMC:I really love the way these birds handle and would like to know of a way to get around this issue. I see above that I'm not the only one with this issue. I'll take any hints or suggestions and see what I can come up with.NOTE: If I were to disengage the A/T and take off myself without using it, if I were to engage it, the plane would act like it did as I described earlier, not following the cues and disregarding any speed restrictions.Thanks again for the suggestions!Brian

Two thoughts, dunno how applicable:MCP Speed should be V2 for takeoff, 143. Not 163.Try Cost Index of 30.

This is very strange, what version of fsuipc are you running?

I mistakenly indicated MCP speed. I always set it to V2 (vcompany policy), and had. When I clicked off the A/T it automatically went to V2+20.I've tried a lot of different cost indices, including 17, 18, 20 and 100, but will try 30.FSUIPC is version 3.7.1.0I should probably point out that I'm running FS2004 on Windows 7. I've been running FS2k4 successfully with all add-ons like this since 10/22/2009.