It would be nice to be able to bind a knob press to something.
For example I have a IRL knob for altitude selection and I can also press that knob. Some airplanes can modify the altitude steps from 1000 to 100 ft by pressing the altitude knob on the cockpit. I would like to be able to assign that to my IRL knob.
Thank you!
EDIT: to be clear, I’m talking about changing the increment. Incrementing by 100 or by 1000 and vice versa. Not the altitude itself.
Nothing stopping you from doing that in what you posted. I do this for most aircraft that have that feature and even some that do not.
The final answer will of course depends on the aircraft, what your knob is and what if any additional software you use.
How? There are no shortcuts to change the steps increment. And I don’t use any additional software.
Maybe my post wasn’t clear enough, but I don’t talk about increasing or decreasing altitude, I talk about the incremental steps being 100 or 1000 and being able to change that on the knob press.
Some generic knob press events have keybinds assigned, like nav and com swap which I assign to a couple encoders w/ press function on my throttle.
Far more knob presses are custom events coded in the various planes that have sim connect variables assigned, but not key bind events.
You are in Mobiflight territory if you want to access those. This doesn’t help console users however.
That’s why I’m requesting the addition of the key bind that as a wishlist 
Yeah, I understand. But I also would not expect them to add keybinds for custom events used by 2nd or 3rd party airplanes. So I think we’re likely to be unsatisfied.
I don’t own third party airplanes yet so I guess you are right.
But isn’t it also the job of those third party devs to make those key bonds available? Maybe if MS/Asobo needs to make it accessible for them to do so.
Use xs and o’s or spad.next
If you are talking about the control settings menu and what’s available to assign there, to the best of my knowledge, third party devs can’t make anything new appear there. The settings menu is completely controlled by Asobo.
I guess the third party vendor could attempt to use only sim-defined control settings in their plane, so in theory everything is mapped to items that already exist in that menu, but I suspect that would limit 3rd part dev’s quite significantly. I would venture to guess every single one of them has custom variables that are not part of the sim key bind list.
Once a dev hits that wall, then they must define their own variables. They can (and do) make those variables visible through simconnect (and maybe WASM?) so external tools can access them. But once you get here, then you are talking Mobiflight, Spad.Next, Axis-and-Ohs, etc…
It’s all been said really. This is a major limitation of the in sim bindings. If not available there it’s external tool or nothing i’m afraid. So you have a choice of putting up with the limitation or doing something about it by using a sim connect control app. This is why so many of us go the external control route.