Having some trouble with the Saitek throttle and the NGX. It seems that when in the air, the throttle wants to idle at 35-40% N1, which is higher than it should. I'm sure that this is related to hardware as when I look at the VC throttle, when I pull it back to idle it stays there for a brief moment then all on it's own climbs back to 35%. The same goes for the upper limit of the throttle range. I've of course tried configuring the throttle through both FSUIPC and FSX, as well as setting up small deadzones at either end of the range. I've also noticed that the movement of the throttles don't match FS at all, ie. 40% N1 in FS relates to about 15% on the physical throttle. Not sure what else to try to fix this. The -800 is slippery enough without trying to make an approach with 40% thrust!

OK, so half of this issue is solved in regard to the VC throttle moving of it's own accord due to FS limitations of simulating the flight idle function. There is still an issue however, that with the hardware throttles connected the idle N1 is reporting roughly 10% greater than when they're disconnected. This has nothing to do with the EEC as the issue isn't present without throttles connected. I've seen a good few posts over the last 24 hours of people who describe something very, very similar ie a 40/50% N1 idle, and who have accepted the issue being one of the EEC function, along with the -800 requiring good energy management on decent. While there is truth in this, I think it may be somewhat hiding a real problem from view. At this point I've tried with 3 different hardware throttles, both in FSUIPC and FSX configs, with the same issue present. With that in mind I think it unlikely that this s specifically hardware related, but rather an issue lying within the 737 or the way in which it plays with FSUIPC. I'm going to try removing FSUIPC completely today to see if that makes a difference, but failing that I'm out of ideas.

I think it isn't an issue, but i think it is how the real thing works ;) maybe at higher speeds with a LOT of air blowing through the engines you just can't get the N1 Fans all the way back to 27%. I see that when flying 280 Knots Indicated the Idle does not go all the way back to 25% but more around 40%. And as you said the 737NGX does need good descent management like the real thing. Doesn't make it even more fun when it is a bit more challenging to operate it within limits and you really have to work on that sometimes? Just my thoughts.This isn't meant personal to you, but a lot of people here complain about engines not all the way to idle or spoilers not working because they cannot manage to descent in a decent way! I don't think there are big mistakes in the NGX according to the Flight Dynamics, A/T system and AFDS. It is actually very smooth and flying like the real thing (i have 185 hours on a 737NG simulator, so i can tell).

Callum, If you're getting different values with your hardware disconnected, then you might very well be correct. I'm not that well versed in hardware/calibration/controller issues, so I can't be of much help beyond suggesting temporarily removing FSUIPC and/or recalibrating in order to diagnose a deeper problem. To be safe, I'd recommend submitting a support ticket if you haven't already done so. And as you did here, make sure to differentiate the problem from the expected Approach Idle behavior.

Cheers nick, finally someone who's gotten their head round what I'm saying! Will be putting in a support ticket today, just wanted to post here as well to see if any of the other who are having a similar issue could recreate with regards to the hardware. I suspect that FSUIPC is playing a part here, even if the throttle is not directly configured through it, as the throttle motion behaves very differently than it does through the FSX config. Will post back up once I've had the chance to test again today.

Try adjusting the throttle sensitivities in the controls menu in FSX.

Tried all of that, even to the extent of creating stop deadzones and adjusting the curve. I think the problem must be with the way the NGX interacts with FSUIPC somehow, rather than it being a matter of configuration.