1 hour ago, Tuckster2020 said:

Can I assme the "key down event" would be the same as pushing a button AND/OR pushing a rotary button ?? Like the rotary button on the A320 where a "push" is setting it to managed mode and a "pull" is setting it to manual mode. 

Those aren't really related. The "Key Down Event" is triggered, when AAO receives "something" that can be interpreted as a button being pressed, and "Key Up Event" will fire when you release that button again. It depends on the actual hardware which one of the two or both will happen. With game controllers that Windows sees as Joysticks or Gamepads, that is all you have. Even the rotary encoders usually only send "press - release" button events, albeit very fast. For MIDI devices, like the X-Touch, this is a little more advanced, as AAO can determine if you are turning an encoder left or right (if it is set up correctly). In both cases = with rotary encoders in general, you only set a Key Down or a Key Up event, but not both.

When you look at these Button and Axis assignment dialogs in AAO, the upper part has a slightly different color than the lower part. The upper part shows what is going from AAO to the sim. The lower part is about what AAO receives from the outside. 

Edited December 8, 20214 yr by Lorby_SI

Hi

Having problems with Axis & Ohs through the Behringer X touch MINI and MSFS.

Everything was good until Wednesday Evening when I launched MSFS which told me I needed an update, going throuh the Xbox app, it started reinstalling the game.

2 days later I have updated files in Content Manager and loaded the FBW A320 

Putting the A320 on a Gate at EGCC I press Exterior Power Button Nothng!

I have deleted the templates and reloaded them, the app is connected to the simulator (it recognises the Aircraft) and pressing buttons gets a green light on the App, but, nothing happens in hte SIM.

Ive shut down SIM and restarted PC (you never know)

Im sure its a simple problem but, I cant find it.

I was so impressed with the X Touch and Axis & Ohs it made Simming a real pleasure, but, I seem to be stuck now

Any help would be appreciated

 

26 minutes ago, Tezbedz said:

it started reinstalling the game.

A full reinstall?

Please make sure that you still have the "lorbysi-content-hooks" package in your Community folder. If it isn't there, just install AAO again, that should bring it back.

Also, if you have updated the FBW too, make sure that the template that you are using in AAO is still compatible with the plane. FBW are constantly changing things with every release, including variables and input events. There is no guarantee that an AAO template will still work 100% after an update of the aircraft.

Edited December 10, 20214 yr by Lorby_SI

Can I use AAO for the Honeycomb Bravo‘s axes and buttons? I started the AAO app but could not see any axes represented in AAO. When I move one axis (e.g. throttle lever) nothing shows up in AAP.

i use Prepar3Dv5.3

Thanks!

Volker

Edited January 17, 20224 yr by vtracy

1. Start the AAO app

2. Connect it to the sim, sitting in the cockpit

3. Use the green "+" sign to add an axis

4. Select a variable or event to control

5. Move the axis on your device

6. Save

7. Same procedure for buttons

If this doesn't work, check "Hardware -> Device Blacklist" if your device ended up on the blacklist.

Edited January 17, 20224 yr by Lorby_SI

Can we use the stream deck plugin  together with the new AAO 2.24 Webserver for handling the FMS or MDCU or do we have to decide what to use?

Edited January 22, 20224 yr by Norwenkel

1 hour ago, Norwenkel said:

Can we use the stream deck plugin  together with the new AAO 2.24 Webserver for handling the FMS or MDCU or do we have to decide what to use?

The WebAPI is supposed to be able to handle all of the requests. If there are any problems with the real-world application concerning performance or bandwidth, I will split the webserver into a separate thread. But during my tests that didn't seem necessary.

AAO with Behringer Midi, FS2020.

Altitude +-100 assigned to rotary encoder. Altitude +-1000 can be used with an combo button. What can I do to use long press of the rotary encoder as the combo button to toggle between +-100/+-1000?

 

 

1 hour ago, dmenne said:

What can I do to use long press of the rotary encoder as the combo button to toggle between +-100/+-1000?

 

That will only possible with scripts. You would have to create three scripts, one each for INC/DEC with a local LVar, and a third that switches that LVar between two values. And that last script would be the one to trigger with the long press.

INC - script to be assigned to the right turn
(L:MyAltVar) 0 == if{ 100 (>K:AP_ALT_VAR_INC) } els{ 1000 (>K:AP_ALT_VAR_INC) }

DEC - script to be assigned to the left turn
(L:MyAltVar) 0 == if{ 100 (>K:AP_ALT_VAR_DEC) } els{ 1000 (>K:AP_ALT_VAR_DEC) }

Toggle script, to be called with the long press
1 (L:MyAltVar) - (>L:MyAltVar)

That is all you need. The two other assignments that are necessary for Combo ops can be deleted (unless you still want to use the combo)

Edited January 22, 20224 yr by Lorby_SI

Question regarding Map BVars to LVars (MSFS):

Is it mandatory to use a BVAR that AAO has scanned in "Manage LVAR to BVAR hook" or it can be also a BVAR i read with valid value in the delevoper mode in MSFS ?

59 minutes ago, Andi68 said:

Question regarding Map BVars to LVars (MSFS):

Is it mandatory to use a BVAR that AAO has scanned in "Manage LVAR to BVAR hook" or it can be also a BVAR i read with valid value in the delevoper mode in MSFS ?

You can use any BVar you want, and more. As far as I can tell, every BVar has a "getter", that the ist var name without an "action" at the end, and then several "setters", like "_Set", "_Toggle", "_Push" and numerous others (I think the developers can invent those too, like the LVars)

The actual mapping code is processd by the simulator, not by AAO, so you can use whatever the sim can understand. You can also make the scripts more complex, the three steps are just the basics. I recently made a mapping for the Aerosoft TwinOtter condition levers, that was quite complex by comparison...

LVar: (L:AAO_TWOT_COND_1, Number)
BVar get: 2
BVar set: (L:AAO_TWOT_COND_1, Number) 1 == if{ 1 (>B:CONDITION_LEVER_1_HIGH_IDLE) } els{ 1 (>B:CONDITION_LEVER_1_CUT_OFF) } 2 (>L:AAO_TWOT_COND_1, Number)

LVar: (L:AAO_TWOT_COND_2, Number)
BVar get: 2
BVar set: (L:AAO_TWOT_COND_2, Number) 1 == if{ 1 (>B:CONDITION_LEVER_2_HIGH_IDLE) } els{ 1 (>B:CONDITION_LEVER_2_CUT_OFF) } 2 (>L:AAO_TWOT_COND_2, Number)

So by setting the LVars to 1, the condition lever moves to the forward position, and 0 brings it back (the lever only has these two positions)

Edited January 27, 20224 yr by Lorby_SI

I have problem understanding the grammar:

(L:MyNav1Var)·0·==·if{(·1·(>NAV1_RADIO_FRACT_DEC)·)·}·els{·1·(>K:NAV1_RADIO_WHOLE_DEC)·}

green LED. But

(L:MyNav1Var)·1·==·if{(·1·(>NAV1_RADIO_FRACT_DEC)·)·}·els{·1·(>K:NAV1_RADIO_WHOLE_DEC)·}

Gives a red LED. Only for "1", any other number works too

Edited January 29, 20224 yr by dmenne
Made clearer what "works" means

41 minutes ago, dmenne said:

I have problem understanding the grammar:

(L:MyNav1Var)·0·==·if{(·1·(>NAV1_RADIO_FRACT_DEC)·)·}·els{·1·(>K:NAV1_RADIO_WHOLE_DEC)·}

green LED. But

(L:MyNav1Var)·1·==·if{(·1·(>NAV1_RADIO_FRACT_DEC)·)·}·els{·1·(>K:NAV1_RADIO_WHOLE_DEC)·}

Gives a red LED. Only for "1", any other number works too

Both scripts are wrong. Too many parentheses, missing K: event type with the first NAV, missing spaces. The color of the LED depends on the outcome of a dummy calculation that happens in the background. For one of the scripts it succeeds (strangely enough), even though the actual syntax is wrong. 

This is the correct syntax

(L:MyNav1Var)·0·==·if{·1·(>K:NAV1_RADIO_FRACT_DEC)·}·els{·1·(>K:NAV1_RADIO_WHOLE_DEC)·}

(L:MyNav1Var)·1·==·if{·1·(>K:NAV1_RADIO_FRACT_DEC)·}·els{·1·(>K:NAV1_RADIO_WHOLE_DEC)·}

Edited January 29, 20224 yr by Lorby_SI

Probably I would have found that solution when it would have been red in all cases.

Lorby Stream Deck plugin is causing the Stream Deck software to become unresponsive. This is for versions 6.16 and 7.06

If I remove the plugin, all of my other profiles (non-Axis and Ohs) work correctly.

EDIT: I deleted the A320 profiles and all seems fine now.

Edited February 7, 20224 yr by mrm0508
SOLVED