Same issue as the attitude controls repeater: the extension controls Repeater model depends on rapidly-changing controller properties (values/deadbands/mapping), which can trigger repeated model rebuilds and UI churn. Prefer a static model (names/ids) and compute/bind the live controller values inside the delegate.
Originally posted by @Copilot in #13915 (comment)
Same issue as the attitude controls repeater: the extension controls Repeater model depends on rapidly-changing controller properties (values/deadbands/mapping), which can trigger repeated model rebuilds and UI churn. Prefer a static model (names/ids) and compute/bind the live controller values inside the delegate.
Originally posted by @Copilot in #13915 (comment)