Lorby-SI Payware

Hello @ll, AxisAndOhs version 2.10 has been released today. It should appear in your account in the shop where you bought it in the next few hours. SimMarket usually sends you an email too, JustFlight doesn’t. Changes in AxisAndOhs version 2.10 Main change: enhanced tracking of input event timing, so especially rotary encoders are working more reliably and fluently. This affects all “Button” ops. Change: Add/Change button dialogs: “Device” box relocated, separate ignore/lock controls Change: “Roll” and “Adaptive repeat” for buttons Change: WebAPI events can be used as AxisInput Change: Resizing the main window is now possible (…

Hello @ll, As of 1st of September 2021, all sales operations of Lorby-SI will cease. All payware assets and IPR have been transferred to our partner company "Lorby Wildfire Response Inc." in Canada, a subsidiary of "Wildfire Training Solutions Inc." handling all matters software. In a first step, the "vendor" in the various shops will be changed to reflect the new ownership effective immediately. Over the next few weeks all other assets (websites, screenshots, manuals etc.) will be adapted or rebuilt to reflect the new ownership too. And there will be another shop of our own where you can purchase the Lorby products. Lorby-SI will still exist, but it …

Hello @ll, in AAO version 2.12 the app will have voice recognition as an additional input device. It just uses the Windows voice assist system, so nothing too fancy. But it generally seems to work well. If you would like to help testing it, please send me a message with your proof of purchase (order number and shop). Non-english speaking computers would be very welcome too 😀

The new version has just been uploaded to SimMarket, and JustFlight have been notified as well. Here is the changelog: Changes in AxisAndOhs version 2.11 Main change: It is possible to use a “master” configuration for an aircraft and mere liveries of it will reference back to it without creating their own copy (but you can still do that of course) Change: RPN logic can process nested ifs Change: no need to merge a template that is empty anyway. Change: process MIDI input of rotary encoders without waiting for event reset (every click triggers an action now) Change: redesigned the RPN SLEEP, it is SPLIT now (but both work), additiona…

Good Afternoon UK time. I have continued trying to get A&O working within MSFS 2020. This morning, I completed a full, clean install of A&O's 2.11, followed the instructions for the Bridge installation, I believe "good so far". Switched on the VRinsight Boeing style Combo 2, Started MSFS 2020 with the FBW A320 on the runway at EGDD, started A&O, then the bridge. I was able to add the VRI panel with the correct port - port 5 and it appeared to work. On pressing the green connect button in the bridge window, it connected and then shut itself down. I then expected to be able to press a button in A&O but it "just sat there". I am clearly missing somethin…

Is it possible with AAO to control the camera in MSFS, for example with the mouse. I find no alternative to this. /Thomas

Using the latest axis&ohms with msfs2020 and the x-touch mini. All my previous profiles are working fine. The problem starts when I click the green plus(+) button to add a new assignment my mouse will freeze. Any ideas?

Hello. I can't figure out how you bind the rotary magneto knob on the Honeycomb Alpha. Can anyone advise me on how to accomplish this? Any guidance would be greatly appreciated.

Can someone tell me where to press "change" on this screen. (from the AAO help file PDF which is shown below)? (It says to press "Change").

I do not see any earlier version on the Lorby webstie listed for download?

What to do? P3d v5 totally freezes with firefighter p3dv5 and pmdg 747. I have installed p3dv5 version of firefighter X . Yours sincerely Jens

I have attempted to use AxesandOhs to calibrate the PFC Throttle Quadrant. Despite reading the documentation and the forum posts, the Throttles do not change anything in the DC-6 . I have used fsuipc7 but the throttle sensitivity is quite limited. Any help would be appreciated--Thanks

Hi, I am currently builiding an X-Touch mini profile for the M20 Ovation in MSFS. I've just bound 2 rotaries to change Com1 and Com2. The increment (COM_RADIO_FRACT_INC_CARRY) works as expected increasing the Com1 frequency (Increment by 25KHz and carry when digit wraps) but the corresponding decrease (COM_RADIO_FRACT_DEC_CARRY) still increases the frequency rather than decreasing it. This happens for Com1 and Com2 but if I use (COM_RADIO_FRACT_DEC) instead that works as expected but obviously doesn't wrap the digit. Anyone else seen this and found a solution - I suspect scripting is the only solution (until Asobo fix it) but as a complete noob to RPN I wouldn't k…

I suddenly get weird effects in AAO. Sometimes it occurs in other places. The buttons seem to work and it does not affect the function of what I can see. What could it be due to. I have tried reinstalling without success /Thomas

Has anyone identified the variables to control the CHR button (off/on) above the clock, the ATC on/off/standby button (near transponder) and the panel & pedestal Flood light brightness on the FBW A32NX Development version? I have check the various on-line references with no success, and tried monitoring the variable using the SDK. I've got most of the other key functions working using AAO and the Behringer X-Touch Mini and other controllers. Would be happy to share info if you need some functions. Thanks.

Hello I'm trying to use the behringer x-touch with AAO in the CJ4. Ive downloaded a template (WT_CJ4_INDEP_210514) from the WT discord site. The problem is .. When turning a knob (height for instance) clockwise ie increment, AAO starts sending seemingly random up and down events, such as AP_ALT_VAR_INC_100 AP_ALT_VAR_INC_1000 AP_ALT_VAR_INC_1000 then (I'm still turning clockwise) AP_ALT_VAR_DEC_1000 AP_ALT_VAR_DEC_1000 AP_ALT_VAR_INC_1000 AP_ALT_VAR_DEC_1000 etc (cant see a pattern) What is going on here thanks PS. How would i know when a new version of AAO comes out ??

Hello @ll, Hotfix 2.09 b04 is out now. This fixes the issue with the slider type axis not being processed. This version also has a new button on the "Add/Change Button" dialogs to suppress the currently visible input event. This should help if you have a stuck button or encoder on your devices somewhere. Other bugfixes: LEDs getting stuck for slow/fast turn button configurations App crash when selecting “None” on the axis assignment dialogs Range protection cuts LVar values Saitek Panels not remembering the operation mode automatically

Hello @ll, AAO 2.08 has developed an unfortunate bug - "slider" type axis are no longer working. Sorry about that, not sure how this happened. Please roll back to the 2.07 if you experience this - or consider sending an email with your proof of purchase to the address on the last page of the manual. A hotfix may be available soon.

I have two Saitek switch panels both with various switch assignments made in "aircraft midi mode" that work well. Problem is that if the AAO program is closed and restarted the two switch panels revert back to default mode in the Saitek panel config window and I have the two switch panels duplicating themselves with the same default Saitek firmware (?) assignments. If I then disable the switch panels in AAO, re-config them to aircraft midi mode and re-enable they are back to working as I originally assigned. Just annoying have to do this every time I start up AAO. Thanks. Edit: Also happens if I save the assignments as a template then re-apply that templa…

And me again. I tried using a case statement in my script, eg: 30·20·10·3·(L:XMLVAR_BoostFuelPump,·number)·case·(>L:DEADBEEF) I would expect it to be something along the lines like this switch XMLVAR_BoostFuelPump { case 0: DEADBEEF = 10 case 1: DEADBEEF = 20 case 2: DEADBEEF = 30 } This works quite well for XMLVAR_BoostFuelPump 1 and 2, if it is 0 however, I get 0 returned, not 10. What am I doing wrong? From reading the SDK documentation the syntax should be correct. [values] [# of cases] Variable case any help is appreciated

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: Scri…

AAO sees the GoFlight GF-LGTII Gear/Flaps/Left/right switches but does not see the three rotaries which are meant for rudder/aileron/elevator trim. This is similar to LINDA which did not see them either but in that case FSUICP came to the rescue and would recognize and assign to them. The rotaries are the assignable two buttons in each direction switch type. Using AAO 2.08 for MSFS 2020. Thanks for any ideas.

Hey, i tried updating to v. 2.08 and it seemingly went all fine. Also dl'ed the new stream deck library. But now button presses on the streamdeck take upward of 15s to process in the sim. Rolling back to v3 and 2.07 respectively makes button presses instant again. Is this known or may I be doing something wrong?

Click the + button to add a new axis assignment. Select "none" from the "Select simulator axis" dropdown list. AAO closes/crashes without any warnings. Also happens if you edit an axis assignment from some existing axis to "none". This is with Win10 and the MSFS 2.08 version. Otherwise it's working ok.

Hi All, Purchased AAO today and got my head around most of it but I cannot seem to set the battery switch on my honeycomb alpha yoke properly. The only option I can find is to toggle the battery master within MSFS but I need one that sets it either on or off rather than a toggle. Is there a workaround for this or is the only option to still map this within MSFS? Regards, Andrew