I am trying to get the MCP working. I am stuck on a few knobs.

AFCAS_SPD_KNOB_ROTATE

I want to set this up as a quick turn, where a slow turn increases by 1 and a quick turn increases by 5 or 10. Not having any luck yet. This was what I tried for decrease and using ++ for increase

(L:AFCAS_SPD_KNOB_ROTATE,·Number)·--·(L:AFCAS_SPD_KNOB_ROTATE,·Number)

There is also an LVAR called AFCAS_SPD_KNOB_DEC and AFCAS_SPD_KNOB_INC but that has not worked either.

The Altitude actually works with the standard sim setting, but HDG, SPD etc does not.

4 hours ago, Crabby said:

There is also an LVAR called AFCAS_SPD_KNOB_DEC and AFCAS_SPD_KNOB_INC

Is that really an LVar? How/where did you get this name from?

In general, LVars are not really meant to be used for controlling things. Their original purpose is controlling animations and storing data. LVars are not events - on their own, they don't do anything.

INC and DEC - that looks more like IEs/BVars to me. Check the event selection dialog in AAO, specifically the tab "MSFS IEs"

Edited June 29Jun 29 by Lorby_SI

Apparently you have to replicate the entire behavior code, just setting LVars is not enough

(L:AFCAS_SPD_KNOB_ROTATE,·enum)·++··100·min·(>L:AFCAS_SPD_KNOB_ROTATE,·enum)·
(L:AFCAS_SPD_KNOB_ROTATE,·enum)·100·==·if{·0·(>L:AFCAS_SPD_KNOB_ROTATE,·enum)·}
1·(>L:AFCAS_SPD_KNOB_INC,·bool)

(L:AFCAS_SPD_KNOB_ROTATE,·enum)·--·0·max·(>L:AFCAS_SPD_KNOB_ROTATE,·enum)
(L:AFCAS_SPD_KNOB_ROTATE,·enum)·0·==·if{·100·(>L:AFCAS_SPD_KNOB_ROTATE,·enum)·}
1·(>L:AFCAS_SPD_KNOB_DEC,·bool)

Replace SPD with HDG for the other knob. Larger increments are not possible IMO.

Edited June 29Jun 29 by Lorby_SI

On 6/29/2026 at 2:12 PM, Lorby_SI said:

Apparently you have to replicate the entire behavior code, just setting LVars is not enough

(L:AFCAS_SPD_KNOB_ROTATE,·enum)·++··100·min·(>L:AFCAS_SPD_KNOB_ROTATE,·enum)·
(L:AFCAS_SPD_KNOB_ROTATE,·enum)·100·==·if{·0·(>L:AFCAS_SPD_KNOB_ROTATE,·enum)·}
1·(>L:AFCAS_SPD_KNOB_INC,·bool)

(L:AFCAS_SPD_KNOB_ROTATE,·enum)·--·0·max·(>L:AFCAS_SPD_KNOB_ROTATE,·enum)
(L:AFCAS_SPD_KNOB_ROTATE,·enum)·0·==·if{·100·(>L:AFCAS_SPD_KNOB_ROTATE,·enum)·}
1·(>L:AFCAS_SPD_KNOB_DEC,·bool)

Replace SPD with HDG for the other knob. Larger increments are not possible IMO.

I am amazed at how complicated developers are making controls. Seems like gone are the good old days of event IDs and rotor_brake

3 hours ago, Crabby said:

I am amazed at how complicated developers are making controls. Seems like gone are the good old days of event IDs and rotor_brake

IMHO it is not like that. Those/many/most developers don't think about external controls at all. External hardware is not really part of the SDK, probably because these devices are irrelevant on the XBox (?). What we are doing most of the time is replicating the behavior code, meaning the code that is executed in the sim when you operate the mouse. There are situations where even that fails, for example with components that only use O: or I: variables (that has improved in MSFS 2024, but it is not quite there yet). Granted, those controls are often fakes, with no real aircraft system attached to them, but still.

And because we need the mouse code, the best course of action is looking at the behavior code itself, using the MSFS developer mode, Tools->Behaviors, then click back into the sim, hover the mouse over the control you are interested in and press Ctrl+G. Then inspect the MouseRect and/or ...Interaction... components and try to replicare the RPN code you see there.