Axis and Ohs: Help and questions

Maybe just a coincidence but bravo template for fbw in my github was uploaded 27 days ago. If that is where you downloaded it, there is up-to-date version in Releases section for Stable, Dev and Exp versions.

If you downloaded

1 Like

Yes, I believe it was.

I’ll try to check later if there are any issues with dev/exp versions. There should not be since friend uses them daily with latest dev or exp version.

I’m sure it’s operator error. Do you have your github link for your profiles?

I’m wondering if there is somebody out here who can provide me some scripts or templates for the B787. I managed to script Speed and Heading but failing creating a altitude change related one. Maybe someone can give me a hint.

FBW A32nx v2.0 releases are for HC bravo. Didn’t have time to test yet but I checked the scripts and those should work, at least dev/exp version. You need to import scripts and template. And if you check the Tips part of this page, you’ll see how to change managed/selected mode: aao_guides/fbw_a32nx_guide.md at main · blindye/aao_guides · GitHub

3 Likes

Thanks a lot bLindyee. My x-touch is working again flawless with the FBW A320 dev. version.

1 Like

On my Bravo throttle quadrant I need to assign autopilot on/off to the autopilot button (EMB110)
I have tried everything with Axis & Ohs and have had no luck :frowning:
Could someone please point me in the right direction.

1 Like

Could someone please point me in the right direction.

If the plane doesn’t react to the official simulator event ID (“AP_MASTER” in this case), then the developer implemented his own code. In that case you only have three options:

  • Ask the developer of the plane what events or variables have to be used to trigger the desired effect
  • Dive into the model definition files to find our yourself (this is only possible if these files are not encrypted - a lot of payware planes are though)
  • Use the model behavior debug feature in MSFS Developer Mode to get some hints about what is going on when you operate the control in the virtual cockpit. Then replicate that in AAO

Thanks for the response.
I can make the button turn on or off individually but can’t assign them combined.


Unable to select toggle:

Or I’m doing the wrong thing, the instructions don’t address this and I am unable to find anything on the internet with AP master toggle with axis and ohs.
Thanks for any further assistance you can provide.

if there is no AP Toggle that works for that plane it´s the right thing to go for two events (ON/OFF).

But you have to make two button assignments for the same button (as a “Key Down Event”).
One for ON, one for Off. (Each time as Key down and scratch the key up event)
Then assign the same Button to “Assigned Combo” and check the “is toggle function” in both assignments.
Last, on one of the two assignments check “suppress Key Down Event”

but can’t assign them combined.

What does that mean? What kind of control is this, a momentary push button (=a toggle) or a rocker switch that stays in the on or off position permanently? And why are you using RPN scripts instead of assigning the events directly?

  • If it is a momentary push button, you assign the “AP_MASTER” event to key down. Every push of the button toggles between AP on and off.
  • If it is a switch, you assign AUTOPILOT_ON to the key down event and AUTOPILOT_OFF to the up event.

If the plane does not react to AP_MASTER, but works with AUTOPILOT_ON / _OFF, you can create a toggle script like this:

(A:AUTOPILOT MASTER, Bool) if{ 1 (>K:AUTOPILOT_OFF) } els{ 1 (>K:AUTOPILOT_ON) }

Hey,
just a question is there anyway to change views with AaO?
Thinking about binding one Yoke button to toggle views and maybe putting a long press for Cockpit view.
That feature is sadly not availiable through the MSFS Keybinding options :frowning:
Maybe is there a way to emulate a Keyboard button press via AaO, so i can bind it that way to my Yoke button?

Thanks for your explanation, I’m starting to better understand AaO.

(A:AUTOPILOT MASTER, Bool) if{ 1 (>K:AUTOPILOT_OFF) } els{ 1 (>K:AUTOPILOT_ON) }
did the job, thank you :slight_smile:

Good evening, is there a way to get a long press working with the Streamdeck plugin?
Would love to bind some toggles with 3 positions to one button (like Windshield Anti-ice off, low, hi)

Would be nice if this could be somehow possible :slight_smile:

Long Click is only possible with the “Button” asset, that registers in AAO as an input event. The other StreamDeck buttons control their respective events, scripts and variables directly, they live outside of the AAO input logic. So a long click would have to be implemented into the SD plugin itself - at the expense of even more things that have to be configured by the user.

For simulator controls that have more than two states you could use a script that cycles through each position on each button press: off → low → high → off → low…

(L:ASCRJ_AICE_WSHLD_L, Number) 2 >= if{ 0 } els{ (L:ASCRJ_AICE_WSHLD_L, Number) ++ } (>L:ASCRJ_AICE_WSHLD_L, Number)

1 Like

Is there any possibility to get the aircraft name in a script? Axis and Oh’s shows the name and livery, can I access that somehow? I would like to do different things in a script depending on the aircraft. Thanks!

everywhere have a streamdeck Profil 15 Button for the cj4 plane with msfs and working Titel Mode.

or how can i change a 32 Button Profile to 15 Button streamdeck Profil

No, sorry. Accessing and/or processing string simulator variables is not possible. You will have to create an individual script for each aircraft.

What is the use case, what do you need this for?