January 22, 201214 yr I must be something missing... I started the 737NGX from the cold and dark state using trisagers tutorial. Everything seems to be working (see screenshots below), but when I move the throttle forwards absolutely nothing happens...? Well, I see the throttle move, but there is no thrust. How come? Am I missing something obvious...?http://fsfiles.org/f...images/5641.jpghttp://fsfiles.org/f...images/2242.jpgI did the whole procedure twice and both times I ended up with everything ready for take off but no thrust. Edited January 22, 201214 yr by Guest
January 22, 201214 yr Check if the hydraulic pumps are on, and also make sure all lights on the overhead panel are switched off. If you follow the correct procedures, this shouldn't happen. Arjen Vandervelde
January 22, 201214 yr Hyd pumps are on as you can see on the screenshot from the overhead. Only two lights are still on: RAM DOOR FULL OPEN, but afaik that's normal on the ground: they should go of by themselves during climb... I just can't find anything wrong...
January 22, 201214 yr If you setup your AXIS in FSUIPC like I did instead of FSX that is probably why. Open FSUIPC to refresh it before pushback. If you do not do this and have some AXIS assigned in FSUIPC they might not work correctly. Edited January 22, 201214 yr by UAL115 Paul Deemer
January 22, 201214 yr Check if the hydraulic pumps are on, and also make sure all lights on the overhead panel are switched off. If you follow the correct procedures, this shouldn't happen.Hydraulic pumps have nothing to do with engine response to throttles, nor have any overhead warning lights. Basically if the engines are running they should respond to the throttles, however badly you follow the checklist. That applies to the real world too.I've had this throttle response problem once. Restarting FSX fixed it. I doubt it has anything to do with what the thread starter did following the tutorial. Edited January 22, 201214 yr by kevinh
January 22, 201214 yr Got it... Found a probable cause using Google which led me to this same forum and an old post from august (which I didn't find using Avsim-search). The culprit was my default flight... After using the FSX default flight, everything is working as it should!It's odd because PMDG says it doesn't matter what your default flight is...Thanks for thinking along! :wink:BTW I simply put // in front of the default Situation in my fxs.cfg, so I can simply restore my default flight when I am flying my other plane. Edited January 22, 201214 yr by J van E
Create an account or sign in to comment