Joystick Button Assignments Specific to the 146
-
Hi:
First, congratulations to JF for the new release.
Even just at first glance, it was worth the wait!Can we get some assistance with the assignments of specific 146 functions to joystick butons?
For example. Is there an assignment to "click" the throttles out of fuel cut off into idle?
Is there an assignment to select the Flight Director line up 5 degrees before take off?
Is there an assignment for the joystick "sync mode" for the autopilot?
I had found selections for all of these in my X-Plane BAe146, but I am having difficulty in MSFS.
Thank you for these and any other assignments that folks might have already found and implemented.
Regards,
Roberto -
@cygnific Thank you.
I managed to set the throttle buttons with the:
SET ENGINE "x" FUEL VALVE
bindings of MSFS.
It works like this in my Honeycomb Bravo. As the engine is revving up and N1 reaches 10%, I slide the appropriate throttle lever down into its lower button range and bring it back up into the axis range, the throttle unlatches, fuel is "ON" and engine starts.
Works great.
Now, for the Flight Director to move up 5deg (or is it 10 deg?) button, and,
for the A/P Synch button (located on the outer left side of the yoke)
I am investigating. Hopefully somebody else has already found them, because most of my flying is in VR and having such relevant buttons assigned to easily reached buttons is very helpful!
Regards,
Roberto -
-
@genista actually, I need some help.
I am not sure how to apply your suggestion.
When I select the "TOGGLE.... " as in your diagram, the in-sim lever jumps up and down betwee fuel "ON" and "OFF"If you could explain the sequence of steps for the assignment, and where you have the lever when you start an engine, that will help a lot.
Thanks! -
@jmarkows I found out that if you select
"SET ENGINE "x" FUEL VALVE" -> also with the "ON RELEASE" action type as was shown by @Genista
rather than "TOGGLE ENGINE "x" FUEL VALVE"
the button works for both ON and OFFThe way I work it is as follows.
Before start, all my throttle levers are down into the "button" area (i.e. BUTTON 25 for Throttle 1, BUTTON 26 for Throttle 2, etc. etc.)
Upon start, when N1 reaches 10%, I move the relevant throttle lever out of BUTTON "x" and into the throttle axis, and the in-sim lever goes from fuel "off" to fuel "on"
At the end of the flight, when you want to shut down the engines, you slide the throttle lever from the axis area, into the button area and the in-sim lever will go into the fuel off poistion.
Great advice from everybody on this post.
Thanks! -
That would be helpful. I use Axis & Ohs and have almost everything working except a few. One is the preselect altitude. I can set my HC Bravo to control HDG and CRS but I’ve tried every variable for ALT increment/decrement and no luck. Anybody figure that one out?
Thanks.
-
@haskell99 I got my logitech multipanel working in SPAD this morning with Alt select. Not straight forward and there's probably a better way but this is what I did:
-
Create a new local variable called bae-mcp-alt
-
Add an expression to calculate that based on the individual digits:
([LVAR:MCP_Alt_dig1] * 10000) + ([LVAR:MCP_Alt_dig2] * 1000) + ([LVAR:MCP_Alt_dig3] * 100) + ([LVAR:MCP_Alt_dig4] * 10) + [LVAR:MCP_Alt_dig5]
I could not find a simple variable in the data monitor with the aggregated value but this calculates correctly into the bae-mcp-var
- configured the ALT display on the panel with 3 events:
a). Display local:bae_mcp_alt
b). Increment MCP_Alt_sel_knob (LVAR) by 1
c). as above but decrement
note I had to set the range for sel_knob as 00-99 and allow rollover.
It took me almost 2 hours to figure this out but now I can spin the knob on my panel and it updates the sim and displays correctly so it really helps.
Side note: I have my panel thumbwheel configured to manage VS and that actually works in the BAE without needing to use the sync mode. I just enable VS in the FCP and use the wheel to dial in my desired rate which also displays in the panel under the selected alt.
I wish all devs would document all key bindings and variable as well as the FBW team do in their docs. Any team writing a product as complex as these planes must have a reference guide for new coders on the team to get up to speed with. I know documentation is boring af but it could save all of us so much time figuring this stuff out on every plane :-)
-
