ParadiseFlight

Thanks for your replies. I discovered it was my aircraft automated script, for setting LEDs, specifically for that encoder, causing the problem. Turns out the behavior is also fully explained by Funatic in the post below, about the negative consequences of using the same channel for button assignment and changing LEDs. For that encoder I was using channel 11 instead of Global channel 1 because I wanted to also be able to control encoder LEDs on layer B. And it works for the LEDs, but causes the strange behavior noted above. So controlling encoder LEDs on layer B requires a different strategy, which I'm not going to bother doing at this point. There is a free framework of scripts on flightsim.to that enables this, but I'm not going to reprogram everything now that 99% of what I have is working as desired. Thanks all for the assistance.

Thanks for the reply. It happens while assigning and while using. I can get it to assign Left and Right if I move it one click yes, which is how I got it assigned originally. The other encoders don't have this same sensitivity. I did try a factory reset using the X-Touch editor a couple weeks ago. I loaded the default bin files. I do not use it in MC mode. It's quite strange. Like I said the other encoders and buttons behave (assign and work) as normal.

AAO is reading left and right when turning my 8th encoder on my X-Touch Mini in one direction. When setting up an assignment, it is bouncing back and forth between CHN: 11 EVT: 3008 TURN_RIGHT and TURN_LEFT as I turn it one direction. Meaning when I turn it left, it randomly detects left and right while turning it. If I turn it right, same thing. I thought maybe the encoder was bad. Tried cleaning it first, but no change. Then I went ahead and bought a new encoder on eBay and soldered it on, but the behavior is the same. I just downloaded MIDI-OX now to test it. When I watch the console, the data coming from the encoder shows as expected. It is showing data only from the direction I'm turning it, not back and forth. Why would AAO have a problem reading this encoder? Is there some way to get debug output from AAO to see the raw data from my device?

I had to do this just now as well in my first time trying the XT with 2024.

Oh wonderful! This was my main concern. I was misinterpreting what internal vs external meant in this context. Yes exactly. I had released a template with scripts a while ago, and now with more experience how this works I decided I should use unique names before exporting my improvements. Now I can proceed. Thanks!

There are times I would like to rename a script group, either because the current name is too generic, or for other optimization reasons. For example, I had created a My Scripts group, but I want to now export it as a template with scripts, and I would rather change that group name to something more identifiable and so it does not affect anyone else who might have a My Scripts group. When I try to rename the group, it says all external references to the scripts in the group will be invalidated. So I have avoided doing the rename. It would be great to have a new group name propagated to any existing templates and configurations. Is this something that could be implemented?

I changed my button mappings for the Fenix A320 for the AP knobs, to use the MSFS input events, so the knobs will now move on screen. My selections save fine when doing the change button assignment, but when I come back later to view one of them, as if I'm going to edit it, the change button assignment window has switched to MAN, showing K: and nothing in the entry. If I click SEL, it reverts back to showing the IE I had saved for the button. It's only a display problem and only seems to happen with IEs. I haven't noticed this for my other buttons assigned to scripts.