Hi there..I usually get my bindings for axis and ohs from a script someone has done previously, but having no joy with the FFX Hondajet

How would I bind for example

RIGHT INNER KNOB CW	N/A -- MSFS Still does not have Bindable H:Events	H:AS3000_TSC_Vertical_BottomKnob_Small_INC
RIGHT INNER KNOB CCW	N/A -- MSFS Still does not have Bindable H:Events	H:AS3000_TSC_Vertical_BottomKnob_Small_DEC

 to a rotary knob (xtouch mini)  
I usually of course select it from a list, but this isnt there..I got the values from the document provided by the plane designer..is it actually even possible to do easily?
This is the actual binding document 
https://docs.google.com/spreadsheets/d/1-N4BEuGB7-NL-Pfdxwv7Gxaq1OyxFmc9OspsqQ0_lgM/edit#gid=2989639
Hope that makes sense ! 

Thanks 

 

The two HVars above are pretty much default, and they are in the lists in AAO (in the group "HTML Variables"). Try using the filter box at the bottom of the event assignment dialog. When the dialog with the treelist opens, immediately start typing "as3000_tsc_vert" and hit Enter.

If a variable or event really isn't there, wrap it into an RPN script or add it to the AAO database manually (menu "Scripting->Input custom variables manually").

Edited January 31, 20233 yr by Lorby_SI

Thank you ! ..thats very helpful indeed ! will let you know if I have any further issues
Out of interest why do I see nothing if I use 

watch simulator events/watch simulator variables. 
Should I not see these come up when buttons are pressed and knobs turned?

Thanks again 

 

The example above working great ..as you say it was already in there 🙂 
Having trouble with ones that are not  there..

for example this one when I add  CSC PUSHED as a custom event nothing happens..  (should it be the whole string L:CSC PUSHED  ?)I see I have choice of K or B when doing that ..I assume this is neither of those..
Not really sure about the alternative- wrapping into an RPN script.. 
Sorry to be asking  such basic questions ! 

CSC or AT (E2)

AUTOPILOT AIRSPEED HOLD ON

L:CSC PUSHED

L:CSC_MODE_BOOL

3 hours ago, vsukpadman said:

Should I not see these come up when buttons are pressed and knobs turned?

No, that is not possible. Only the default SDK  (K:) events can be tracked that way.

The custom or complex controls can be tracked in MSFS developer mode, specifically in the Behavior dialog. 

A good starting point is flightsim dot to. There are a lot of templates, scripts and profiles for the most common aircraft in MSFS. Even when a profile was made for a different piece of hardware you can still import the scripts that come with it and use them. in many cases, triggering one single "thing" (K-Event, LVar, HVar, BVar) is not enough to get the desired result. At some point there is no way around scripts.

Edited February 1, 20233 yr by Lorby_SI

Thanks for the detailed info..yes I usually use flightsim dot to , this plane was there, but only a few of the commands ..hence finding the binding document... 

but still stumped on how to enter for example the autothrottle button..  L:CSC PUSHED.  I just cant make it press the button

It does seem a bit black magic !..im used to datarefs in X plane which are WAY easier !  🙂

24 minutes ago, vsukpadman said:

Thanks for the detailed info..yes I usually use flightsim dot to , this plane was there, but only a few of the commands ..hence finding the binding document... 

but still stumped on how to enter for example the autothrottle button..  L:CSC PUSHED.  I just cant make it press the button

It does seem a bit black magic !..im used to datarefs in X plane which are WAY easier !  🙂

MSFS is not XPlane.

Lvars are kind of the same as datarefs though. They are not events, they are variables. You can either make AAO search for them (Scripting menu) or just enter them into a script to try what values need to be sent and if the LVar mentioned is really the only thing that has to be manipulated (normally they control only the animation)

1 (>L:CSC_PUSHED, Number)

or
1 (>L:CSC_MODE_BOOL, Number)

and
0 (>L:CSC_MODE_BOOL, Number)

or as a toggle script
1 (L:CSC_MODE_BOOL, Number) - (>L:CSC_MODE_BOOL, Number)

Edited February 1, 20233 yr by Lorby_SI

18 minutes ago, vsukpadman said:

Thanks for the detailed info.

btw - AAO comes with a 100+ pages manual, where you can find this information - and more. Just click on the question mark in the menu bar.

3 minutes ago, Lorby_SI said:

MSFS is not XPlane.

haha indeed..lets not go there LOL 
Great info ..I will do some experimenting and reading your documents ..really appreciate it !