Many thanks but unfortunately nothing worked, so i had another look at the community folder and realised that sometime back i had copied it to the root of the FS folder and copied the WASM module there, rather than the packages/community folder. Once i copied it in to the correct community folder everything worked. Got my buttons and encoders assigned now 
Bless you for also posting a key with your configuration.
A bit of a noob since I just started using this device, got it working with two methods, but wanted to switch over to the x-touch-mini-fs2020.exe method fully.
Can you school me a bit as to where to paste the information you provided?
I assume is just going to go into a python script from the original author? I have no idea which oneâŠ
Hi guys, I was using the Custom FBW mod for a320, and the latest update to that yesterday somehow broke the x-touch mini integration.
Altitude selector works, but speed and heading are not working.
Did anyone also encounter this problem? Any idea how to fix?
Sure, I can try.
Once you install the software you should have âX-Touch-Mini-FS2020â somewhere. Click into it and you will see âConfigurationsâ folder with *.json files:
So you can post my config into âconfig_default.jsonâ, or you can create a new config file - âconfig_AIRPLANE.jsonâ, where you replace AIRPLANE with whatever you are writing the config for.
Then you edit âconfig.jsonâ and add:
{
"aircraft_contains": "AIRPLANE",
"file": "config_AIRPLANE.json"
},
As an example:
{
"aircraft_contains": "M20R",
"file": "config_M20R.json"
},
Which just means that if the software detects that MSFS is loading M20R airplane, the software will load config_M20R.json.
Btw. this is my latest config: M20R - Pastebin.com
3 Likes
Thank you so much for that detail. I wasnât sure how to get the executable to read different ones.
Can I ask about where you got a key of sorts to know what commands exist? Ie: how do you know the names of all the recognized functions you add to the assignments?
Sorry for the late reply, been less active lately.
You can find all the events in âconfig.schema.jsonâ file and here.
All this info has already been posted in this thread, but I appreciate that itâs not the easiest task to find it
I have exactly the same problem?
Hi,
I think the new FBW custom version doesnât use the default Simvar events and simvars for MSFS 2020 anymore. Check here the new additions to the custom FBW variables:
https://github.com/flybywiresim/a32nx/blob/autopilot/docs/a320-events.md
https://github.com/flybywiresim/a32nx/blob/autopilot/docs/a320-simvars.md
So I think we should update the button config with the correct simvars/events. Iâm using the X-Touch-Mini-FS2020 script, so I should change them in its config file.
Iâm currently on a break from msfs2020 though, Iâll wait for a while until these big changes are ironed out, and then Iâll try to customise my button layout in the future. Iâll appreciate greatly if anyone has done it already and willing to share their new configs
1 Like
Newbie here as far as Xtouch is concerned. So after several weeks of waiting, I managed to start setting up my Behringer yesterday. Spad.next did its magic and I was able to configure several aircraft functions with very little effort. Didnât have to go through xmini2vjoypy or the other relatively exotic solutions that are out there.
It was a very plug and play process as Windows recognized the device and downloaded drivers automatically, then spad.next also acknowledged the Xtouch and let me assign keys to events/values/lvars without too much trouble. Using JF P28R as an example, I had nav/panel/dome lights and various other buttons configured within an hour or so (most of the other basic stuff goes to Honeycomb Alpha/Bravo anyway).
However what troubled me is that I couldnât get the LVARs for GNS530 mod and also 430 default, as whenever I changed anything in the GPS panels I wouldnât see any values registered to spad.next so I couldnât map anything to Behringer. Obviously thatâs an issue irrelevant to the current topic, but I was wondering if anyone has seen anything like that when setting up Behringer to handle G1000 or GNS530/430 (or if they have done this successfully so that I know it can be done).
edit: found the solution I was after, apparently GPS shortcuts need to be set as events in spad.next which enable a different list of H:events which I hadnât seen before. These arenât automatically exposed by MSFS so they have to be added manually by the appâs developer. There I found what I was looking for and I made good use of my Xtouch, it can now control pretty much everything in GNS530. Iâm tempted to buy a second unit if I ever move to airliners (ie. if CTDs ever stop).
1 Like
For the G1000 I use Garmin G1000 Template for Axis And Ohs and X-Touch Mini » Microsoft Flight Simulator but not with spad.next but with AAO. Maybe you can make it use with your tool.
Happy flying out of Germany
2 Likes
i use your settings for as530 and runs very well fo my 172 skyhawk
I wish the same for the g1000 on 172 G1000 but i canât find themâŠ
{
âindexâ: 9,
âevent_upâ: { âeventâ: âMobiFlight.AS530_RightLargeKnob_Rightâ, âtypeâ: âmanualâ, âvalueâ: 1 },
âevent_downâ: { âeventâ: âMobiFlight.AS530_RightLargeKnob_Leftâ, âtypeâ: âmanualâ, âvalueâ: 1 },
âalternate_event_upâ: { âeventâ: âMobiFlight.AS530_RightSmallKnob_Rightâ, âtypeâ: âmanualâ, âvalueâ: 1 },
âalternate_event_downâ: { âeventâ: âMobiFlight.AS530_RightSmallKnob_Leftâ, âtypeâ: âmanualâ, âvalueâ: 1 },
âevent_short_pressâ: â{alternate}â,
âevent_long_pressâ: { âeventâ: âMobiFlight.AS530_RightSmallKnob_Pushâ, âtypeâ: âmanualâ, âvalueâ: 1 }
},
{
âindexâ: 10,
âevent_upâ: { âeventâ: âMobiFlight.AS530_RNG_Zoomâ, âtypeâ: âmanualâ, âvalueâ: 1 },
âevent_downâ: { âeventâ: âMobiFlight.AS530_RNG_Dezoomâ, âtypeâ: âmanualâ, âvalueâ: 1 }
},
1 Like
You can find g1000 (and others) events here: MobiFlight Event Module SimConnect Event IDs - Pastebin.com
2 Likes
Grazie mille 
Hi, if anyone could help in updating to the correct simvar for x-touch mini in order to change the SPD setting?
current =
âevent_upâ: âAP_SPD_VAR_INCâ,
âevent_downâ: âAP_SPD_VAR_DECâ,
From the FBW docs, I think this is the one to use now -
'A320_Neo_FCU_SPEED_SET_DATA â
but not sure how to enter that in to the config?
Just got my xtouch set up using X-Touch-Mini-FS2020 !
Also 3d printed some knobs so they feel different (VR flying only here)
Thingiverse link for knobs: X-Touch Mini knobs for Flight Simulators by smitty_fpv - Thingiverse
5 Likes
Been playing with this somewhat, I made it do something cool!
change the generic function file âhdg-lock-sync.jinja2â to this:
{% set encoder_index = data.get_global_variable('HEADING_ENC_IDX') %}
{% set bug = (data.get_simvar_value('AUTOPILOT_HEADING_LOCK_DIR')) | round | int %}
{% set heading = ((data.get_simvar_value('HEADING_INDICATOR') * 180 / 3.1415)) | round |int %}
{% set knob = (((bug - heading) / 27) + 7) | round %}
{% if knob < 0 %}
{% set knobpos = knob + 14 %}
{% elif knob > 13 %}
{% set knobpos = knob - 14 %}
{% else %}
{% set knobpos = knob %}
{% endif %}
{{ data.set_encoder_led_value(encoder_index, knobpos) }}
and add the simvar trigger to âconfig_default.jsonâ:
{
"trigger_type": "condition-file",
"simvar": "HEADING_INDICATOR",
"condition": "Functions/Generic/hdg-lock-sync.jinja2"
},
and the encoder lights will follow the heading bug position as you fly around!
enjoy
3 Likes
Hereâs a short demo of the moving hdg & alt bugs
8 Likes
I was instantly sold when I saw this this evening, and ordered 1 unit as well. Do you have a good use of the slider as well? And do you use both A and B layers?
I have it mapped to spoilers but i hardly ever fly jets or airliners. I only need layer A.
Any suggestions to get rid of the texts/markings that are printed on the cover? I would like to clean it up to make it more look like an AP panel or something.