Lorby_SI

AAO has no voice recognition system, it relies on Windows speech'to'text by default, or the bridges (Windows Online = "Cortana", Azure, Polly). I'm not sure what I could fix though, the Cortana bridge seems to work normally for me? What should I be looking at? Apparently, recognition works very well for some people, and not so great for others. Not sure why that is, AAO is using the same mechanisms as most other tools, including I think VA... One of the AAO testers even built an entire ATC voice interaction system based on AAO, using custom grammars and lots of Javascript.

Not for me, I can't confirm that one. Can you specify what "breaks" means? What exactly are people reporting? I am running StreamDeck 7.5.1 right now (just updated as well), with the AAO plugin, using the BKSQ StarShip profile in MSFS 2024. Seems to work just fine. Cross checked with the Lorby Gauges profile, working as well.

That is not enough information. How this must be operated depends on what type of asset it is (HVar, IE, BVar, LVar etc.), and what value you should be sending with it. And IE will do different things when you send value 0 with it than when sending 1. Not at my computer at the moment - I would suggest taking a look at the knob's behavior code. Activate MSFS developer mode, open Tools->Behaviors, click back in the sim and hover the mouse over the knob. Then press Ctrl-G. Now take a look at the MouseRect component - it shows what happens when the knob is operated with the mouse - that's what you then replicate in AAO.

The variable name is only misspelled in the initial example. It is correct on the subsequent pages and also on the "LVars used by the voice recognition module" page. The gauge should be in the list by default, it is shipped with the app. "Gauges -> Desktop FIPS -> + -> Select 'Voice recognition status' from the dropdown"

That was my impression as well. In general, the purpose of LVars normally isn't "operating" stuff. They are just variables holding a value, they don't "trigger" anything. Their traditional purpose is to control the 3D animations and the lighting of the knobs, levers etc. But since MSFS there are no rules anymore, the developers all do things differently - and not all of them have external controls in mind. Sometimes the AAO user has to resort to really dirty hacks, and sometimes there is no way to control something from the outside at all (=only with the mouse)

OK, so I looked into it. There is a typo in the manual, the variable that holds the numerical value is called "(L:AaoVoiceRecNum)". I would also recommend to run the "Voice Recognition Status" gauge, so you can see what is being picked up. I have to leave a significant pause between the text and the numerical value, and my microphone doesn't seem to be the best - the Bridge struggles to pick up the correct numbers.

Does the Synaptic list say that you can write to this LVar? Many of them are read-only and you will have to use an Event from the other list.

I've just tested the Cortana Bridge. I've downloaded the ZIP from the AAO website and followed my own PDF instructions regarding installation and setup in AAO (scripts and config). Initially I got the same error as you, but that went away when I reattached my microphone... apparently I disconnected that at some point (I recently had PSU trouble). After a restart the bridge started to work normally.

"Cortana Bridge" is just a name to differentiate it from the normal Windows Voice Rec. It doesn' need the actual "Cortana" subsystem. But I haven't used it in years, maybe something did change in Windows. I would recommend not to start running. Try the default Windows engine first. And look around for a VoiceAttack MSFS plugin.

Appatently, VA has a plugin system. So it should be possible for you to write a plugin that processes your voice input, wraps it into suitable RPN code and send that to AAO via the WebAPI. Or maybe someone already made a plugin that talks directly to the sim?

Yes, bordering on impossible. I have no idea how to do that. The obvious solution would be if VA would access AAOs WebAPI - and I am very sure that it doesn't. But I know nothing about VA or its capabilities, so I couldn't say if there is a really esoteric detour (like using an AAO webpage or Javascript as intermediate). In any case, this is quite the project you have there. If the built in voice recognition would work for you, that would be CONSIDERABLY easier.

AAO Manual, Chapter 4 "Voice recognition", section about "Numerical input" The issue with AAOs voice recognition is, that it relies on the Windows Voice Engine, which for some people is working fine, for others it isn't. There are additional plugins for AAO that improve on that, like the "Cortana Bridge". As for VR: you can display the StreamDeck as a gauge in VR. Check out "Streaming the StreamDeck" on the AxisAndOhs Downloads page: Downloads - AXIS AND OHS

How are you sending commands from VA to AAO??? Why not use the voice recognition that is built into AAO or one of the bridges?

(only) LVar collection and BVars rely on the AAO Community package "lorbysi-content-hooks". Make sure that the package is present and active in your Community folder. Instead of BVars try using their parent, the IEs. Check the "MSFS IEs" tab on the AAO event selection dialog. BVars are the "bindings" of an IE, which in most cases can be used directly by supplying the correct value (with IEs it is not just 1 or 0, it can be anything).

The web page seems to be comprehensive, it also mentions when a LVar is read-only (=they cannot be used to operate a switch, only to read its state/position). There is also a second list with default simulator SDK events that can be used, there just wasn't one for the FD (at first glance).