Author Topic: GSX vs custom Keyboard Bindings  (Read 580 times)

swissdani

  • Newbie
  • *
  • Posts: 31
GSX vs custom Keyboard Bindings
« on: November 16, 2025, 01:23:15 pm »
Hi Umberto

I wanted to use the custom pushback function on one of my flights today. However, I noticed that some of the keys specified in the manual (arrow keys, num pad 1 and 3) had no effect. Could this be because I have manually defined all num pad numbers as custom view points? The arrow keys are also defined so that I can use them to look left, right, etc. in the cockpit. Does this interfere with the GSX function?

Would I need to create a new keyboard control profile specifically for GSX, where none of these keys are assigned a function in MSFS2024?

Best regards,
Daniel

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 53111
    • VIRTUALI Sagl
Re: GSX vs custom Keyboard Bindings
« Reply #1 on: November 21, 2025, 02:39:14 pm »
Exactly, the GSX manual suggest some default keybinds that should be disabled, but that assumes you are using a default settings, if you added other keys that are used by GSX, you must disable them in the sim as well.

That's a simulator limitation that started with MSFS 2020. In FSX or P3D, developers could *temporarily* "steal" a key from the sim entirely, do what they need to do with it, and give it back. The only possible issue of this approach, is that two application might try to do this at the same time, so only one of them would work, but it was easy enough to solve if at least one of the conflicting 3rd party apps had the ability to redefine its keys.

This feature has been removed from Simconnect so, whenever a key is used, it's always passed back to the simulator so, instead of "risking" a faulty addon to steal a key permanently from the sim because it had a bug and it never gave it back, we are now *always* get a conflict no matter what, because both functions are executed at the same time, so the limitation that was supposed to be placed to prevent those rare bugged addons, resulted in a conflict every time the sim and the 3rd party app want to use the same key.