I seem to having trouble actually red-lining the 737 engines on takeoff. I notice my thrust indication both on engine 1 and 2 are around 102.XX whenever I try to go full throttle. However, when I hold the F4 button, I get to 104+ and I start to redline the engine. Its odd, but I can see a twitch in the controls when I go just a bit farther back on the throttles. Windows shows the controls are normal and operating correctly, no twitches whatsoever. Does anyone know what setting I should look for to fix this issue? Has anyone experienced this same issue or is it one of those "FSX bugs" that cannot be fixed? Of course this issue happens with the NGX. Thanks for any suggestions/help.

Why do you even want to red-line the engines for takeoff? Do you really want to harm ther livetime? However the NGX may also had/habe problems with the idle setting for some throttle quadrants on some systems. The problem was that some users weren't able to get the minimum idle thrust during flight/descent as noraml. F2 helped there. But I think you won't ever need so much trust until you aren't in an emergency.

Hi Raul,It may be your throttle sensitivity settings in FSX. I have found on my system that if the throttle is assigned to an axis and the sensitivity is less than 100% then I lose a range of actual throttle travel. I'm not talking dead-zone here.Use FSUIPC to manually set the top and bottom range(s) of your throttle(s)jake

Hi Raul,It may be your throttle sensitivity settings in FSX. I have found on my system that if the throttle is assigned to an axis and the sensitivity is less than 100% then I lose a range of actual throttle travel. I'm not talking dead-zone here.Use FSUIPC to manually set the top and bottom range(s) of your throttle(s)jake

Oh yeah I also do not use FSUIPC...I have not purchased it yet since I see no point to it right now. Or could this be what can fix that little issue? Because I can recall a time where I fixed it on the cessna. Maybe its fixed on the cessna but not on the NGX...I will confirm this later on.

Why do you even want to red-line the engines for takeoff? Do you really want to harm ther livetime? However the NGX may also had/habe problems with the idle setting for some throttle quadrants on some systems. The problem was that some users weren't able to get the minimum idle thrust during flight/descent as noraml. F2 helped there. But I think you won't ever need so much trust until you aren't in an emergency.

I do realize that the engine will have less life and get damaged if left at full for an extended period of time. However, that is beside the point. I specified only takeoff, I didn't mention cruise or any other phase in flight. I was taking off KLAX which has no significant effect over engine performance elevation wise. Hence, why I mention the F4 key being pressed and why I see a significant amount of difference when I depress it. It happens on the NGX and most noticeably on the Carenado cessna 172 or 152 which if not at full thrust you will take off very late. Or I am the only one with this problem? Idle controls are fine and I can fully reverse thrust all day long and it never fails. Full throttle is the problem, sensitivity is at high 127 and null 1. I will post a screenshot of what I mean later today.

I'm not sure you need to pay for the registered version to do this (somone please correct me if I'm wrong) Just download it and see. Read the manual!I had your problem in reverse. After SP1c (but possibly not connected) my thottles wouldn't zero, so when I fired up the engines they went straight to c. 24-26%N1 thus rolling me over the marshaller and into the terminal building while I was still staring at panels.I used FSUIPC to set the actual real range of my throttles in raw data values, which is something, in my experience, Windows joystik calibration (nor Saitek's for that matter) cannot sucessfully do.bestjake

I'm not sure you need to pay for the registered version to do this (somone please correct me if I'm wrong) Just download it and see. Read the manual!I had your problem in reverse. After SP1c (but possibly not connected) my thottles wouldn't zero, so when I fired up the engines they went straight to c. 24-26%N1 thus rolling me over the marshaller and into the terminal building while I was still staring at panels.I used FSUIPC to set the actual real range of my throttles in raw data values, which is something, in my experience, Windows joystik calibration (nor Saitek's for that matter) cannot sucessfully do.bestjake

Hey Jake,Strangely I just flew the Carenado Cessna 172 trying out Accu-Feel and was able to full throttle fine! I also own the TPM, I tried full power and full idle. Its just like on the cessna on idle, its about 200-300 RPM less than the suggested 1000RPM for idle. So I had no issues with idle whatsoever. I revved full power and was at 2300-2400RPM full throttle pressed the F4 to make sure...no change. However when I start the NGX I have a difference in throttle visually (throttle on pedestal) and with the percentage of power. I see throttle twitching and when I hold F4, it goes full range but only stays if I hold the button...is this a limitation on the NGX animation and control? I confirmed this just now with my TPM and throttle quadrants.

Hey Raul,Yes, same. I saw the throttles move forward a litle when loading NGX. Ryan makes a reference to something similar early in tutorial 2, so maybe there was some work done on the way NGX SP1c interprets throttle response.I too do not see this on othr A/C (not that I've flown any for longer than five minutes since installing NGX!)You can apply specific profiles to PSUIPC so it might be worth at least trying it.If NGX is seeing your throttles wrong, FSUIPC can fool them into a different range of travel just for that profile, and then back again when you aren't using it. Give it a go. I can't think of anything else that could cause this bar dirty/broken pots in the controller.You can open a ticket, but I'm not sure it's a recognised issue. I suspect it is specific to your system or everyone would be seeing it.Have you done the usual uninstall and reinstall of the whole NGX package, deleting original files, and then only installimng SP1c on top of the base install?sorry I can't be more help, Raulbestjake

I seem to having trouble actually red-lining the 737 engines on takeoff. I notice my thrust indication both on engine 1 and 2 are around 102.XX whenever I try to go full throttle. However, when I hold the F4 button, I get to 104+ and I start to redline the engine. Its odd, but I can see a twitch in the controls when I go just a bit farther back on the throttles. Windows shows the controls are normal and operating correctly, no twitches whatsoever. Does anyone know what setting I should look for to fix this issue? Has anyone experienced this same issue or is it one of those "FSX bugs" that cannot be fixed? Of course this issue happens with the NGX. Thanks for any suggestions/help. Hi Raul, and Jake, It appears that you are correct in the fact that Saitek throttles used with NGX won't redline. I have tested them as well in other a/c. Jake is right in that FSUIPC (possibly unregistered) will fix this issue. I just have to find the time to RTFM, since I own a copy.

Look at post 13 on this topic:http://forum.avsim.net/topic/364856-ngx-rolls-forward-on-loading/It's really easy once you're in FSUIPC. You don't actually have to RTFM, I just like to encourage people to do so with anything slightly complex. saves so much time in support calls!jake

Look at post 13 on this topic:http://forum.avsim.n...ard-on-loading/It's really easy once you're in FSUIPC. You don't actually have to RTFM, I just like to encourage people to do so with anything slightly complex. saves so much time in support calls!jake

I seem to having trouble actually red-lining the 737 engines on takeoff. I notice my thrust indication both on engine 1 and 2 are around 102.XX whenever I try to go full throttle. However, when I hold the F4 button, I get to 104+ and I start to redline the engine. Its odd, but I can see a twitch in the controls when I go just a bit farther back on the throttles. Windows shows the controls are normal and operating correctly, no twitches whatsoever. Does anyone know what setting I should look for to fix this issue? Has anyone experienced this same issue or is it one of those "FSX bugs" that cannot be fixed? Of course this issue happens with the NGX. Thanks for any suggestions/help.Hi Raul, and Jake, It appears that you are correct in the fact that Saitek throttles used with NGX won't redline. I have tested them as well in other a/c. Jake is right in that FSUIPC (possibly unregistered) will fix this issue. I just have to find the time to RTFM, since I own a copy.

Hey Raul,Yes, same. I saw the throttles move forward a litle when loading NGX. Ryan makes a reference to something similar early in tutorial 2, so maybe there was some work done on the way NGX SP1c interprets throttle response.I too do not see this on othr A/C (not that I've flown any for longer than five minutes since installing NGX!)You can apply specific profiles to PSUIPC so it might be worth at least trying it.If NGX is seeing your throttles wrong, FSUIPC can fool them into a different range of travel just for that profile, and then back again when you aren't using it. Give it a go. I can't think of anything else that could cause this bar dirty/broken pots in the controller.You can open a ticket, but I'm not sure it's a recognised issue. I suspect it is specific to your system or everyone would be seeing it.Have you done the usual uninstall and reinstall of the whole NGX package, deleting original files, and then only installimng SP1c on top of the base install?sorry I can't be more help, Raulbestjake

Thank you very much everyone for your help I will try all the suggestions given. After confirming this I will see what to do. Regardless of that fact though, I may or may not need to investigate this further as this might need FSIPC to be used properly! http://www.brcockpit.com/loja/produto/Throttle-Boeing-737-NG-%252d-15-a-20-dias-para-entrega.-Clique-na-foto-e-leia-as-informa%E7%F5es-na-%22Descri%E7%E3o-do-Produto%22..html This will definitely need FSUIPC registered version as that allows you to fully configure this baby! And found out this model also has backlight and manual trim for like the same cost of the Jetmax 737TQ...I'm still investigating on this as this is what iv'e always wanted to get since the launch of the NGX. What do you think...or should I just start a new thread?