wakevortex

Great... thanks again.... off to learn about script files then LOL 🙂

Thanks again yes seems indeed this is not as easy as I thought...will take a look at your suggestions.. not sure what you mean here "consider using a script file instead of the in-app scripts"?... how do I do that ? there will be more than 1 use case ...I ideally wanted to basically use a change in variable state to trigger various announcements p71 of the manual is helpful... ! EDIT... your idea worked perfectly for this use case (battery on - trigger an announcement to start my VA logging program ) Going forward should I try to stick to that ?..the script file you suggested sounds interesting , but what I have seems to work really well ! appreciated !

Just following up on this.. now its working as expected, Is it possible to now trigger my working script from a sim variable in AAO...so for example when Battery is turned on...it triggers a script (and therefore speaks) .. how would that be called from AAO rather than using a button.. any help appreciated

Thanks for your great help... this worked beautifully ! (QUERYXML:https://apipri.sayintentions.ai/sapi/sayAs?api_key=YOURKEYHERE&channel=INTERCOM1_IN&message=Cabin%20secure&rephrase=0) appreciated as always

Thanks for the reply.... will take a look tomorrow...as mentioned I could get SI to generate voice from browser and cmd line, just not from AAO this was what worked from CMD. curl --get --silent "https://apipri.sayintentions.ai/sapi/sayAs" --data "api_key=MYKEY&channel=INTERCOM1_IN&message=Cabin%20secure&rephrase=0" again all a little out of my depth... but will experiment with what you said ..

Hi there.,..Im trying to use this new feature of Sayintentions.ai with AAO , and am stuck ..I even enlisted help of chat GPT as this is a little out of my knowledge level to be honest this is what Im trying to do initially using a joystick button to test and then moving on to a variable when it works.. https://sayintentionsai.freshdesk.com/support/solutions/articles/154000233373-sayas-api-make-the-co-pilot-cabin-crew-atc-say-whatever-you-want I can make it work from a web browser and cmd prompt, (voice triggers) but not AAO when I assign the test script to a button...no voice is heard ..any ideas? heres what GPT came up with 'cmd /c "C:\\Windows\\System32\\curl.exe" --get --silent "https://apipri.sayintentions.ai/sapi/sayAs" --data "api_key=MYKEY&channel=INTERCOM1_IN&message=Cabin%20secure&rephrase=0"' · run would appreciate any ideas...im sure its simple but its above my pay grade LOL thanks. !

Guensli came back with an answer..it seems the variables ARE different, but only by Capital/small letters ! what a strange one ! below from Guensli " I just have discovered that 2020 and 2024 use different variables. so, e.g. for SPD Knob in 2024 it is: 1 (>IE:AIRLINER_FCU_SPD_KNOB_PULL) and for 2020 it is 1 (>IE:AIRLINER_FCU_SPD_KNOB_Pull) So, 2020 users have to change in the AAO script editor this for BARO, SPD, HDG, ALT and VS from PULL/PUSH to Pull/Push Thats just a workaround, I "officially" do only support 2024"

Good point... was just watching the knob for push or pull.... will do some more experimenting and try those A300 vars.... again thanks !

Sadly they didnt work as RPN s (1 (>L:INI_FCU_MANAGED_SPEED_BUTTON, Number) or 1 (>L:INI_FCU_SELECTED_SPEED_BUTTON, Number) difficult I know for you as you dont have the aircraft ...but thanks for trying ! Ive asked guensli if he has any ideas.... or maybe someone else here has it working?

Thanks !..will try that and see how I get on ... will let you know

Guenslis scripts has for example 1 (>IE:AIRLINER_FCU_SPD_KNOB_Pull) 1 (>IE:AIRLINER_FCU_SPD_KNOB_Push) and 1 (>IE:AIRLINER_FCU_HDG_KNOB_Pull) 1 (>IE:AIRLINER_FCU_HDG_KNOB_Push) Totally different as you can see, but that doesnt seem to have any effect in FS2020 ...havent tried it in FS2024 will have a look with FSdev mode, but thats not something im familiar with .. BTW the inibuilds post with those lvars I posted have a linked PDF and this info " You can view a list of the key LVARs on the iniBuilds A350 Airliner via this sheet here or via the attached PDF for reference. What are LVARs? LVARs are "Local Variables" which are used to read/set various switches or system behaviours in the aircraft. How to use LVARs? You can bind the listed LVARs to various hardware switches, axis or buttons to control their virtual counterparts on the iniBuilds A350 Airliner externally using 3rd Party software (e.g. Mobiflight, Axis and Ohs, SPAD.Next or FSUIPC etc.)" appreciate the help

Im in Fs2020 and tried guenslis new AAO scripts for teh inibuilds A350 which all work except push and pull knobs on the FCU.. he says he wrote them for FS2024 and he couldnt check FS2020 I found the Lvars documented... on the inibuilds forums they are for example INI_FCU_MANAGED_SPEED_BUTTON Bool Push Airspeed Knob INI_FCU_SELECTED_SPEED_BUTTON Bool Pull Airspeed Knob INI_FCU_MANAGED_HEADING_BUTTON Bool Push Heading Knob INI_FCU_SELECTED_HEADING_BUTTON Bool Pull Heading Knob How would I make these work in AAO to use with an xtouch mini (im sure its simple but i tried a few things with no success ) thanks !

OK initial test with the FS2024 version...it imports my Fs2020 database, and connects .. all good so far.. tried a basic aircraft I had in Fs2020 (Milviz 310R) and it responds as expected Only small issue found so far entering the hardware change menu (to check my hardware assigns ( it had the 2 xtouches wrong way round) ) kills the Simconnect connection and I have to manually reconnect.. (maybe thats always been the case) but it seems to be working...good work !

Thanks ....mail sent. !

Great ...thanks for info...good there is a workaround...feeling lost without AAO !