Something I failed to notice in my longer posts above: currently in the aircraft, there’s no way to “lockout” the autothrottle; in other words, any movement of your physical throttle(s) will override the AT’s N1 setting. So any noise in your throttle axis or any inadvertent bump or nudge will cause the engines to spool up or down. For now, the iFly devs’ response has been (paraphrasing), “firewall your throttle on takeoff when you press TOGA, then don’t touch them until you pull them back to idle during the flare.” But that method doesn’t let you “pre-set” your throttle level if you disconnect the AT at or above minimums like most of us would prefer to do.
Those of us familiar with how PMDG managed to come up with a setting to deal with when, if ever, throttles will override AT have a hard time blithely accepting that it’s not possible to come up with a similar setting in the iFly. The official “Flight 1” account on Discord posted some kind of non-sequitur when pressed on it:
What? PMDG aircraft are coded in C++, too, which is compiled into WASM. I don’t get WTF kind of excuse this is for a relatively straightforward question about control override settings.