Autopilot altitude select bindings
-
Ah, that's because you won't find them there. Those are custom events that I've created specifically for Starship, and you will need to use some 3rd party hardware binding software to utilize them.
-
You can also increment/decrement LVAR:bksq_Altitude_Preselect_1 by 30.48. The LVAR is in meters, 30.48 meters = 100 ft.
-
That might not work in all scenarios, so just do so at your own risk. Also, if you're reading from that variable, you should be able to get the correct unit out of it by specifying "FEET" when you request it.
-
Ah, that's because you won't find them there. Those are custom events that I've created specifically for Starship, and you will need to use some 3rd party hardware binding software to utilize them.
@Black-Square said in Autopilot altitude select bindings:
Ah, that's because you won't find them there. Those are custom events that I've created specifically for Starship, and you will need to use some 3rd party hardware binding software to utilize them.
Is there any way for you to make it work with the built-in bindings, or any special reason it can’t work for altitude? It would be convenient if Starship could use these standard controls for AP like most other aircraft (including Velocity), as far as I know they all use that same mapping. My standard vertical speed and heading bug mapping works as is in Starship. I’m not even sure how to bind custom events to be honest, or if this is going to prevent me from using the same knob for other aircraft.
-
I might revisit this again specifically for Starship, but intercepting those inputs is a dangerous game in MSFS. Intercepting any control input involves a very convoluted system of abstraction, but it can sometimes have unintended results. Intercepting the autopilot inputs is even more so, judging by what I've seen in other code. I'll look into it.
-
Using SPAD.NeXT I have been able to get most of the autopilot binds to work with my Honeycomb Bravo, with the exception of Altitude Select - not sure what the issue is - has anyone got it to work in 2020 or 2024?
-
You're speaking of H:ALT_AltitudeSelectKnob_Inc_1? That's the event copied directly from the code, so it should be guaranteed to work if the others do. (always a dangerous thing for a developer to say)
-
You're speaking of H:ALT_AltitudeSelectKnob_Inc_1? That's the event copied directly from the code, so it should be guaranteed to work if the others do. (always a dangerous thing for a developer to say)
@Black-Square Yes that is the one - I am new to SPAD but the others are all working (entered the same way). Will try again today.
Each time I create a new event for the two encoders and just copy/paste the code from the manuall - works on literally all the other custom events I have added - not sure why this one is weird unless I maybe have a conflicting bind in MSFS itself (haven't found one).
-
@Black-Square Yes that is the one - I am new to SPAD but the others are all working (entered the same way). Will try again today.
Each time I create a new event for the two encoders and just copy/paste the code from the manuall - works on literally all the other custom events I have added - not sure why this one is weird unless I maybe have a conflicting bind in MSFS itself (haven't found one).
@Callsign_DISCO said in Autopilot altitude select bindings:
@Black-Square Yes that is the one - I am new to SPAD but the others are all working (entered the same way). Will try again today.
Each time I create a new event for the two encoders and just copy/paste the code from the manuall - works on literally all the other custom events I have added - not sure why this one is weird unless I maybe have a conflicting bind in MSFS itself (haven't found one).
There won't be conflicting binds unless you have created them. These are unique to Starship. If you created them using the client events area it should be a simple matter of binding those actions to your physical control and then in SPAD you can use the :Show Log" button and spin your control. See what command it's issuing, might help you diag what's going on and make sure your encoder is working as expected.
-
The conflict could be with something else setting the altitude target via the native events, perhaps? Just an idea.
-
Removed possible conflicting binds that could be in 2020 and 2024 - get all but ALT SEL to work in 2020, but no function in 2024 - this is on the free trial of SPAD.neXt but shouldn't be an issue.
Have tried Set and Increment with values of 0, 1, 100, etc. Pretty sure it is just my inexperience with SPAD and 2024 but a little frustrated.
-
Hopefully someone else with more SPAD experience will chime in, but perhaps this post, or this thread might have something to do with it?
