Parme

Hi sorry for late answer been away for works No I don’t :)

I’m having issues doing that, cus when aao has a assigned PTT it won’t listen so it never recognizes the ”now”

Yes, the scripts are done and the lights are on, maybe there is something in my windows

well so basically, Aao works that way so that you need an "!" after the command, that tells AAO to wait until the PTT is released so that you have time to speek the numbers so, if i put "at" before the exclamationmark it will release the PTT before the numbers are said. so basically the worh for the release of the PTT needs sadly to be after the numbers...

Hmm Im not sure , but you could probably do a voice command as the PTT and send it as a virtual keypress, for example let’s say the word ”now” is the trigger for PTT, so if you say ”now … set altitude to 12000 end” the word ”now” triggers the PTT and the word ”end” releases it ? So basically you get 2 words extra instead of a physical keypress. I’m not sure if it will work but in theory it should. I can test it if you want

(>A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·Feet) is the working AAO variable for G1000 altitude set ,

wait, lorby helped me with everything on this forum, here is the link https://www.avsim.com/forums/topic/699647-communication-between-voiceattack-and-aao/page/3/#comment-5811629

Hmm I’ve never done that but if you want I can help you in discord

I’ve managed to get all the commands working now using AAO. It’s a completely other variable it uses and it’s not supported in the agent. But what i did now is that i created my own script for aao and call altitude , heading and verticalspeed from there instead. To compile a new dll for the agent was after some research way too complicated for me

lol nevermind, i had to roll 1 time on the knob then it worked, it doesnt work when the "--" is in the altimiter, it has to be 0, so from default aircraft state it wont change. lol. thanks alot lorby

weird, i have this in my script (L:AaoVoiceRecNum)·(>A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·Feet) and nothing changes, ive also checked the AAO voiice recognition window to see that it getting exactly what i say and i also see the green light flashiing on the script ....

yeah i see, but none of the above variables for altitude change in the g1000 did work so i have to search more

Thanks ! I will definitely play around with this instead ! Do you have a trick in your sleeve to find out this kind of information cus it didn’t pop up in the list of events

What I’ve tried is to use the event reader and then rotated the inner and outer knob to see what events that triggers , funny thing is that the AP_SET_ALT_ENGLISH triggers but it’s not possible to use that event in the script cus then it just increments och decrements by 1000 or 100. I’ve also tried to use the inner and outer knob events but same thing happens

It looks exactly like the AAO manual, the plane I try it on is the Cessna 172 g1000, it works fine on the classic :)