I've created a number of keyboard shortcuts for use with the Cirrus SR22T in MSFS 2024. I test each one of them inside the aircraft and they all work in 2D. I also use Voice Attack in VR to be able to activate the commands. At the start of a VR session, i.e., during a cold start, the voice commands work fine. At some point during the session, about 80% of them stop working. On most of the commands, I have a response programmed through Voice Attack so I know that it recognized the commands. I have no idea how to start to troubleshoot this issue, so hopefully someone here can help?

In what way does this concern a Lorby app? Are you assigning the keyboard keys in AxisAndOhs? If so, make sure to update the device blacklist. And maybe consider using vJoy instead of keyboard commands.

3 hours ago, Lorby_SI said:

In what way does this concern a Lorby app? Are you assigning the keyboard keys in AxisAndOhs? If so, make sure to update the device blacklist. And maybe consider using vJoy instead of keyboard commands.

3 hours ago, Lorby_SI said:

In what way does this concern a Lorby app? Are you assigning the keyboard keys in AxisAndOhs? If so, make sure to update the device blacklist. And maybe consider using vJoy instead of keyboard commands.

Yes, the keyboard binds are done in Axis and Ohs. I took a look at the device blacklist and the Keyboard is identified and listed as allowed. I'll take a look at vJoy.

Just now, mkel2010 said:

Yes, the keyboard binds are done in Axis and Ohs. I took a look at the device blacklist and the Keyboard is identified and listed as allowed.

Actually, that should be blacklisted as well. I know, this sounds weird, but AAO communicates with mice and keyboards through other means. When you have trouble like this, make sure to blacklist absolutely everything - except for your game controllers = joystick/yoke/pedals/TQs

But what I suspect is that maybe not all keyboard events are reaching AAO, and it will miss the odd key press or release and ultimately potentially get stuck. Not sure.

Edited Saturday at 07:59 PM3 days by Lorby_SI

29 minutes ago, Lorby_SI said:

Actually, that should be blacklisted as well. I know, this sounds weird, but AAO communicates with mice and keyboards through other means. When you have trouble like this, make sure to blacklist absolutely everything - except for your game controllers = joystick/yoke/pedals/TQs

But what I suspect is that maybe not all keyboard events are reaching AAO, and it will miss the odd key press or release and ultimately potentially get stuck. Not sure.

I will try that. Right now, the only thing I have attached is the Keyboard.

2 hours ago, Lorby_SI said:

Actually, that should be blacklisted as well. I know, this sounds weird, but AAO communicates with mice and keyboards through other means. When you have trouble like this, make sure to blacklist absolutely everything - except for your game controllers = joystick/yoke/pedals/TQs

But what I suspect is that maybe not all keyboard events are reaching AAO, and it will miss the odd key press or release and ultimately potentially get stuck. Not sure.

Blacklisting the keyboard seems to have fixed the issue.