October 11, 20241 yr Hi.. Im using the app Sayintentions.ai which publish K vars to adjust their apps various volume levels.. How Can I add that as a script in AAO so I can use it with a rotary control up/down on my Behringer X touch Mini... Thanks in advance ! Here is what I need to map K:COM1_VOLUME_SET Description: INT range 0 to 100 (in percent) for the volume of the COM1 radio. Settable: Yes K:COM2_VOLUME_SET Description: INT range 0 to 100 (in percent) for the volume of the COM1 radio. Settable: Yes K:AUDIO_PANEL_VOLUME_SET Description: INT range 0 to 100 (in percent) for the volume of the Intercom radio. Settable: Yes
October 11, 20241 yr Commercial Member 2 hours ago, wakevortex said: How Can I add that as a script in AAO so I can use it with a rotary control up/down on my Behringer X touch Mini... You don't need a script. Assign the Behringer rotaries as Axis. Second box from the top on the Add/Change Axis dialog contains the Events. Select the Event, set Axis Min = 0, Axis Max = 100, Rounding "Int", turn the encoder on the Behringer so it shows up on the dialog, save. Edited October 11, 20241 yr by Lorby_SI LORBY-SI
October 11, 20241 yr Author aaaah... thanks ! ... much appreciated will let you know if I have any further issues.. Im so used to using scripts people had already made on flightsim.to. I would never have thought of using an axis for a job like this ... 🙂 Edited October 11, 20241 yr by wakevortex
October 11, 20241 yr Author Hmm.. something Im not grasping ...sorry When you say "select the event". how do I do that ? I have tried to add an axis, and in second box from top , when filtering, all I can see is an event like. COM1_VOLUME_SET. in the list which says its from 0-1 How do I make that a K variable and go from 0-100 ? like below.. K:COM1_VOLUME_SET Description: INT range 0 to 100 (in percent) for the volume of the COM1 radio. Settable: Yes Im missing something simple I'm sure Thanks again
October 11, 20241 yr Commercial Member 2 hours ago, wakevortex said: How do I make that a K variable and go from 0-100 ? like below.. "K:" does not designate a Variable, "K:" is a simulator Event. What you select from the event treelist is that K: Event. You just have to set Axis Min and Max to 0 and 100, as it says in your spec, and set Rounding to "int". As I wrote above. Edited October 11, 20241 yr by Lorby_SI LORBY-SI
October 11, 20241 yr Author That is the issue... If I pick that variable from the treelist. ...COM1_VOLUME_SET It appears in AAO as min 0 max 1 and I cant change those values... the max- 1 is red BTW... Having not delved into this axis area before, Ive no idea how to make the 1 become 100 ..again im sure im missing something simple. .. wish I could just post a picture here 🙂 EDIT..it seems it reacts to MOUSE wheel..the only thing I didnt try ... ! hope that makes sense Thanks again Edited October 11, 20241 yr by wakevortex
October 11, 20241 yr Commercial Member 20 minutes ago, wakevortex said: EDIT..it seems it reacts to MOUSE wheel..the only thing I didnt try ... ! Most numerical boxes in AAO have the following functionality: - Mouse wheel over the left half of the box = big changes - Mouse wheel over the right half of the box = small changes - Doubleclick unlocks the box and you can enter the value using the keyboard. It is the same for the value boxes on the button dialogs, and I think almost everywhere else (=where necessary). Edited October 11, 20241 yr by Lorby_SI LORBY-SI
October 11, 20241 yr Author All sorted... THANK you... I did have an oddity.. I added these 3 events , (once I assigned them to hardware) then saved as a new template which I then merged into an existing aircraft template .. If I try to save OVER my original aircraft template with the new variables added...AAO freezes and I have to kill the process If I give the new merged template a new name it saves perfectly..tried 3 times...repeatable.. weird.. Edited October 11, 20241 yr by wakevortex
October 11, 20241 yr Commercial Member 1 hour ago, wakevortex said: I then merged into an existing aircraft template .. Why not link the template instead of merging it? Then you keep these definitions in one place (they are the same for all aircraft, right?) 1 hour ago, wakevortex said: If I try to save OVER my original aircraft template Sorry, I don't understand. What do you mean? How are you doing this exactly? Bear in mind the difference between Templates and Configurations. "Templates" are mere blueprints, they serve no other purpose than to store data separately. The active part, that is assigned to an aircraft is called a "Configuration". Which one where you applying how to what when the app froze? Edited October 11, 20241 yr by Lorby_SI LORBY-SI
October 11, 20241 yr Author It's the same way I've always used AAO I create a specific template for an aircraft type.... assign that to an aircraft and next time I load that aircraft, all my assignments are there . and if any amendments need to be made to that template at a later date, I add the commands or merge from another template and then re-save the original template with the same name . That didn't work this time as after merging my changes and trying to save the template as usual with the same name as before (overwrite) , the program froze and I had to kill the task ..that was repeatable.. This is the first time Ive used/added AXIS commands... I dont know if thats relevant .. only saving the now changed (merged) template with a NEW name seemed to work The differences in Apply/link template and configuration have never been easy to understand for me to be honest... Thats what has always worked for me... so I didnt change my methodology.. is there any video somewhere to explain this clearly?... Im sure its obvious once you grasp it. ! !
October 11, 20241 yr Commercial Member "Templates->Apply a template..." copies the contents of the template into the aircraft configuration. Meaning, it duplicates everything, and the config stands on its own. Changes to the template will not propagate to the actual aircraft until you apply it again. "Templates->Link a template..." only links a Template to the Aircraft, it does not create copies of everything (=you cannot change anything in the aircraft config). But every change that you make to the template will automatically be present in every aircraft that has it linked. Did you know that you don't need templates for the way that you are using the app? You could just use "Templates->Apply other config to this aircraft". This copies all axis and buttons from one existing config to your current plane, overwriting everything. Your issue sounds like you somehow managed to create a circular reference (=something that is calling itself, ending up in an endless loop). Not sure how you managed to do that, it should be impossible. But these are computers after all. Edited October 11, 20241 yr by Lorby_SI LORBY-SI
October 11, 20241 yr Author Thats really helpful..thank you.. I will take your advice and try to use it in the way it was intended going forward.. We do slip into some bad habits if it works for us LOL again thanks ! your support is fast and helpful as always Edited October 11, 20241 yr by wakevortex
Create an account or sign in to comment