I've identified this issue to be caused by manual mode being continuously on when the configurator is active, as controlled by the logic here:
|
if (FC.isModeBitSet(modeElement.data('origId'))) { |
|
// The flight controller can activate the mode |
|
$('.mode .name').eq(modeElement.data('index')).data('modeElement').addClass('on').removeClass('inRange').removeClass('off'); |
|
|
|
if (jQuery.inArray(modeElement.data('modeName'), acroFail) !== -1) { |
|
acroEnabled = false; |
|
} |
This leads to misleading display of the status for the acro mode, seeming to indicate that acro mode is unable to be activated even when no other modes are active.
See the following screenshots for an example of the behavior of the acro mode when there's a range defined for manual mode, as opposed to when manual mode has no assigned range.

I've identified this issue to be caused by manual mode being continuously on when the configurator is active, as controlled by the logic here:
inav-configurator/tabs/auxiliary.js
Lines 403 to 409 in 515307c
This leads to misleading display of the status for the acro mode, seeming to indicate that acro mode is unable to be activated even when no other modes are active.
See the following screenshots for an example of the behavior of the acro mode when there's a range defined for manual mode, as opposed to when manual mode has no assigned range.