Autopilot altitude select bindings
-
@Dingle You can also bind axis in Mobiflight, but it can be quite fiddly if you are not used to playing with that sort of thing.
You can always just use a combination of ingame binding for the basic axis you don't need to change for every plane anyways and Mobiflight more plane specific things. -
@Avionic I would be happy to fiddle to have it all in one place. Do you have a place to start fiddling? I only saw a binding for throttle that works in MSFS 2024, so there must be another way to to it
@Dingle Need to figure out how many bits or resolution the specific sensor on your axis is.
Mobiflight has no built in calibration - and everything is RPN which can be confusing if you have never heard about that.
Thankfully, there is now a tool to help you and Mobiflight can show you the raw value of your axis if you don't already know it
https://hubhop.mobiflight.com/tools/
Add a 1 and a 2 and voila you have your axis in Mobiflight now.@ 4.0002 / 0 max 16383 min (>K:THROTTLE1_SET) @ 4.0002 / 0 max 16383 min (>K:THROTTLE2_SET)
For my VKB STECS it is a 16 bit axis, which means it goes from 0 to 65535.
Hope it helps.
-
@Avionic Yes, it really does help big time.
So MSFS uses 14Bit for inputs in general? -> Okay, found that, with the tool you mentioned its obvious it is not in general the case!
Thanks a lot! -
B Black Square referenced this topic on
-
Greetings. Apparently I have the same issue when using a Honeycomb throttle with the Starship in MSFS2020. I do have The latest FSUIPC at my disposal. Is there a workable solution for somebody who is not quite as savvy with all the tech talk being thrown around. I’ll come around at some point but right now this is all Greek to me.
-
Greetings. Apparently I have the same issue when using a Honeycomb throttle with the Starship in MSFS2020. I do have The latest FSUIPC at my disposal. Is there a workable solution for somebody who is not quite as savvy with all the tech talk being thrown around. I’ll come around at some point but right now this is all Greek to me.
@lawndart I know the above thread looks daunting, but the only thing you should need to do in FSUIPC is send these two HTML events (sometimes called an "H:Event"):
H:ALT_AltitudeSelectKnob_Inc_1, andH:ALT_AltitudeSelectKnob_Dec_1. I'm not an FSUIPC expert, but I know this is possible using the program discussed here, if there is not an even easier way now. -
@Black-Square we have made progress but progress has bled over and made other things a bit flakey.
The Honeycomb unit has a mode switch that sets the bug to be modified...
IAS, CRS, HDG, VS, ALT
There exists a file for Black Square that already has the events in it.... maybe.
BS STARSHIP ALTITUDE SELECTOR INC and ...DECREASE
This has the desired effect that it changes the altitude bug but it also changes the altitude bug when in every previously isolated mode as stated above.
It's like there should be something that says IF A AND B THEN C.
-
@Black-Square we have made progress but progress has bled over and made other things a bit flakey.
The Honeycomb unit has a mode switch that sets the bug to be modified...
IAS, CRS, HDG, VS, ALT
There exists a file for Black Square that already has the events in it.... maybe.
BS STARSHIP ALTITUDE SELECTOR INC and ...DECREASE
This has the desired effect that it changes the altitude bug but it also changes the altitude bug when in every previously isolated mode as stated above.
It's like there should be something that says IF A AND B THEN C.
@lawndart Interesting. That sounds like a very solvable problem. Just to be clear, you're not suggesting that it's anything I need to implement, right? This sounds entirely like a scripting issue in SPAD/FSUIPC/Mobi, or whatever you're using.
-
@Black-Square I am stuck. I fix one thing, I break another. I am sure this can all be done via FSUIPC but I am going to have to learn a few things before I solve the problem.