No thrust when moving thrust levers

[LukeJ 0]

I experienced this during beta testing. The cure was to delete the default situation listed in the fsx.cfg so that when FSX loads, the Free Flight screen displays the Trike at Friday Harbor (the true default). Subsequent loading of the NGX returned all systems to normal.

Do you know what line you had to change in the cfg. I had the exact same problem. My default flight is the air trike at Friday Harbor. I selected the cold and dark setup from the FMC and have had this problem. Thanks for the help, Luke Jones

[Guest BlueRidgeDx]

Luke, If your default situation is already the Trike/Friday Harbor, then that's probably not the problem. But if you still want to give it a shot, the line is in the [uSERINTERFACE] section, and it's called "SITUATION=". Just remove everything after "SITUATION=" and restart FSX. If that doesn't fix it, there's another workaround that might help you until a real fix is available: Ensure you have a non-zero amount of fuel in the center tank. Try just 100lb, and make sure you turn off the Center Tank fuel pumps on the overhead, so you don't burn the fuel. That's not a real solution, but it is something I personally encountered during the beta.

[jordanal 70]

Same exact thing on my first taxi attempt this evening with the 800w. 22% N1 and 400 something on both EGT's, while i watched both VC throttle levers move along with my hardware throttles, but no increase in N1%, none. No chocks, alrams, warnings, or anything else unusual. I could also pull the reverse levers and watch those move as well in the VC, but no reaction to the N1 gauges, just idle. It's almost as if it were some ECC logic preventing the increase. This was started from the PMDG Cold & Dark panel state saved as the default, when this particular session started. I thought it might be my FSUIPC axis assigments that I've used for years, but revereting to the default FSX axis while in the session revealed no difference. This hurt my brain for about an hour until I decided it was time to go grill some food and crack open a beer. I will try the same SWA 800w from a short-turn panel state first thing tomorrow.

[oneill875 1]

OK I got into my cessena and moved the mixture lever to full rich then loaded up the 800WL, this time it worked but I have a feeling it was a fluke. What seems to happen is the N1 value gets stuck at 20.5% and the oil temp does not rise nor the Vibration indication. I know if it is going to work because the oil temp will rise and then suddenly the N1 will jump from 20.5 to 21.3+%, only then will I be able to use the engines. Check your engine panel and see if this happens to you too. Dan.

[sergs 0]

If you had DisablePreload=1 in your FSX.cfg, change it to DisablePreload=0. This worked for me.

[gwoardnog 0]

Just wanted to let know that this was an issue for me as well. "Just remove everything after "SITUATION=" and restart FSX." That fixed it, but the funny part was the 900 version would perform fine from cold+dark before I implemented that fix. (Cessna 172, engine off, mixture 0, master off, avionics off, at KMKC parking).

[gwoardnog 0]

I can't log-in or submit a ticket to support, if needed I will gladly support a ticket to the following, to another characters: b a s e b o n e 1 @ h o t m a il . c o m. That's a spam e-mail so it might take a while, but it's mine and I still have/had this bug. I have no qualms submitting my real account to someone from pmdg making an enquiring if needed though. I have an account/s pretty much buying everything but the 1900c/d so we should be good regardless.

[DVA2332 0]

I am having this issue as well. FSX, Windows 7 64 Bit. Seems like it is most common when I try to load a cold and start panel state. I can get the engines started, but there is no air pressure once I shut off the APU and advancing the throttles does not do anything, the air pressure reads 0. Switches are in the right positions. Tried the suggestions above, no luck. I've also noticed that with one of the cold and dark configs that the Electrical hydrolic switches don't work, has the overheat light above both the switches. This loads like this by default.

[oneill875 1]

I'm not really sure how but my NGX starts up fine now, I still get a bit anxious when the N1 readings seem to hang at 20.5% but they do jump to 21.3% and all is well.I deleted my FSX config file to allow it to rebuild and my frame rates doubled, followed the optimization as per the introduction and havent looked back.I have not had a freeze again since, I am now able to enjoy this bird as it was meant to be!

[GigiUSA 0]

Hi Dan,Did u delete your FSX.cfg file and then opened FSX in order to rebuild it? Wad this the only thing you did in order to fix this problem? I am having the same issue. Thanks.

[oneill875 1]

Yeah but I changed the fuel mixture to full first and I think that fixed it, everything worked after that. I deleted the FSX.cfg to improve frame rates so I don't know if that fixed it too.I just deleted it and started FSX and it rebuilt a new one. You'll have to redo all settings within the sim after deleting the file, only takes 5 mins or so.I have created some start up panel states now so I don't use C+D. I have ground power on and IRS off as my start up. Dan.

[NGX 1]

I experienced this too on my first flight. Follow this exactly. Turn packs and recirculation pumps off. Make sure all hydraulic pumps and fuel pumps are on. Make sure the fuel cutoff valves are on. Turn the right engine starter switch to ground and leave it. Don't attempt to start the left engine until the right engine readings are settled. If they're still increasing/decreasing, wait! Once they have levelled off completely, then you can start the left engine. The mistake most make is that as soon as the starter returns to off on the right engine, they try starting the left engine. Just give this a try.

[rototom 198]

I experienced this during beta testing. The cure was to delete the default situation listed in the fsx.cfg so that when FSX loads, the Free Flight screen displays the Trike at Friday Harbor (the true default). Subsequent loading of the NGX returned all systems to normal.

I was having this same problem and this fixed it for me. Thanks!