VS increase / decrease defualt msfs keybinds
-
I'm having trouble getting VS to increase / decrease using default msfs keybinds with my hardware. I've tried using both my Honeycomb Bravo and also my VKB STECS.
I’m not entirely sure if it’s just a nuance with the autopilot I’m not understanding, or if there is some kind of conflict / msfs weirdness at play.
I'm setting my desired altitude on the S-TEC Altitude/Vertical Speed Select Programmer, and leave the VS knob at 0. I'll then engage heading mode (which I've also bound to AP ON, to mimic the lack of an actual AP on switch), and engage VS mode. All of this works and annunciates as expected with the default msfs keybinds and my hardware.
However, once I try to increase my VS via my hardware, it becomes very hit or miss. Sometimes it engages, and sometimes it does not, and I remain in level flight. Using the mouse to click the Up / Down buttons works reliably every time.
-
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.
