PrivatePilotC172

Yes I was doing something wrong. But not AAO at all! I have checked and double checked all the scripts both on the AAO (RPN) side and on the XTouch Gauge side and all were correct with the functions I was calling in my script library. The reason the Funatic/Other scripts were not calling was frankly ridiculous. I was in the wrong A320 Neo. I have been using the A320 Neo V2 mistakenly believing this the the FBW version. This all relates back to moving my community/official directories (and their content) to a new SSD (F:Drive). For some reason four folders remained and the recently installed DEV edition of FBW320 was one of them. Its all working now. I have been able to blend scripts from Funatic and others to extend the XTouch template to 8 pages; when I have this all working well I will share it. The ONLY issue I have now is with the XTouch Gauge resolution in VR. Its too small. I have seen the workaround (adding a 3X Zoom) to the each X-Touch Gauge screen but this has not worked for me yet. Thanks for all your help Lorby and thanks for telling me I was doing something wrong. Better to figure this stuff out. I now have 5 GA aircraft, A Hawk T1, A TBM930, and the FBWA320 working as intended with AAO/XTouch. I can now practice IFR procedures with the degree of immersion I need. Now to figure out how to achieve Reverse Thrust with the Trustmaster Warthog Quadrant Detent. God help me! I guess this cycle may all start again when I upgrade to MSFS 2024 😉

I just wanted to double check. That when you import scripts (like the Streamdeck A32NX scripts that support the streamdeck profiles), that, as long as they are visible in the script editor, you should be able to call them without any additional steps. I have scripts visible that I have imported in their own managed groups and I have attempted to call them with <Group Name>-<Script Name> with a K> Assignment without success for the A320 FCU functions. These include Funatics, Silver Surfer and others.

I tried the axis and the script options for ND_MODE and neither are responding. I have been going around in circles with this. I have all my other GA aircraft working well with AAO/XTouch. Its just the A320 I am having issues with. Standard functions like (Barometer aka KOHLSMAN) are working as direct mappings to X-touch dials or as scripts. No issue. FCU specific stuff is simply not working at all with L: assignments or downloaded scripts (as you suggested - I have tried 3 or 4 different ones). For example if we look at ND Mode: As an axis, if I assign: L:A32NX_EFIS_L_ND_MODE, Number where it says 'Enter Variable' NOTHING HAPPENS. If instead I directly select this event to the axis: AIRLINER_ND_MAP_MODE_CPT! 1 (>IE:) THE ROTARY WORKS! I want to use the more comprehensive X-Touch Gauge scripts out there but they all use L: assignments to perform their functions and these are not working for me at present. Any help appreciated as this is driving me mad! If I can simply get the mode, range, speed and altitude working, I am sure I can do all the rest of the functions using modified scripts if necessary.

Hi, I have about 70% of the FBW A32NX FCU now working with the X-Touch Dials and button assignments. The 'Mode' and 'Range' dials on the A320 (I am using the flybywire version) are unique in that they do not have increment/decrement triggers but are an incremental number from 1 to 5 I believe. How do I script this against each rotary increment and decrement assignment using RPN if, else statements? The script for these buttons looks like this: :Rotary_2_Left 0 (>AIRLINER_ND_MAP_MODE_CPT) (END) :Rotary_2_Right 1 (>AIRLINER_ND_MAP_MODE_CPT) (END) :Rotary_3_Left 0 (>AIRLINER_ND_MAP_RANGE_CPT) (END) :Rotary_3_Right 1 (>AIRLINER_ND_MAP_RANGE_CPT) (END) Instead of 0 for decrement, I want it to be the value of the mode/range dial minus 1 unless the dial is at 0. Instead of 1 for increment, I want it to be the value of the mode/range dial plus 1 unless the dial is at 5. I have found scripts that do this already but I am trying to get this working inside my own templates and scripts which I want to develop further over time.

You are absolutely correct. I have this working now. C152, C172 and TBM-930 all 90% configured and working with a touch and my controls. Thanks!

AAO is working perfectly Lorby. It is detecting all the events. I think the complexity with the Warthog Throttle switches is some of them are 3-state. They go on, middle and off. So, might need a script to handle this. Button, the on/off switches are seen as different buttons. So is the reverse detent, its not an axis, its a button (so should be able to activate reverse thrust hold events, I hope!

Please IGNORE this post. I can see the switches it was a USB issue.

I have since found out that FSUIPC is able to see these 'two-way switches' so hope AAO can do the same

Hi All, I am using the A10 Throttle Quadrant and Joystick from Thrustmaster with MSFS2020. Most of the buttons are 'momentary' and therefore are picked up by MSFS or of course AAO. There are a number of switches on this throttle (some 2-way and some 3-way) which do not appear to be momentary. They are not detected by MSFS/AAO. Has anybody managed to configure the 2-way switches with AAO? I appreciate there is probably a prior step to this (maybe using their target software) but I wanted to reach out to this community to see if anybody has managed this successfully Also, has anybody managed to configure the reverse throttle buttons (beyond the standard detent) with AAO to effect reverse throttle? Many Thanks for your help (or pointing me somewhere else if this is not the right forum).

Hi, Ah , Reverse Polish yes I have heard of that. I have my profile working correctly with a C152 and a C172 with the X-touch dials and buttons all working well now. No idea what the spinning issue was but since a reboot it has disappeared. Thanks for getting me going Lorby!

I have got all the autopilot functions of the TBM 930 (buttons and rotaries) working using pure AAO button assignments and, by assigning 0's and 1's to each decrement and increment event within AAO itself; not successful using downloaded templates/OfA The only issue now is that the rotary has to be turned really slowly to register the increment. If I 'spin' the rotary too fast is goes a bit crazy. But getting closer. As to getting the basic layer file and Funatics scripts working with the x-touch; Not so lucky at this point as it seems to be configured for different midi channels etc. I reset the X-touch mini to defaults and when these basic layer templates were applied they had different numbers/channels for the buttons and rotaries. Can try this again later. Is there a good guide somewhere to writing your own RPN scripts?

Hi, so I have about 70% of the TBM-930 autopilot working with the x-touch and AAO. The problems are the dials. I can find the event to increment using a midi rotary but NOT to decrement. Example. To set the heading on the G3000 autopilot in the TBM-930, the simulator event in AAO shows as: [AUTOPILOT_HEADING]: 0 (>IE:AUTOPILOT_Heading) In AAO, if I search under MSFS Input Events, I find: AUTOPILOT_Heading|1 if I assign this to a rotary increment (Turn Right) IT WORKS! BUT. i see no way to do a decrement on the same rotary? Am I missing something. Other functions such as the heading bug on the G3000 have an increment and decrement event which works perfectly. My question is how do I assign the rotary dials to heading, course, speed and altitude for increments and decrement events? Thanks in advance!

Thanks Lorby for the detail in your response. I have definitely 'messed' with the X-touch editor so will revert to default and try again. Will report back with any 'event assignments' I cannot find to the community with screenshots as suggested. Once I have completely mapped one aircraft, I am sure I will be OK. AAO is a great investment just for the primary flight axis and trim (especially with the option to create negative curves); everything feels better. I just need one of those new force-feedback yokes to complete the immersion 😉

Thanks for the response. I am a in software in my professional life but find this whole domain (or mapping controllers) a bit bewildering at first so bear with me 🙂 I mean't HTML Variables and MSFS Input Events. I fly the TBM 930 and the G1000 C172 (hope to learn the A320 Neo next) and a C172 in real-life too 😉 I purchased AAO specifically to improve the axis and trim activities (which is much more realistic and controllable now - especially trim) and, so I can use the X-Touch MIDI controller for the purposes of autopilot and NAV/COM control. On the TBM 930, I am simply trying to control the autopilot panel in the centre top of the cockpit. I have managed to get the buttons to work (for switching on AP, NAV, ALT, HEADING modes). With the rotary dials on the X-Touch, I am trying to create Increments and Decrements with the Heading, Alt, Speed dials themselves unsuccessfully so far. 2 Problems 1) I can only seem to find INC events in AAO for the autopilot rotary dials (Maybe the stock TBM930 doesn't expose every event? Not sure) 2) The Rotary switches on the X-Touch are NOT being detected in both directions. I can't always detect a 'turn right' event with this midi controller. When I setup the X-touch, I assigned a unique CC number to every button and rotary. This appears to be working OK as AAO is seeing most of these events; it seems to be INC/DEC of the rotary where I have issues. This may be an issue with how I have setup the buttons/rotaries in the X-touch Editor software. Not sure! When I was talking about the 'virtual instruments' before I meant this Gauge below. X-Touch Mini Gauge for use with AAO (Axis and Ohs) for Microsoft Flight Simulator | MSFS Apologies for the confusion and thanks for your help and the great product which I know once I have it working well (per aircraft) will make a huge difference to my IFR immersion in VR in MSFS 2020!

I have this working. It was because I was using HTML variable assignments within the necessary lorby hooks in place in the community folder. It worked with direct button assignments but not with variables. The 'virtual instrument' I was referring to, is a visual popup of the X-Touch panel (like an AAO Virtual instrument) which I intend to use in VR as a 'button template'. Apologies for the confusion.