Overview
The „X-Touch Gauge for Axis and Ohs“ is a framework, that helps you programming the Behringer X-Touch Mini Midi Controller to use as an input device for Microsoft Flight Simulator 2020 using AAO (“Axis and Ohs”) Software.
It does NOT deliver direct-to-use configurations for airplanes or helicopters.
This framework offers:
- Easy handling of button and rotary assignment
- Simple integration of “Shift” key for “overloading” single buttons or rotaries with a second or modified action
- Support for unlimited number of layers and aircrafts
- Easy interface to control X-Touch Mini LEDs
- Optional mirroring of X-Touch Mini device as “Axis and Ohs” Desktop or Web FIP (perfect for VR flying!) or if using multiple layers (labels shown are depending on the selected layer)
- Dynamic labels on X-Touch Gauge (depending on Shift Button status, even possible to dynamically modify labels depending on conditions)
- Pre-Touch functionality that suppresses first button push to help VR users to identify if proper button has been pressed
- Testing “X-Touch Mini Look & Feel” before actually buying it by clicking buttons and rotaries in the gauge with the mouse
The framework configuration is stored in simple text files, one file per layer and aircraft. It uses standard RPN script syntax for event triggers or LED control, so “programming” a layer means editing a text file and filling in proper RPN scripts.
Requirements
This framework requires “Axis and Ohs” software version 2.32 b34 or newer (see https://axisandohs.weebly.com). “Axis and Ohs” has to be purchased separately.
For programming the framework you do need at least basic knowledge of RPN Scripting, MSFS events and variables.
Experience in how to assign buttons to trigger events in MSFS using “Axis and Ohs” is highly recommended before using this framework!
Files
There is one zip file "XTouchGauge_vx.zip" containing the X-Touch Mini Gauge code. I have added a second file (XTouchGauge_Sample_FBWA320.zip) containing some configuration files for FBW A320 as examples on how to use the Gauge. The focus of this procjet is the X-Touch Mini Gauge, NOT the FBW A320 configuration!
XTouch "Script Group"
Do NOT store or modify any scripts in the "XTouch" Scripts Group as this will be deleted on every update!
Fresh installation instructions
There are detailled installation instructions in the attached PDF file. Please read this documentation first!
Update installation instructions
Update procedure changed to allow updating from any older version to current version. See chapter "Installation of an Update" in the documentation.
V1.3 Update: Please delete the files XTouchMini_L.xml, XTouchMini_M.xml, XTouchMini_S.xml and XTouchMini_XS.xml in the LorbyAxisAndOhs Files\UserGauges directory and the folder XTouchGauge in the LorbyAxisAndOhs Files\UserGauges\1024 directory prior to updating to v1.3. If you miss that the gauge will show up twice in the gauge selection drop down and you will not be able to distinguish between v1.2 and v1.3.
Manual Bug Fix for v1.0 users
Unfortunately in the v1.0 release I forgot to remove the FBW Initialization script from the template file. This initialization script will now be applied all the time for every aircraft you apply the template. That does not make sense and might lead to side effects.
Updating to v1.2 following the new update procedure will remove this script from the template. However, unfortunately you have to remove it manually from all your aircrafts you started to configure with this gauge. To do so load every affected aircraft in MSFS, then open Scripting/Aircraft automated scripts in AAO, select the "FBW_A320-INIT_XTouch_AUTO" script and click on "Remove". Sorry for the circumstances.
Users that started with 1.1 or newer are NOT affected by this bug!
New tool "X-Touch Mini Gauge Layer Builder"
Check out X-Touch Mini Gauge Layer Builder at http://www.funatic.de/XTMGLB/alpha.html
Still very early Alpha release, not all features implemented. No intensive testing done yet. However, I wanted to share with you as I think this will help in creating the layer files, even at this alpha release level!
Feedback and Bug reports really appreciated!
Video series on how to setup and use
Youtuber "FlightSim and other stuff" started recording a series on how to set up and configure this X-Touch Mini Gauge and allowed me to link to his YT channel. The series on this is starting with the videos released on 2022-08-19 and later. Check out his videos if you prefer video guidance!
Regular Live Q&A Sunday evening in FlightSim and other stuff Discord. See announcements channel.
SU 12 VR issue
Since SU12 the In-Game-Panel in VR is way too small. Asobo has identified this as a bug - we need to wait until fixed.
However, Lorby released a workaround:
- Stop MSFS
- Download new In-Game-Panel from Downloads - AXIS AND OHS
- Delete lorbysi-content-fippanel from community folder
- Install downloaded In-Game-Panel in community folder
- Add 3.0 (>L:AAO_PANEL_ZOOM, Number) in the second line of your Layer file, just below :GaugeText
- Start Sim and enjoy In-Game-Panel in VR again
This zoom does have an impact on the In-Game-Panel in 2D as well (but not on the Desktop FIP!). If you are using AAO In-Game-Panel in VR as well as in 2D consider changing the Zoom value using a script assigned to a button....
2 months ago
2 months ago
Funatic
bcip
The entire installation went well except for chapter 3.4.
I cannot find the XTouch Mini Gauge line in the drop down box.
I think the gauge files are not in the right place?
Thank you for your reply.
6 months ago
5 months ago
Funatic
LeFouVolant
Hi Thomas, it's Trevor. I sent you some messages on Discord (DMs I think. Are you still using Discord?
Regards, Trevor.
10 months ago
teebeejay
How can i get an activated button to flash instead of just on ...
This doesnt work (its flashing all the time weather activated or not)
(L:I_FCU_EFIS1_FD, number) 641 9 @XTouch_Macro_LED_Value
11 months ago
That's easy... :-)
(L:I_FCU_EFIS1_FD, number) 640 + 9 @XTouch_Macro_LED_Value
For more complex ones you could do something like
1 641 1281 0 4 (L:Var) case 9 @XTouch_Macro_LED_Value
(L:Var) 0 => off
(L:Var) 1 => Blink Slow
(L:Var) 2 => Blink Fast
(L:Var) 3 => on
11 months ago
Funatic
EisernUnion
awesome. thanks a lot for sharing this! together with the layer builder it helps a lot!
1 years ago
flusiflo
@Funatic: you, my friend, are a genius. Thanks so much for your efforts. The framework alone is amazing but then you also added the layer builder and the in-game panel which takes it to another level. It's actually beautiful how you have this all working together. Wow. It took me a couple days to figure how everything worked together but I got it now and I'm impressed. Your hard work is appreciated.
Question: the in-game panel flashes off-and-on every second or two. It's really distracting. Does anyone know how to prevent the flashing?
1 years ago
Hi @Mayhem6633,
I never had this issue - but on discord I had one user reporting same issue. He also did have a red border on the web fip. He figured out that the AAO web service was not running. He checked the "Enable web service", restarted AAO and all ok.
Does this work for you, too?
1 years ago
Funatic
Mayhem6633
Hi
Tried to setup Fenix with x-touch and followed the instructions but failed.
The x-touch does not respond in FS Fenix accordingly.
AAO Version 22.70 b37
XTouch MIDI Out ID 5
Start a flight with Fenixc A320 at parking gate
The x-touch does not react in the Sim.
Flightdeck for Fenix is working.
What steps do I need to verify this solution?
Thanks a lot.
1 years ago
First of all: open the INIT_XTouch_Auto Script you have created during setup in the RPN Scripts editor. Locate the line containing the MidiDeviceID and change the value to 5 (default is 3). Click on Update / Close and try again.
Let me know if this already fixed the issue.
1 years ago
Funatic
erathost
hi. how do i need to setup the x-touch mini within x-touch-editor? thanks
1 years ago
Hi flusiflo,
the gauge uses default XTouch values - so there should be no need to modify anythin in the XTouch Editor. However, if you changed something, then you can either bring it back to default values (I would prefer that) or change appropriate settings in the INIT_XTouch_AUTO Script.
Default in XTouch Editor means Global Channel 1.
In AAO it should be listed with Midi Out ID 3 in Hardware/Show Midi Devices tab.
First criteria to check: after setting up everything, load a plane and then check if the XTouch switches to MC mode automatically. If not, then do not continue, there is something not working properly. Come back here and report or contact me on discord (Funatic#9878)
1 years ago
Funatic
flusiflo
Is there any option to activate led's without custom settings?
After installation, my xtouch mini does not display any led indication. I checked ports and id, while nothing I did helped.In gauge, all light indications are displayed, but not on xtouch.
It seems that midi signals do not reach x touch.
1 years ago
Hi Lisliv,
did you cross check same points I mentioned in the discussion with Liner707?
1 years ago
Funatic
lisliv
Hi Funatic,
I have everything working except for the button lights on the XTouch Mini. I've tried everything I can think of, but the lights don't come on.
I'm using the APU Master Switch in the FBW A32NX as the test light (I've also tried the Beacon switch) and want button 22's light to come on once the APU Master Switch is activated, i.e shows as the blue 'On' in the flight deck. The Master switch comes on in the flight deck when I press button 22 on the XTouch, but the button's light doesn't come on. The code I have in the 'Button LED values' section is this:-
(L:A32NX_OVHD_APU_MASTER_SW_PB_IS_ON, number) 1 == 22 @XTouch_Macro_LED_Value
According to the doco, the A32NX_OVHD_APU etc variable is defined as a number with values 0 or 1.
The XTouch is in MC Mode (the indicator light is on) and all defined rotaries and buttons function correctly with the aircraft.
What am I doing wrong?
Thanks!
1 years ago
Hello 707Liner,
your code looks absolutely fine.
Please run the following steps to identify the issue:
Regards,
Funatic
1 years ago
Funatic
707Liner
I can get the virtual xtouch to work fine with all the button labels etc. Cockpit is also responsive. However my real xtouch isn't doing anything. It's not syncing.
1 years ago
Hi Jingle,
please check:
If you still have problems, please join "Flight Sim and other Stuff" discord (link is on his Youtube "About", I will not put in the link here as this is not my discord). I am there quite often and I can try to assist you interactively.
Regards,
Funatic
1 years ago
Funatic
jingle
Would it be possible to have two xtouch minis each with their own desktop FIP?
2 years ago
Hi,
as clarified in private message this would be technically possible but is not covered in current gauge installation.
2 years ago
Funatic
skydon
Hello Funatic,
I have successfully installed all scripts/templates for PMDG 737 in AAO latest release as well as their InGamePanel in my Community folder.
All assigned rotarys and buttons do work great now via X-Touch Mini but I can not find out how to get the X-touch Mini be seen in the AAO InGamePanel.
I am pretty sure I have missed it somewhere in AAO as I am now 81 years+ 😊 so need some advise.
I only fly in VR so getting X-Touch settings shown in VR would be a great help.
Best from Sweden,
Bjorn
2 years ago
Hi Bjorn,
please check this video: https://youtu.be/7w0fH60Nt3I. It is explaining all steps that need to be done for the setup.
If you still have some problems, please join his discord - you will find me there so I can provide proper support.
Regards,
Thomas
2 years ago
Funatic
saabpilot
Hi, AAO just reports an error in the xml file when trying to import the template. (2184,9)
2 years ago
Can you please check your AAO version?
2 years ago
Funatic
snowyuk
Can the font size of the text be changed?
2 years ago
No, unfortunately this is not possible as there is no way to control Size, Style or color of text from AAO.
2 years ago
Funatic
funflyer68