ap_alt_var_dec100 and *dec1000  seem to be missing here. I can't find them here. what am I doing wrong ?

 

Thanks

21 minutes ago, MindYerBeak said:

ap_alt_var_dec100 and *dec1000  seem to be missing here. I can't find them here. what am I doing wrong ?

 

Thanks

Sorry, I don't understand. What is missing where exactly? What is "here" and what are you looking for? Is this about something in the AxisAndOhs app? What are you trying to do?

Edited November 11, 20232 yr by Lorby_SI

7 minutes ago, Lorby_SI said:

Sorry, I don't understand. What is missing where exactly? What is "here" and what are you looking for? Is this about something in the AxisAndOhs app? What are you trying to do?

Sorry for not being clear.I'm looking to assign a button(rotary) - x-touch mini- using aao.I need ap_alt_var_dec100 but I can't find it in key down events.

Edited November 11, 20232 yr by MindYerBeak

33 minutes ago, MindYerBeak said:

Sorry for not being clear.I'm looking to assign a button(rotary) - x-touch mini- using aao.I need ap_alt_var_dec100 but I can't find it in key down events.

Firstly, the lists in AAO only contain the SDK events. Those may not be applicable to your aircraft, especially in MSFS. Many developers implement their own methods. Assuming that we are talking about MSFS, there is also the issue that the AP has multiple "slots" and you may need a script to access them.

If you are flying MSFS, then it is essential to provide information about in which exact aircraft you want to assign what exact button or lever to which hardware. Otherwise the answer is pure guesswork.

If we are talking about the default events, then what you are looking for is
100 (>K:AP_ALT_VAR_INC)
1000 (>K:AP_ALT_VAR_INC)

100 (>K:AP_ALT_VAR_DEC)
1000 (>K:AP_ALT_VAR_DEC)
 

The value that an event is called with is dialled into the box to the right of the key down/up selections -> check the AAO manual about that.

Edited November 11, 20232 yr by Lorby_SI

I'm using MSFS,the aircraft is the fsreborn 500 and the hardware is xtouch mini. Awhile back I created a general profile with spad.next (change spd,hdg,alt,vs)that works for all airplanes .So I installed aao again and and tried to replicate the same profile.Most events work for aao too.So far only sync hdg and ap_alt_var_dec and inc 100/1000 wouldn't work "out of the box" with aoo.

Edited November 11, 20232 yr by MindYerBeak

28 minutes ago, MindYerBeak said:

wouldn't work "out of the box"

The way AAO does it is actually right out of the (SDK) box - AAO is in essence just a translator between your hardware and the SDK.

I don't have that aircraft, but doesn't the FSR use a clone of the default G1000? Then the default events should work, and the more specialized knobs are controlled with input event (HVars) I think. For heading sync you need a script that copies your current heading to the AP, IIRC that is one of the examples that are already in the app ("Scripts-ACT_HEADING_TO_AP"). Scripts can be assigned to button same as the events, they appear in the same treelist.

Edited November 11, 20232 yr by Lorby_SI