As a gas/glow flyer, this OpenTx problem is the only remaining sore spot in the Taranis programming.
OpenTx 2.0, 2.1, and 2.2 for the Taranis all have a bug in it when using the Trim Idle Only function with crossed trims. (The Trim Idle Only functions perfectly without crossed trims, and crossed trims function perfectly without the Trim Idle Only selected.) The bug is that the Trim Idle Only function sticks with the THR trim button instead of following the assigned throttle trim. So with crossed trims this results in the assigned elevator trim operating with the Throttle Idle Only algorithm, and the assigned throttle trim not using the Throttle Idle Only algorithm. There are several different ways of getting around this bug, but the best solution is to allow the Trim Idle Only function to work correctly with crossed trims.
To view the open issue on Github about fixing the Trim Idle Only and crossed trims problem, go to this link:
https://github.com/opentx/opentx/issues/5635
I'm really hoping Aloft can use some of their influence to convince the OpenTx development team to finally resolve this issue.
OpenTx 2.0, 2.1, and 2.2 for the Taranis all have a bug in it when using the Trim Idle Only function with crossed trims. (The Trim Idle Only functions perfectly without crossed trims, and crossed trims function perfectly without the Trim Idle Only selected.) The bug is that the Trim Idle Only function sticks with the THR trim button instead of following the assigned throttle trim. So with crossed trims this results in the assigned elevator trim operating with the Throttle Idle Only algorithm, and the assigned throttle trim not using the Throttle Idle Only algorithm. There are several different ways of getting around this bug, but the best solution is to allow the Trim Idle Only function to work correctly with crossed trims.
To view the open issue on Github about fixing the Trim Idle Only and crossed trims problem, go to this link:
https://github.com/opentx/opentx/issues/5635
I'm really hoping Aloft can use some of their influence to convince the OpenTx development team to finally resolve this issue.