VS increase / decrease defualt msfs keybinds
-
Have you tried enabling the "Control ALT SEL with Hardware Events" option on the tablet to see if that makes any difference?
-
That definitely worked, unfortunately now I can't change the Baro with my mouse. Is there a way around this? Or is there a native msfs keybind that allows for hardware mapping?
@FakeWayne I'm not looking at the simulator's menu right now, but there should be events with roughly the names
KOHLSMAN_INC, andKOHLSMAN_DEC. I hope that helps! -
So yeah, when you search for a native msfs Kohlsman, "Increase Altimeter" and "Decrease Altimeter" are what come up, and these events can successfully be mapped with hardware. Unfortunately, the events only change the actual altimeter and not the Baro on the S-TEC Altitude/Vertical Speed Select Programmer.
-
So yeah, when you search for a native msfs Kohlsman, "Increase Altimeter" and "Decrease Altimeter" are what come up, and these events can successfully be mapped with hardware. Unfortunately, the events only change the actual altimeter and not the Baro on the S-TEC Altitude/Vertical Speed Select Programmer.
@FakeWayne Ah, yes, that makes sense, as the autopilot altimeter is altimeter index 2. I was just saying recently that it's a real shame Asobo neglected to give us a way to input an index or input variable to the countless native events that require one. In this case, you would need to use some third party application to adjust altimeter index 2.
-
Understood. So there is no way to use the "Control ALT SEL with Hardware Events" option, while being able to just adjust the autopilot baro with a mouse?
@FakeWayne I believe you need a third party key-bind software (Axis and Ohs (AAO)/ SPAD.neXt/ FSUIPC) to bind hardware to the autopilot without enabling the setting in the tablet. This should allow the baro to remain interactable with the mouse.
-
Just to add to this...
Something I figured out last night while messing around:
If I use the mouse just once to click either up / dn on the S-Tec autopilot, thus giving it control over the VS rather than the Altitude/Vertical Speed Select Programmer, then my hardware works as intended to increase / decrease the VS. Once control is given back to the Altitude/Vertical Speed Select Programmer, the hardware no longer works.
-
It is seriously worth considering using a third party app to look after controller binds. MobiFlight is free and is what I use.
There is a small learning curve but it gives you an amazing amount of flexibility with your binds, especially with third party aircraft.
I have started adding MobiFlight presets for the Commander 114 to the HubHop repository including the S-TEC thumb wheels. This will give you a head start if you decide to give MobiFlight a go,
-
Second this. I use MobiFlight free version also. Once you get to grips with it you can do so much.
I would recommend checking out the SDK with regards to RPN also so when you look at other peoples examples it makes a bit more sense.
