There are several threads on this issue...referenced below is my post which is currently under investigation where even with the option of AT override set to NEVER, I am STILL able to override the AT with the throttles when the AT is engaged causing a battle between the throttle position and the AT mode. Have tested this with all AT modes on the NGX - with AT option set to 'NEVER'. http://forum.avsim.net/topic/349629-possible-throttle-issue-with-hf4/page__hl__aca856 With AT override option set to NEVER, when the AT is engaged and active, all throttle axis inputs should be ignored - this is the way it is supposed to work. It should not matter if you are using FSUIPC or not....yes, I am very familiar with the AT modes on Boeing aircraft and how they operate, I am not talking about AT HOLD mode. I have tested my hardware configuration with other PMDG aircraft as well as other brands - it's not a configuration or hardware noise problem...I suspect something is broken with the AT override option logic on the NGX. Hopefully this will be resolved in the upcoming SP, I will post on the referenced thread any feedback I get from PMDG support. Rob.

I hope this will be fixed

Sorry man, didn't mean to come across rude or anything. Always too easy to get a message across the wrong way by text-exclusive communication I guess... I'm willing to help people out where I can! Hope he didn't take my pointer to the FCOM sections in the wrong way. They basically describe the AFDS mode scenarios during takeoff, which is probably something useful for him.

Hi Etienne,for me your post was a helpful information, you even looked up the right section in the FCOM for me - so just don't mind!!! I have reported that problem to PMDG: in my opinion overriding of the computed throttle setting should only be detected when the hardware throttle is MOVED (and overriding is intended) - like it is described in the Introduction. Right now the NGX - when AT-Mode changes - sets the thrust to any detected DIFFERENT position of the hardware thrust levers. In the old 2004-version of the NGX this item was programmed correctly. Read you... Matthias

Good, we'll see what it does in SP1! Looking forward to getting my hands on it.

There are several threads on this issue...referenced below is my post which is currently under investigation where even with the option of AT override set to NEVER, I am STILL able to override the AT with the throttles when the AT is engaged causing a battle between the throttle position and the AT mode. Have tested this with all AT modes on the NGX - with AT option set to 'NEVER'.http://forum.avsim.net/topic/349629-possible-throttle-issue-with-hf4/page__hl__aca856With AT override option set to NEVER, when the AT is engaged and active, all throttle axis inputs should be ignored - this is the way it is supposed to work. It should not matter if you are using FSUIPC or not....yes, I am very familiar with the AT modes on Boeing aircraft and how they operate, I am not talking about AT HOLD mode.I have tested my hardware configuration with other PMDG aircraft as well as other brands - it's not a configuration or hardware noise problem...I suspect something is broken with the AT override option logic on the NGX.Hopefully this will be resolved in the upcoming SP, I will post on the referenced thread any feedback I get from PMDG support.Rob.

Still does it for me.

It changed in SP1 as far as I know.And it also works when you set to NEVERThat did it for me Pre SP1

Te issue, that is not an issue, can be solved by disabling throttle movement in thrust hold (from the menus), in this mode the only way to manually move throttles will be disengaging AT.

Agreed, thats what I do.

after hitting toga just ensure the throttles are fully firewalled i had that issue also

also make sure you don't have throttles mapped in FSUIPC AND in FSX...it's one or the other.

This is caused by hardware throttle spikes. As stated, it can be eliminated by setting the throttles to never override the autothrottle in the CDU menu options.

Even if I have the option "Never" set, it will override the AT and disconnect the AT. I tried enable them in FSX only and also in FSUIPC only. Always with the same result.

try to disable the throttles completilty and use the keyboard for the throttles just to try if the problem are the joysticks or not.