[BUG] Altitude & heading setting jumps

We have been getting some reports from our RV-10 customers that when using
their hardware controllers to set the autopilot altitude it will do increments
of 1000 and the heading increments of 10 degrees. Additionally, it sometimes
happens when clicking on the knobs. Their other planes work fine, so this is
an isolated issue. On our side:

  • the autopilot section is set up identical to our RV-14 which doesn’t have this problem
  • the RV-10 features three G3X screens: two PFDs and one MFD

I thought that the problem could lie in the PFDs. While the knobs are named
differently, I suspected that clicking on the left PFD could also trigger the
right one. In panel.xml the AltimeterIndex tags are commented out, as I was
having problems getting the screens to work with separate altimeters. Could it
be that I need to add them back? Is there any suggestion to fix this issue?
Below is a snippet of my panel.xml file in case it helps. If you need a copy
of the aircraft to check, let me know.


Hello @SWS-AlexVletsas This is the default behaviour of our input events it
seems. On most aircraft, these events are intercepted through JS or behaviour
templates and replaced with explicit calls to set events… You can have a
look at the AltitudeSelectManager js class in msfssdk.js for the WT
G1000 for a JS example. Or have a look at the
ASOBO_AUTOPILOT_Knob_Altitude_SubTemplate to see how it’s overridden on
the A320 for a behaviour template example. Same goes for heading and speed
selection. Regards, Sylvain

An update on this topic, it seems that when you have more than two knobs for the same function in the cockpit and you use a keybind, the outputs will jump in steps of 10 instead of 1.

I.e. if you have two heading knobs and bind the heading increase/decrease to a controller, your heading bug will jump by 10 degrees. This is now reproduced on two aircraft. One uses the default G3X, the other one uses custom avionics and the default AP heading knob XML template.