![]()
I can’t say I know all the in’s and out’s of programming this software but with regards to the device ID’s and swapping templates from one to the other it would be great if they can be swapped regardless of ID’s being changed. Thanks again but I do hope you will consider improving the handling of multiple of the same devices, at least the X-Touch minis so all this can be handled more easily. #Xtouch mini osculator to atem midi template how toThanks for the reply, I had already transferred over one by one the assignments, and I’ve just now figured out how to edit the LED script to make it work by replacing all the MIDI: statements from 3 to 5 instead. Both of these LED scripts have then to be run as Aircraft Automated Scripts. You need to find those and use the RPN script editor to replace the MIDI device ID with the OUT ID of the device where you want those LEDs to light up.ģ. On the output side, there should be a script that controls the LEDs for each template. If you want to make a template of your own, use an empty config, apply the downloaded template, make the changes, then save as a new template.Ģ. On the input side, after applying the template(s) to an aircraft config, reassign every button and encoder to the device where you want it (doubleclick, turn or press, apply). The template that you've downloaded was made for a local device that has MIDI IDs (IN and OUT) that are different from yours. These IDs are unique for each device attached to the PC, they can change with no warning and they are different on every computer. So, is there another way to do this that keeps everything from the template intact but on the X-Touch mini of my choice? I've already tried the channel priority option, that was no help, seems like I need a way to change the device ID perhaps?Įach XT has an IN and an OUT ID. I really wish there was a option that just allowed you to swap everything from one Xtouch mini to the other in one click and I'm surprised and disappointed that's not available really. So it seems in the process it lost the scripting for the lights. I've tried the Reassign controls in the current config option and managed to transfer the assignments to the X-Touch I want but unfortunately the button lights do not work any more, they would switch on if that item was on in the aircraft but not now. ![]() I've imported a template for the Fenix A320 which I want to go the horizontal one but it's going to the vertically mounted one, the only way I can get it to work is unplugging the vertical one before starting Axis and Oh's but I do not want to lose the functionally of the second unit. Most of the stuff needed before aircraft is moving are in Layer B, and after all preparations are done and you are ready to taxi only Layer A is needed.Īll button LEDs are working correctly.Hey there, I have two X-Touch minis, one in a horizontal position and one vertical. ![]() Long pressing Cabin call button is T/O Config button, not mentioned in overlay. LDG Lights: Short click: Turns LDG lights ON and OFF, Long click: Retracts LDG lights Taxi lights: Turns on/off Nose light and RWY Turn lights A layer functions are above and B layer below for other rotaries (for example NAV MODE is working in A layer and PFD brightness in B layer).īelow rotaries S: SEL means Short press of the rotary is Selected mode, L: MAN means Long press of the rotary is Managed mode.įor buttons, text above button is Layer A and text below button is Layer B.įor example first button on top row: Layer A = FD, Layer B = ADIRS 1 knob.īutton below that: Layer A = Taxi lights switch, Layer B = APU Master In AAO go to Scripting -> Import scripts -> Open update.xml (select all scripts and click import)įor rotaries Baro and COM works in both layers. Updating from previous version to latest: #Xtouch mini osculator to atem midi template zipIf you are using Experimental version of the FBW A32nx then all is done. If you have Development version of the FBW A32nx then read readme.pdf inside the zip file. Go to Templates -> Apply a template to this aircraft -> Choose FBW_a32nx_exp_xtouchmini and click Apply Go to Templates -> Import template -> Choose FBW_a32nx_exp_xtouchmini.tmpl file from extracted zip -> Click import. Open AAO and make sure Hardware -> MIDI Devices enabled is checked Start MSFS and load FBW A32nx to your favorite airport ![]() Installation (this needs to be done only once, next time AAO will load profile automatically): Printable overlay is included in the zip. À propos de XTouch mini template for Flybywire A32nx (for experimental and development versions) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |