Bonanza and Baron starters
-
Best practice on how to map the starter on the HC Alpha (or similar hardware)? I ask this question, as it seems some users have a problem starting the engines due to how the hardware is mapped.
-
You can either use the L:Vars for each magneto switch, L:BKSQ_IgnitionPosition_1 (range 0-4), or you can just map the native K:Events for the magneto and starter controls, such as K:MAGNETO1_INCR, or K:SET_STARTER1_HELD. Hope that helps.
-
Thanks. I'm currently using the K:SET_STARTER1_HELD, but while the button is holding in animation, I don't think it's held as 'in the starter motor is continuing to run', as in the same way if I'm using the mouse to hold the starter.
-
Sorry I don't quiet understand what you're seeing. The magneto switch is visually held in the start position, and the starter is not running, or the other way around?
-
When using the mouse, the starter seems to send a command every 2 seconds. When using the hardware starter mapped with K:SET_STARTER1_HELD, it only fires once for 2 seconds, but the animated switch in the virtual cockpit is still showing in starter position (just as when using the mouse).
-
Thanks for the explanation. I'm using the same event, and I don't seem to have that problem, but I have a hunch about what might be causing it. I made this change a while ago to my aircraft, but it hasn't made it to a Bonanza update yet. If you want to give it a shot, change the "starter_time" value in the aircraft's engines.cfg to 30, or 60 (seconds). That might stop at least one of the effects you're seeing.
-
And now it works! Thanks.
Note: All variations need to be modified (TC, standard, wingtip...) and I needed a restart of both MSFS and the computer.
-
@meh1951 this solution works just fine. Thank you!
I just changed it a little bit in order to use the button held and button release events instead.
note: disregard the LOCAL:JOY_0X07380XA221_BUTTON_36 condition, it's an internal solution of mine to reuse the same button for multiple functions
