Axis and Ohs: Help and questions

Whats that program you are using? If you click on a switch does it give you the Lvar?

i don’t know that function of AaO: its collect lvars and provide me looong long list
so i loaded Blender and import SimObjects\Airplanes\PMDG DC-6B\model\PMDG_DC-6_VC.gltf :wink:

You can also check the POH. The numbers used there are often the same as the obj numbers. See p26 and further of the POH.

However, not all numbers can be found in the POH unfortunately!

not always in mine particular example you will not found 602 part

You are right! I will adjust my remark to make it correct.

Hello @ll,

be mindful that changing the value of an LVar will potentially only move the switch visually (=control the animation), but not actuate the system behind it. Those two actions are technically independent from each other.
If the LVar doesn’t trigger the actual system, then you have to use the ROTOR_BRAKE event (or even both at times).

2 Likes

To add: how to get the correct value to send to (>K:ROTOR_BRAKE):

Multiply the part number with 100 and add

  • 1 for left mouse click
  • 2 for right mouse click
  • 3 for mouse move
  • 4 for left mouse button release
  • 5 for right mouse button release
  • 6 for middle mouse button click
  • 7 for mouse wheel up
  • 8 for mouse wheel down

Which one of those works depends on the control that you are trying to access. Some have a completely different code, for example the lights potentiometers. Only way to find out is looking into the animation definition XML file.

In the above example, 60201 (>K:ROTOR_BRAKE) does the same as left clicking on the 602 part.

In the current AAO version 2.07 you have to use scripts, but in 2.08 you will be able to assign these values to the ROTOR_BRAKE event directly on the Add/Change Button dialogs.

5 Likes

Hi, thank you very much for your fast and valuable support. I have just tested it and the method you have suggested works perfectly well!

btw. this would also be the solution to simulate a “split” rotary encoder on an MIDI device. There are devices (MIDI Fighter Twister) where this can be set up as the default, and the encoder always only sends the velocities 63 - 64 - 65.

Those encoders don’t turn round&round, but instead only go one click to the left or right and then repeat the assigned action until put back into the center position. In real life they are usually spring loaded I guess.

In this example I am moving the heading bug. The scripts include controller acceleration, so the movement will get faster, the longer you keep the encoder left or right of the center. The movement stops when you move the encoder to the center position.

And here is the code - the script group and name must be exactly like in the screenshots or it won’t work. (Changing the group or script name changes the name of the script variable)

Base script:

(L:RotaryInput-HeadingBug)·0·==·(L:RotaryInput-HeadingBug)·64·==·or·if{·0·(>L:HdgBugCnt)·1·(>L:HdgBugRep)·}

Automated script

(L:RotaryInput-HeadingBug)·64·<·if{·1·(>K:HEADING_BUG_DEC|(L:HdgBugRep))·(L:HdgBugCnt)·++·(>L:HdgBugCnt)·}·(L:RotaryInput-HeadingBug)·64·>·if{·1·(>K:HEADING_BUG_INC|(L:HdgBugRep))·(L:HdgBugCnt)·++·(>L:HdgBugCnt)·}·(L:HdgBugCnt)·8·==·if{·2·(>L:HdgBugRep)·}·(L:HdgBugCnt)·16·==·if{·4·(>L:HdgBugRep)·}

1 Like

Hello @ll,

AAO 2.08 has been released today.

This version is mostly about stability and bugfixes. A lot has changed under the hood concerning the handling of controller events.

here is the change log:

Significant changes:

  • The input event processing logic has been redesigned, so it works the same for all input devices.
  • The startup and connection sequence of the app has been redesigned. The app will now try to wait until the aircraft has finished loading before it establishes the various data connections. This is to avoid problems with certain addon aircraft that don’t like it if LVars are assigned too early in the process.

Individual changes:

  • Change: Scripts: The output of the “Test” button is always copied to the clipboard, so you can Ctrl&V it into a text editor
  • Change: MSFS: AAO tries to match aircraft liveries to existing profiles for this particular aircraft addon
  • Change: the current simulator flight plan can be copied to the clipboard (Menu item in “Extras”).
  • Change: static Macros can be used in the Desktop/WebFIP logic
  • Change: MIDI Out now supports program change events
  • Change: it is possible now to access string variables in the WebAPI (for example to show the call sign on the StreamDeck)
  • Change: When assigning templates you now have the choice of what to merge exactly (so only parts of a template can be loaded into the current config)
  • Change: Saitek Panels: all controls now fully event based, MIDI mode can be configured for individual aircraft now, option to override the output variabls in MIDI mode
  • Change: Add/Change button dialogs: input value boxes now unlimited in range (to accomodate PMDG DC-6 ROTOR_BRAKE event triggers)
  • Change: Added startup error device file to catch instances where the app would not start fully when incompatible devices are connected.
  • Bugfix: Blacklisting MIDI devices crashed the app
  • Bugfix: Add/Change Button dialogs had trouble handling gamepads
  • Bugfix: Combo Buttons were only working when pressed before the actual button
  • Bugfix: Long/short clicks were duplicating
  • Bugfix: Local variables were not retaining their values when the app recovered from a SimConnect crash
  • Bugfix: custom variable import used incorrect headers
  • Bugfix: SOUND took precedence over everything else in scripts
  • Bugfix: Global automated script dialogs not handling duplicates correctly

If you are using the Elgato StreamDeck plugin, please make sure to download the new version 4.12 from the AxisAndOhs website

7 Likes

These are some very helpful updates and fixes! I’m excited to try out the new version. Thank you for keeping the new features coming.

Just received my Streamdeck today, next stop AxisAndOhs. Any advice on the best way to get started, there’s quite a few videos out there, but any in particular for a noob?

Can anyone see what I am doing wrong here? Trying to bind PMDG DC 6 Cockpit Door Open and Close to my Bravo Throttle. The GUST Lever works OK, but no the Cockpit Door


Any indication when it will be available at JustFlight.com?

2 Likes

Can anyone see what I am doing wrong here?

I can’t find any reference to an event that would open/close the cockpit door. The LVar you are trying to set is only referenced in the sound configuration of the DC-6, I don’t think that it controls the door animation. All I can see at first glance is a Component to control the door warning light, (L:dc6_253_obj, number)

The app has been sent to JustFlight on Monday, same as with SimMarket.

With JustFlight, vendors don’t have access to the shop system. We can only send them emails and then wait. I already tried to ask JF if something’s the matter, but haven’t received an answer yet.

2 Likes

I’m trying to set up A&Os to work with my button box in msfs. The button box has a load of momentary buttons, switches and push-rotary encoders but I cannot get A&Os to recognise a keypress for more than a very brief moment - the button number flashes up in ‘Assigned button/key’ then goes back to reading POV <0> DIR <0> ?
I’m only using the assigned buttons section and ive blacklisted all the other controllers so theres no interference.

Axis and Ohs is incredible. I want the update so bad. There is no way to contact Just Flight regarding the update. So I asked it by the Just Flight Forum. A lot of views but no single reaction. Is there an other way to update the app?

I’m only using the assigned buttons section and ive blacklisted all the other controllers so theres no interference.

There seems to be a stuck button on the device itself, which is repeating automatically (on-off-on-off
) Any idea what that POV control could be? I’m not sure how to catch that, this would require yet another blacklist for individual buttons. This is certainly possible. I suggest that you send me an email with your proof of purchase. The address is on the last page of the manual.

You don’t have to blacklist the others, you can isolate a specific device with the drop down box below the “Assigned
” box.

Customers contacting JF directly seems to be a good idea. This certainly helped the last time. I have written to my contact twice now, using different mail accounts, but did not get an answer. Very odd.