Joystick Button Assignments Specific to the 146

Razalom

Genista

@stopnicki To avoid having to lower then bring back up the levers, you can change the bind setting from "On press" to "On release". That way, it works like the real thing.

jmarkows

@genista Won't this only work for startup and not shutdown?

stopnicki

@genista that is very, very helpful

stopnicki

@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!

Genista

@stopnicki you have to make sure the action type is set to "On Release". Otherwise it will indeed jump up and down !

stopnicki

@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 OFF

The 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!

muskysim

Is the there a document that lists all the variables and events that can be used to assign the MCP functions to hardware peripherals using something such as FSUIPC7
Thanks

haskell99

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.

b3lt3r

@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 :-)

jmarkows

@b3lt3r Ah, thanks for finding that. I just added to an open ticket I had with Just Flight asking if the MSFS commands worked because increase/decrease AP altitude didn't seem to be working.

haskell99

@b3lt3r You are a coding beast! Not sure I can make that work with my limited skills but gives me some ideas. Also agree, the dev had to know what VARS they are using… please share so we can make the hardware work!

Thanks.

b3lt3r

@haskell99 let me know if you get stuck and I'll drop a screenshot from Spad or maybe try and upload a snippet for the panel.

I am no beast - all trial, error and profanity - I'm certain Les O'Reilly or one of the other actual beasts on the spad discord could have done it better and faster but it works for me which is good enough (tm) :-)

The Sledge

I'm looking for the TMS Sync button mapping rather than A/P Sync.

Cheers,
Sledge

jmarkows

@the-sledge it's Toggle Afterburner On/Off in MSFS. Don't hold it when you use it, tap once to enable Sync mode and then tap again to let the AP resume.

The Sledge

@jmarkows said in Joystick Button Assignments Specific to the 146:

@the-sledge it's Toggle Afterburner On/Off in MSFS. Don't hold it when you use it, tap once to enable Sync mode and then tap again to let the AP resume.

Ah, no. As I said, I want the TMS Sync button. AFAIK it's a separate function?

Sledge

jmarkows

@the-sledge You sure did and I'm not sure how I misread that.

I don't believe I've seen a standard MSFS binding for that, if anything it's probably an LVar or similar.

The Sledge

@jmarkows It's a real pain for right-handers with a joystick and trying to use the left hand on the mouse to click a button while hand-flying. IIRC from my X-Plane days I could prob find the LVAR listening with FSUIPC.

Martyn

The TMS sync button doesn't currently have an associated MSFS control assignment. The problem we have is the very limited number of suitable assignments that we can 'hijack' for these non-default systems and controls. If you can use LVars then it's "L:R_TMS_Sync, number" (1 = button pushed).

The most significant and not-obvious (e.g. afterburner) control assignments are listed in the manual but we'll try to put together a document dedicated to all the support assignments.

ShermheadRyder

@martyn said in Joystick Button Assignments Specific to the 146:

The most significant and not-obvious (e.g. afterburner) control assignments are listed in the manual but we'll try to put together a document dedicated to all the support assignments.

This would be a massive help to SPAD.next users like me if it's not too much trouble :)