but strangely the mode knob didnt …it starts turn with the encoder and flips back instantly
Still working normally here (FBW mod, devel version)
Well Lorby,
first of all thank you very much! You are a godsend for the simming community.
With your hints, tips and tricks I got the A32NX to a point I never thought was possible (in terms of controlling).
After countless hours of trial and error I have a template to share with the community for controlling the A32NX with the X-Touch via AAO. I even made a documentation on how to use it.
Sadly, I‘m not allowed to share a link but you can find it on Flightsim.to
I even got the Button LED‘s on the X-Touch blinking:)
Next I‘m trying to get the LED-Rings working (but that could be a tough one).
Greetings and best wishes.
hello agin def not working at my end , is there a way to wipe the scripts for me to start again afresh ,i uninstalled axis and ohs , then installed it again but the old scripts where still there, ? i assume that the are stored not in the axis ohs program , hence if i could find where they are installed i could try a fresh installations since ive prob knackered things for myself. and a fresh start me thinks would e good.
cheers again
harry
Any Ideas why the error:
„ import failed object reference not set to an instance of an object“
Could appear when trying to import a AAO Template?
hello,
Do you have a tutorial for the led lights on the Touch Panel.
I have only one for AP
I need
alt
vs
nav
hdg
and many more
Thx and regards
hello Axisor0…its prob something ive done in my quest to understand this …thats how Im asking lordySi how to totally wipe saved scripts since uninstalling and reinstalling axis and ohs isnt clearing previously saved scripts for me.
BUT i really do think that what lordySi isnt a million miles away from being a must have when coupled with a behringer for control of ailriners. my next task is to create a shell for the behringer to more closely resemble the fcu .
cheers for your help with this and if theres anything I can an do just shout out…youlss soon be sick of this mad scotsman.
cheers the noo
harry
What a great job!!! Congrats !
Do already have a tutorial to make my Xtouch mini like this one ? 
Cheers
The path to config are in the manual
“C:\Users…\AppData\Local\LORBY_SI\
There is also folder called LORBY-SI in \AppData\Local, delete that too
Have you tried unassigning them under the tab „global scripts“?
Also if you load a template you could first try to „delete your current config“ before.
Hi, sounds like a broken Template, or a version conflict.
Can you please send that template to me so I can check? I’m about to release the 2.04 and if there is a problem, I’d rather solve it.
Email address is on the last page of the AAO manual.
1 Like
From what you describe, there seems to be interference from something else. Did you assign any automated scripts (global or airplane level), a button that uses the same variable or another addon doing the same thing? And is that the same aircraft as before the update?
Mail is out.
Thank you for checking what could have went wrong!
Cheers
Hi, while progressing with the key bindings some more questions came up.
a) Virtual keys
In the simulator I have e.g. following keyboard bindings:
V - show map
SHFT+CTRL+ALT+L - translate cockpit view to the left
If I assign just the letter ‘V’ as a virtual key in AAO it works, map will be displayed.
If I assign SHFT CTRL ALT L as a virtual key in AAO it does not work, nothing happens.
b) Could it be that a bunch of the simconnect events are not (yet) functional? None of the events I tried from the ‘View’ and the ‘G1000’ section are working.
Thanks.
As someone who hit that wall before you: you’re right. For Views, I use AAO’s key mode to access the keyboard shortcuts. For the G1000, you have Simconnect commands starting with “AS1000” (IIRC you may need to install the MobiFlight MSFS community module to see these, full list here: MobiFlight Event Module SimConnect Event IDs - Pastebin.com).
you have Simconnect commands starting with “AS1000” (IIRC you may need to install the MobiFlight MSFS community module to see these, full list here:
NO! Do not install Mobiflight. The Mobiflight event IDs are mapped to their internal syntax only, and are invalid in AAO. You would just add another WASM module to MSFS, serving no purpose (for AAO) at all. But you can use the names that are listed in Mobiflight, just remove the “MobiFlight.” part and just use the rest of the name string as H: var (see below)
The glass cockpits and many instruments in the Asobo planes are controlled with HTML / H: variables. Many of those are directly available in AxisAndOhs, others you can find on the Net - or find out yourself too (developer mode → model behavior debug). AAO also has a scanner to look for them, but most H: var names are constructed from templates, and fining the correct name is tricky.
Other systems may be controlled by LVars, which you can also use in AAO (Scripting → Read LVars from sim)
In AAO you can access all of the H: and L: vars in the RPN scripts like this:
1 (>H:AS1000_PFD_SOFTKEYS_4, Number)
or, if their name is known to the app, by assigning them to a button directly using the HTML-Variables event group.
SHFT+CTRL+ALT+L - translate cockpit view to the left
Personally, I’m using the cursor keys for camera movement.
But anyhow, I will look into that combo. Left or right modifier keys? (Ctrl, Shift, Alt)
Could it be that a bunch of the simconnect events are not (yet) functional?
Correct. View commands and the G1000 events are listed in the SDK documentation, but they do nothing.
Any Ideas why the error:
„ import failed object reference not set to an instance of an object“
Could appear when trying to import a AAO Template?
Hello @ll,
could somebody who sees this error please contact me? I need the “Details” from the error message window (there is a button on it)
This is what I’ve been doing, but I thought it required the Mobiflight module to be able to “see” the H: variables. I’ll remove it then (I have no other use for it), I stand corrected, thanks.
This is what I’ve been doing, but I thought it required the Mobiflight module to be able to “see” the H: variables. I’ll remove it then (I have no other use for it), I stand corrected, thanks.
No worries. AAO has its own WASM module, which handles writing to and reading from all types of simulator variables, including LVars and HVars. It is probably better not to have too many modules in the sim, especially when they try to do the same thing.