can not register a single function from the device itself
Is “Hardware->Midi devices enabled” switched on?
“Register” where? What happens when you open the “Add Button” dialog with the green “+” and push a button on the X-Touch? Try isolating the XTouch in the “Device” drop down box, to rule out interference from other controllers.
Yes, the Midi devices enabled is checked and as I stated it does show up Hardware Show Midi Devices.
When I Add Button I can pull an event from the drop down and then attempt to assign a X-Touch button to it but it does nothing. Doing the same thing with any of my other peripherals immediately show up in the Assigned button/key window, but nothing I do with the X-Touch registers into the AAO.
I do not see a “Device” drop down box. There is the “Hardware” drop down which has a Device Blacklist but when I click that button it shuts the program down immediately.
I do not see a “Device” drop down box.
The “Device:” Drop Down box on the Add Button dialog - below the box where the incoming inputs are shown.
There is the “Hardware” drop down which has a Device Blacklist but when I click that button it shuts the program down immediately.
What AAO version is this and where did you buy it? That bug has been fixed a while ago.
Purchased from SimMarket on 7/11
Products Ordered:
1 x LORBY-SI - AXIS AND OHS V2 FSX P3D MSFS () = EUR 15.00
Delivery Method Direct Download
Sold by LORBY-SI
Purchased from SimMarket on 7/11
OK, but what does the title bar of the app say what version it is?
2.09 b04-MSFS
OK. I suggest that you send an email to the address on the last page of the manual, including your order number and a screenshot of the “Global” page of the Behringer editor, plus this file:
C:\Users…\AppData\Local\LORBY_SI\LorbyAxisAndOhsMSFS\DeviceBlacklist_MSFS.xml
After that, delete this file, it seems to be broken. If you don’t mind resetting everything back to factory default, delete the entire folder C:\Users…\AppData\Local\LORBY_SI\LorbyAxisAndOhsMSFS\
Though I have to admit that I have never heard of anything like this before. I am completely in the dark about what the problem could be.
Ok, will do. Give me a little time though, I’m between some other pressing items at the moment.
And thank you for your prompt attention.
Make sure XTouch editor is not running when you are using AAO. Actually you don’t even need the editor, works fine with default settings.
I had something similar to this when I first got the x-touch. In my case my headset microphone was conflicting with the midi channel. After I disconnected the usb headphone the device start working on AAO.
However I believe Oliver fix this issue several versions ago.
Well apparently something in the installation was corrupt and after several email exchanges with Oliver I am happy to report that it is working as it should.
Props to Oliver for the quick response and determination to find the problem.
Now the fun begins.
Has anyone identified the variables to control the CHR button (off/on) above the clock, the ATC on/off/standby button (near transponder) and the panel & pedestal Flood light brightness on the FBW A32NX Development version?
I have check the various on-line references with no success, and tried monitoring the variable using the SDK.
I’ve got most of the other key functions working using AAO and the Behringer X-Touch Mini and other controllers.
Would be happy to share info if you need some functions.
Thanks.
CHR button (off/on) above the clock
Code in the animation defintion file (NODE_ID “PUSH_CHRONO_CHR”) suggests
1 (>H:A32NX_CHRONO_TOGGLE, Number)
the ATC on/off/standby button
Again, the code suggests the default simulator variable. But there may be a lot of scripting involved too.
x (>A:TRANSPONDER STATE:1, Enum)
with x being one of
0 = Off
1 = Standby
2 = Test
3 = On
4 = Alt
5 = Ground
pedestal Flood light brightness
I think that it is these scripts
(A:LIGHT POTENTIOMETER:76, Percent) 10 + 100 min 76 (>K:2:LIGHT_POTENTIOMETER_SET)
(A:LIGHT POTENTIOMETER:76, Percent) 10 - 0 max 76 (>K:2:LIGHT_POTENTIOMETER_SET)
panel Flood light brightness
same method, different potentiometer
(A:LIGHT POTENTIOMETER:85, Percent) 10 + 100 min 85 (>K:2:LIGHT_POTENTIOMETER_SET)
(A:LIGHT POTENTIOMETER:85, Percent) 10 - 0 max 85 (>K:2:LIGHT_POTENTIOMETER_SET)
Be mindful, this is off the top of my head, not really tested. I am looking at the FBW code, that the above seems to be what it says.
Thanks so much!
Will give them a try and report back.
I was able to get the CHR working, but no luck with the other variables. Admittedly I have very limited experience with script writing, so I’m sure it’s something on my end.
Will continue experimenting, greatly appreciate the help though.
Thanks again!
The potentiometers work, I’ve just tested them.
The transponder knob doesn’t work, or only partially. We can switch between STBY and ON, but not to AUTO. The reason is, that in code Asobo and FBW are using a variable with an “I:” prefix. It doesn’t look like those can be accessed from the outside, sorry. You could simulate what AUTO does with a script, but not turn the knob visually.
Edit: that being said - I was able to get the transponder knob to work from the outside, but that procedure is not for the faint of heart. I changed the related “I:” variables into plain LVars in the FBW code and then replicated their scripts in AAO.
As I suspected, it was my script writing ability that messed me up.
Using your example I was able to get the potents to work.
Thanks so much for a great product and helpful support!
thx alot for the impit, i finally got it work antoether way:
Is there a place to go to find already made templates? I would like a DC-6 template for the Honeycomb Bravo that has gyro pilot functions setup.
Thanks in advance!
Hmmm… that’s would be nice, but right now you have to search at different places.
I would start with PMDG DC-6 profile for StreamDeck XL (for LORBYs AAO SD plugin) » Microsoft Flight Simulator , just using the xml file and add the assignment for your controller.
Hope that helps
Norbert
