February 13Feb 13 Dear Team, with the update to v1.2.1 my keybindings for FMGS to WINCTRL MCDU does not work anymore. The name convention changed from v1.2.0 Old Key Down Event: AIRLINER_KBD_B_1 (AIRLINER_KBD_B_1) I could read out with the MSFS2024 DEV Tools, that it is now: A350_INTERIOR:PEDESTAL:FMGS_1:KBD_B_1 I tried following cases: 1 (>IE:A350_INTERIOR_PEDESTAL_FMGS_1_KBD_B_1) 1 (>B:A350_INTERIOR_PEDESTAL_FMGS_1_KBD_B_1) (>H:A350_INTERIOR_PEDESTAL_FMGS_1_KBD_B_1) Any suggestions are welcome. Kind regards Airliner001
February 13Feb 13 Commercial Member Sorry, the sim won't start for me at the moment. When dealing with native MSFS Input Events ("IE" in AAO), you can just select them from the events dialog in AAO, on the tab "MSFS IEs". That way you avoid typos or incorrect spelling. And you don't need scripts for everything, IEs can be directly assigned to buttons. Edited February 13Feb 13 by Lorby_SI LORBY-SI
February 13Feb 13 Commercial Member 2 hours ago, Airliner001 said: I could read out with the MSFS2024 DEV Tools, that it is now: A350_INTERIOR:PEDESTAL:FMGS_1:KBD_B_1 No, that is the path of the component (=the 3D button on the panel). It has nothing to do with how that component is operated, that would be in the MouseRect or InputEvent sections. Closer inspection of the Mouserect reveals that now you have to use LVars. 1 (>L:INI_MCDU1_B, Number) IMHO this makes no sense at all. They already had everything bound to IEs. This looks like a bug/oversight by inibuilds. Edited February 13Feb 13 by Lorby_SI LORBY-SI
February 13Feb 13 Author Thank you for quick your help. It works very well! Have a nice weekend. Kind regards Airliner001 Edited February 13Feb 13 by Airliner001
Create an account or sign in to comment