Keyboard event bind (VK_END) triggering elevator trim up

[geoffda]

I have a button bound to VK_END to trigger the external camera view in MSFS 2020. This has worked for ages (and in fact was working two days ago). Starting today, VK_END is now triggering elevator trim up instead of the external camera view. Pressing the End key on the keyboard results in the expected behavior.

1. If I delete the AAO binding, then the button press no longer triggers a trim up event, so that would suggest that I don't somehow have a trim up event bound to that button elsewhere. Nevertheless, I have verified that there is nothing else bound to that button in my MSFS settings.

2. Deleting the binding and recreating it results in the same behavior.

3. Starting with a brand new aircraft profile and creating the binding results in the same behavior. This is includes trying several different aircraft.

4. Binding to different buttons and/or different controllers results in the same behavior.

5. Binding VK:Insert instead of VK:End does not work. It appears to do nothing, but it is possible that it is triggering an incorrect bind that I'm just not aware of.

6. The same bind works correctly using FSUIPC.

7. Uninstalling and reinstalling AAO had no effect.

8. Renaming the LorbyAxisAndOhsMSFS directory and creating the bind in a new profile has no effect.

9. Using the scripting 

All signs point to this being an AAO problem. I'm running Windows 11 22H2 (OS Build 22621.2283) and I did pick up this update today, so it is possible that it introduced an issue. AFIK, that is the only thing that has changed on my machine since this was working two days ago. Can anybody confirm that the End key can be bound in this Windows 11 build for MSFS and that the binding correctly triggers the external camera view? Otherwise, if anybody has any further suggestions on what to try or how to debug this I'd appreciate it!

 

Edited September 17, 2023 by geoffda
more detail

[Lorby_SI]

I'd suggest using scripts instead of direct keyboard bindings. That way you can send the actual scan code of your hardware keyboard. And set the app focus on flight simulator at the same time

In genereal I would advise against using virtual keyboard events. vJoy or ViGem are the better solution IMHO

 

 

Edited September 17, 2023 by Lorby_SI

[geoffda]

Yeah, I tried that as well. 

(FOCUS:FlightSimulator)·(VKD:79-207-35)·(SPLIT:100)·(VKU:79-207-35)··

has the exact same behavior; that is it results in an elevator trim up event.

[Lorby_SI]

Sorry, no idea. Sounds oddly specific. What is the Trim Up bound to? Could those two codes be mixed up somehow? Num Lock issue?

Edited September 17, 2023 by Lorby_SI

[Lorby_SI]

Use SDK assets instead of key bindings?

Script for external view:
3·(>A:CAMERA·STATE,·Enum)·0·(>A:CAMERA·VIEW·TYPE·AND·INDEX:0,·Enum)·0·(>A:CAMERA·VIEW·TYPE·AND·INDEX:1,·Enum)

Script for the cockpit view
2·(>A:CAMERA·STATE,·Enum)·0·(>A:CAMERA·VIEW·TYPE·AND·INDEX:0,·Enum)·0·(>A:CAMERA·VIEW·TYPE·AND·INDEX:1,·Enum)

Script for showcase view
5·(>A:CAMERA·STATE,·Enum)·0·(>A:CAMERA·VIEW·TYPE·AND·INDEX:0,·Enum)·0·(>A:CAMERA·VIEW·TYPE·AND·INDEX:1,·Enum)

Script for drone
4·(>A:CAMERA·STATE,·Enum)·0·(>A:CAMERA·VIEW·TYPE·AND·INDEX:0,·Enum)·0·(>A:CAMERA·VIEW·TYPE·AND·INDEX:1,·Enum)

See spec here:
Camera Variables (flightsimulator.com)

Edited September 17, 2023 by Lorby_SI

[geoffda]

Thanks, (and I just saw your edit, so thanks for saving me the the effort of trawling docs to figure out how to send the enum values 🙂 ). That seems to work.

What is weird is that I just tried uninstalling/reinstalling and now the bind half-works. On the first button press, I get the external camera view (though it still moves the trim), but on the second press, it doesn't recognize the End press and only sends the trim up.

[Lorby_SI]

Chris_PU_A320 has published a StreamDeck package for the A310 on flightsim dot to that has a lot of camera related scripts in it. Just disregard the StreamDeck stuff if you don't have one, all you want is the script XML file to import in AAO.

[Lorby_SI]

5 minutes ago, geoffda said:

uninstalling/reinstalling

That does nothing for Lorby apps. Save yourself the trouble.

[Lorby_SI]

I just tried this with the default A320. I've assigned the following script to a button on my yoke:

(FOCUS:flightsimulator)·(VKD:79-207-35)·(SPLIT:100)·(VKU:79-207-35)·

Those are the scan codes for the "End" key on my keyboard (separate block with ins, del, end, pos1, pg up, pg dn). It toggles between the external and the internal view. The elevator trim does not move.

Edited September 17, 2023 by Lorby_SI

[geoffda]

Thanks. Unless there is something that got introduced by the specific Windows build I just upgraded to, there must be something going on that is local to my machine...Now that we have camera simvars, I'll try to sidestep whatever the problem is by using those.

[Lorby_SI]

I'm on Windows 11 22H2 build 22621.2283

Not missing any updates as far as I can tell (or rather Windows Update).

Edited September 17, 2023 by Lorby_SI

[geoffda]

PM Sent.

Edited September 18, 2023 by geoffda

[geoffda]

For anyone else encountering something like this, the Num Lock key needs to be on for the binds to work correctly for extended keys. In the case of the End key, when Num Lock is off, it gets treated as the Num Pad 1 key--which is the default MSFS bind for up elevator trim.

Edited September 18, 2023 by geoffda