Totally agreed. For “serious” simmers investment on hardware goes a long way, and the frustration of not being able to map controls really subtract from immersion. It is the thing I like the most on DCS: EVERY switch, action, button, lever, knob that can be accessed via mouse is also in the control list to be mapped… so it IS possible even on much more complex aircraft, please make it happen also on MSFS planes
2 Likes
One new thing in '24 is that apparently we can now set and read B vars (Input Events) via RPN calculator code from standalone WASM modules (execute_calculator_code() Gauge API). That includes “setting”/triggering the different suffix variants like “_Inc”, “_Toggle”, etc., which we can’t do with SimConnect.
In '20 this was only possible from gauge modules, not standalone ones. Though there has been no official word about it (not even a mention in any release notes that anyone can find), and in fact they officially deprecated the whole Gauge API w/out providing any alternative for running RPN code (it still works, just, you know, “deprecated”). It’s possible this isn’t even intentional or could cause random puppies to suddenly keel over. 
I wouldn’t have known about it except for this thread on the dev forums (about one that doesn’t work, ironically). Tried it with some others and it worked.
https://devsupport.flightsimulator.com/t/some-inputevents-dont-work-when-sent-via-execute-calculator-code/11564
(My WASimModule and the accompanying testing UI is a pretty quick way to play with running RPN remotely and works with '24… links in my forums profile.)
any news on this subject? over one thousands requests did catch the attention of MS/Asobo? Ad moreover, am I the only one finding the assignment of the commands unreliable? Like park brake on and off does not work, only the toggle option…
With MSFS, I had to use extensively the Bvars to control the Famous Flyer Boeing 707. To get the hash codes, I used the names as shown in Behaviors; the names were a mix of lowercase and uppercase letters.
With FS2024, it is not working as is. I noticed that the Bvar names are the same but all in uppercase letters. Eventually, after changing the names to uppercase letters, everything seems to work again.
1 Like
Do you use Spad, AAO or something else to trigger the bvars?
You need to use your mouse in cockpit or external software as asked by you above.
1 Like
No, I use my homemade SimConnect client.
1 Like
Definitively voted YES. 
Another +1 vote from me!
1246 votes and counting…
I fear this will never happen and this post of mine in a similar thread explains why.
Since the roadmap item for this topic has been changing status to indicate it’s done, I would like to point to this post from when the new API was introduced (2023) for the shortcomings of the current enumerate input events api. These are things that would be essential to make the input events api practical and useful.
To our understanding these are still valid concerns and this has not improved.
I am sure Sebastian of MobiFlight who started this thread would be happy to share his feedback and input on the API topic, as there has not really been much communication from Asobo regarding this as far as I know. We have thousands of users using MobiFlight with MSFS2024, and providing a better API to query the aircraft directly for cockpit controls instead of writing snippets of calculator code would be so much more robust and convenient.
I can’t help to think these users have nothing to do with Xbox or PS5, so…