Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

MSFS Gear not working

Featured Replies

I tried to get the gear working with several functions, including GEAR_TOGGLE, GEAR_SET (1 or 0) and setting those values in scripts, nothing seems to be working. A binding directly in the sim to toggle gear works, but I want to use Voice Recognition for it, thus AAO. Any ideas?

Further, is there a way to debug Voice Recognition in AAO and see what it recognizes if anything, and if the corresponding button function is executed?

  • Commercial Member

GEAR_DOWN and GEAR_UP are the events that seem to work most of the time. But it seems more likely that the voice recognition is not set up correctly on your end. Be mindful of the language settings in the Extras menu. 

No, there is no debug option. In general, AAO doesn not "recognize" anything - it is using the Windows Voice Recognition feature. SO make sure that this one is working first. On many computers, when this feature is used by a program, you will see a small microphone icon in the lower right corner of the screen.

Edited by Lorby_SI

LORBY-SI

  • Commercial Member

Asobo Bonanza G36 (where the gear lever moves even when you are on the ground)

1 (>K:GEAR_TOGGLE) - tested, working
0 (>K:GEAR_SET) - tested, working
1 (>K:GEAR_SET) - tested, working
1 (>K:GEAR_UP) - tested, working
1 (>K:GEAR_DOWN) - tested, working

Edited by Lorby_SI

LORBY-SI

  • Author

Yes I just found out that the gear error is on the 3rd party (RedWing Super Constellation), will check with them.

My Voice Recognition works well with other commands, that's not the issue, but it helps that eg. in VoiceAttack, I see what's being recognized to debug.

  • Author

If we could at least have the green light next to the assigned button light up when the voice recognition worked, that would help

  • Commercial Member
12 minutes ago, Eteokles said:

I see what's being recognized to debug

I'm not sure that I understand that one. All that AAO gets from the Windows subsystem is the information that the term that you typed into in the box in the AAO Button Assignment has been understood. If you write "pause" in the box, the AAO app gets a notification from the Windows Voice Recognition when "pause" has been received - nothing else. I don't see where I could possibly provide any additional information?

Edited by Lorby_SI

LORBY-SI

  • Commercial Member

Here is how this works:

An app that wishes to use the Windows Voice Recognition system creates a "Grammar". That object contains all the words that it wants to be notified about, when the Windows subsystem recognizes them. In AAO, the Grammar is built from what you wrote into the input boxes of the Button Assignment dialog. And that is all the information that AAO will ever get: if Windows understands your terms, it will notify AAO - that's it. There is no debug information, no information about other Grammars that may or may not be understood, nothing.

Just make sure that you have selected the correct language in AAO. If anything is causing trouble, that is usually it.

Edited by Lorby_SI

LORBY-SI

  • Author
1 hour ago, Lorby_SI said:

It does that already.

It doesn't for me. As I already said, Voice Recognition itself works pretty well for me, so that's not the issue, but creating new commands, it helps to have some check if the voice was understood or not. For me, the button green light doesn't light up even when it works (whatever I want to do in the sim works).

  • Commercial Member
39 minutes ago, Eteokles said:

It doesn't for me.

Weird. It does for me. I say the word, it takes a moment, then the green light comes on for a fraction of a second, but still very noticable. Are you using the PTT? If you do, how is that set up, toggle or continuous press?

"Tools->Find button" works as well btw.

Edited by Lorby_SI

LORBY-SI

  • Author

I set up my own script to toggle voice recognition on and off with a local variable that I set. (tbh was confused that AAO doesn't natively support to set buttons as toggle).

(L:VOICEREC)·0·==·if{·1·(>K:AAO_VOICEREC_ON)·1·(>L:VOICEREC)·(SPEAK:VOICE·RECOGNITION·ON)}·els{·1·(>K:AAO_VOICEREC_OFF)·0·(>L:VOICEREC)·(SPEAK:VOICE·RECOGNITION·OFF)}

  • Commercial Member
46 minutes ago, Eteokles said:

tbh was confused that AAO doesn't natively support to set buttons as toggle

Not sure I understand that one. Voicerec PTT was intended as a "press-and-hold" action (down event = on, up-event = off on the same button). You were looking for an extra Toggle event?

In any case, on my end it doesn't matter how voicerec is turned on or off. The green LED is always working. 

Edited by Lorby_SI

LORBY-SI

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.