Hi,

i have updated to the latest Version of the AaO and i realized that at some point Axis and Ohs doesn‘t recognize my Keyboard Button that i have binded to „Voice Toggle“. Its kinda random dying on my. When i press the Keyboard Button (in my Case „+“) i cannot see a green light in all the active Button Assignments, also when i try to add a new button it doesn‘t detect the Keyboard press. 

What helps is: pressing the green connect button and disconnect AaO from MSFS then press it again to connect it. Then the Keyboard Press is detected normal until it Dies again random at some point.

Can someone else please tell me if this is only the case for me or does it happen for someone else too?

Sounds like AAO is not receiving a/the key up event from your keyboard. Could be from another key too, doesn't have to be the '+'. When it thinks that a key is still being pressed, the next keyboard input is registered as a combination key, which does nothing for you. Disconnecting and reconnecting the app clears out that buffer.

"Voice Toggle" means the voice recognition toggle event?

Edited August 13, 20241 yr by Lorby_SI

40 minutes ago, Lorby_SI said:

Sounds like AAO is not receiving a/the key up event from your keyboard. Could be from another key too, doesn't have to be the '+'. When it thinks that a key is still being pressed, the next keyboard input is registered as a combination key, which does nothing for you. Disconnecting and reconnecting the app clears out that buffer.

"Voice Toggle" means the voice recognition toggle event?

yes correct the "Voice Recognition Toggle event" its the only button i use a keyboard button Press to toggle. The rest of my AaO buttons are Midi and Controllers (Alpha Yoke and Bravo Throttle) so its really just the one button that stops working. 

Its also not my main keyboard only a USB Numpad that i otherwise use for changing the Views inside the MSFS but don't have that programed via AaO, i use the normal MSFS Control Settings for that. These are also working when the AaO button is not working. So cannot be a hardware detection issue.

I've just tested this,  "+" key on the numerical keypad bound to a button assignment that triggers a script that increments an LVar. 

I cannot detect anything wrong.

• pressed the + key about 200 times
• Held the key down for a few seconds a couple of times
• Used other keys in between.
• Pressed Shift and Ctrl together with the "+" (nothing happened, which is correct in this case)

The "+" worked without fail every time when it was supposed to.

Edited August 13, 20241 yr by Lorby_SI

i can give you more what i do, its happening when i use my voice checklists, the first one is working and then the second one that i want to call for and press the "Voice-Detection-Keyboard Button" it doesn't work

50 minutes ago, Bam2000 said:

i can give you more what i do, its happening when i use my voice checklists, the first one is working and then the second one that i want to call for and press the "Voice-Detection-Keyboard Button" it doesn't work

But - that doesn't sound like an issue with the keyboard then. That must be related to something the/your checklist does.

I'm sorry, but I have no idea how to reproduce this at the moment. This may take a while.

Hey, have some mor information now on this problem.

I have binded the stock command "Voice Recognition Toggle" (L:VoiceRecOn)·1·==·if{(VOICE:Microsoft·Zira·Desktop)·(SPEAK:Voice·recognition,·off)·1·(>K:AAO_VOICEREC_OFF)·0·}·els{(VOICE:Microsoft·Zira·Desktop)·(SPEAK:Voice·recognition,·on)·1·(>K:AAO_VOICEREC_ON)·1·}·(>L:VoiceRecOn) to a midi button and whenever i have the problem that the keyboard is not activating the Voice Recognition i try to execute that Midi Button. Then i Hear and see for around 1 second the green light and "Voice Recognition on" just short after "Voice Recognition off" without me pressing the button twice.

So it has nothing to do with the keyboad not working more like the voice recognition turning itself off direct after turning on. Since my Keyboard Button doesn't have the Voice Output included i did not realize it before.

I have tried to check logs, but could not find anything regarding Voice Recognition Crashing, will keep an eye out if i find anything. Latest Log:

13.10.2024 09:54:47.248 : MW: Exception received: 3 from send id 50 errloc 50
13.10.2024 09:54:47.255 : Exception received: 3 from send id 24 errloc 1
13.10.2024 09:54:47.255 : Exception received: 3 from send id 25 errloc 2
13.10.2024 09:54:47.255 : Exception received: 3 from send id 26 errloc 3
13.10.2024 09:54:47.272 : Exception received: 3 from send id 28 errloc 5
13.10.2024 09:57:36.150 : SH: Invalid Simulator Variable - check StartupLog - Ex 7 from send id 243 errloc 121
13.10.2024 09:57:36.190 : SH: unrecognized SimConnect ID - invalid event or setter variable? From send id 318 errloc 196
13.10.2024 09:57:36.190 : SH: unrecognized SimConnect ID - invalid event or setter variable? From send id 326 errloc 204

 

 

Edit a restart of AaO or pressing the green icon to disconnect and reconnect or even just going to the Script Editor fixes the problem and the Keyboard and Midi button activate the Voice Recognition again

 

edit2: also it sometimes doesn't work directly after start, so i guess it cannot be something with my Voice Checklists because i did not execute any

 

Edited October 13, 20241 yr by Bam2000

A little Update on this: latest Version 4.50 fixes the Keyboard issue for me. I guess it was connected to " - Bugfix: Keyboard button used as Toggle Combo doesn't release " So thanks for the fix, keep up the great work 🙂

Edited November 25, 20241 yr by Bam2000