Hi, I have SP1 installed and own both the base NGX and 600/700 expansion. Ever since the update to SP1, I have noticed that that when I press the TOGA button shortcut after thrust stabilizes at 40%, and then move my hardware throttle to the "firewall", the n1 exceeds the takeoff limit. As a result, I have to carefully retard the throttle to match the limit on the n1 gauge, a very delicate task while simultaneously trying to control the ground rollout. I believe I have read a similar report here, but I cannot find it with the search function. Is this a new bug, or is this something I have to workaround and if so what is the workaround? I use the standalone CH products Pro Throttle, and FSX controls the throttle (not FSUIPC). Actually, I was using FSUIPC to control the throttle axis until SP1, could that have something to do with this behavior?

Try changing the at override setting in the cdu options.

Makes sense. I'll give that a try.I have thought about this, and it seems to me that this may have been an intentional change by PMDG to TO/GA's interaction with hardware throttles, with regard to the throttle hold stage on takeoff so that if needed the user can exceed the normal n1 limit to get max thrust in case of engine failure or for that extra "oomph" for evasive action. I need to have A/T override for the descent phase when in ARM mode, so using "never" is not really an option. However, I can use the never setting just for takeoffs, and return to my normal override during a/t hold/ARM mode during descent.I'm sure this change was documented somewhere, but anyways, I have found my workaround to this issue.