Hello. I was using AAO with XTouch Mini in MSFS, with planes like FlyByWire A320, WorkingTitle Cessna CJ4, and everything was going perfect. Until last week that I got a new PC and a tried to do the same, but now it doesn't work.

I installed the X-Touch editor and set to Standard mode, Encoders and Buttons to CC Type and CC## NO, saved and dumped layers A and B. As shown at some tutorials and as i did when I first did it.

I installed AAO last version and set MIDI devices enabled. 

I Installed Net 4.8 Runtime ("allready installed in this PC" said when I did it) and the VC++ Redist 2019 ("Visual Studio 2015, 2017, 2019, and 2022" version I found).

I imported some templates, like a one for the FlyByWire A320 that was working perfectly in my old PC.

I start MSFS and go to an airport with v. g. the FlyByWire A320 and then I start AAO.

AAO detects the plane (it shows the name).

But nothing happens if I turn encoders, like baro or speed, or buttons like FD or LS.

However, something happens if I push some keys at plane panel, FD or LS: lights change (on-off-on...) at X-Touch.

So, it seems that the communication between X-Touch, AOO and plane is working but not fine.

I don't know what could have happened and how could I fix it. I'm not sure if this actually has to do with AOO support; if not, I understand and apologize.

Thank you for your attention.

If profiles are only partially working with MSFS planes on a new PC build, double check that the package "lorbysi-content-hooks" is present and active in your "Community" folder

Also, make sure that the profiles that you install are actually compatible to the current version of the aircraft. Everything is progressing all the time with this sim...

Thank you very much for your support. Profiles are not partially working, they are not working at all (just two keys -FD or LS at plane panel- that are detected as lights change (on-off-on...) at X-Touch. Nothing more at other planes tried. And "lorbysi-content-hooks" is present in my "Community" folder (I'm not sure if it contains what is necessary).

I feel a little lost because I installed the templates from .templ files, in the past, and they worked perfectly until the last moment I used them in my old PC last week. Now I can see that scripts are installed mostly from .txt files in Documents folder and templates are created from those scrips at AAO.

I don't know... It doesn't work for me anymore and yet it worked last week, same planes, same templates. I feel I'm doing something wrong that I'm not able to realize.

Maybe will try a fresh install of everything. I don't know if there are any series of recommended tutorials to start from the beginning.

Thank you!

 

 

2 hours ago, barbaryto said:

Now I can see that scripts are installed mostly from .txt files in Documents folder and templates are created from those scrips at AAO.

I have no idea what that means, sorry.

Nothing whatsoever has changed in AAO regaring template and script files.

A package that is intended for the X-Touch must contain a template - that is the only way that this works. That template file must be imported using the "Templates->Import template" dialog, and then applied to your current aircraft when you are sitting in the cockpit (after that you see all the button definitions on the main dialog of AAO) And you may have to adjust the MIDI IN ID of your device in all those button assignments, if it is different from what the author of that template was using. That is why AAO may ask you to confirm the button definitions while the template is imported. If the package needs scripts too, then those will be in a separate script file that must be imported using the "Scripting->Import scripts" dialog.

You should also reset the Behringer to factory defaults. I have no idea why anybody would start messing with the hardware setup - that is definitely not how this is intended to be used as seem from AAO.

Quote from the Internet regarding factory reset of the Behringer X-Touch Mini:

Quote

1. Unplug the device.
2. Press and hold both LAYER buttons, A and B, on the right side of the device.
3. Plug-in the device while still keeping down the two layer buttons.
4. Keep holding down the buttons for a few seconds, the buttons will flash a few times.
5. When only the layer A button is illuminated, the reset is complete. Release the buttons.

And here is the procedure to take it out of MC mode:

Quote

unplug the USB cable. Then insert the cable again while pressing the lower left button.

 

Edited March 21, 20233 yr by Lorby_SI

On 3/21/2023 at 6:49 PM, Lorby_SI said:

You should also reset the Behringer to factory defaults. I have no idea why anybody would start messing with the hardware setup - that is definitely not how this is intended to be used as seem from AAO.

You were right! I reseted the Behringer to factory, by following your instructions (no tutorials about hardware setup this time) and it worked!

Thanks a lot for your always valuable support. You are the best.