Keybindings for the MB-339

[6S.Duke]

Hi everybody,
With this post I would like to collect all your feedback to add all the keybindings necessary for using better the MB-339.
At the moment we are working to fix some annoying issues on the CDU and Custom Data Card and other issues related to the navigation, and we are finalising in parallel the flight director.
At this stage we would like to add also some new keybindings like the three position flap already introduced in our internal version of the aircraft.
Please post here your feedback so I can track better everything.
Thank you.
 
Based on your previous feedback:
* CDU keybindings (work done, to be released)
* Three position flaps (work done)
* Two detent trigger (work done)
* Radio keybindings
* HSI course/heading
* Master Caution keybinding (work done, to be released)
* Navigation Mode selector keybindings
 
 






 

Edited January 15, 2024 by 6S.Duke

[LordOrion]

If possible, try add as many "ON else OFF"  and 3 position keybinds as possible, (where applicable): they are more handy for HOTAS configurations building than dual "feature ON" / "feature OFF"  binds.

Edited October 25, 2023 by LordOrion

[6S.Duke]

If possible, try add as many "ON else OFF"  and 3 position keybinds as possible, (where applicable): they are more handy for HOTAS configurations building than dual "feature ON" / "feature OFF"  binds.

Yes, list me the commands you think are necessary and we will do our best to add them

Inviato dal mio ASUS_I005D utilizzando Tapatalk

[YSIAD_RIP]

5 hours ago, LordOrion said:

If possible, try add as many "ON else OFF"  and 3 position keybinds as possible, (where applicable): they are more handy for HOTAS configurations building than dual "feature ON" / "feature OFF"  binds.

 

Especially an ON Else OFF for AirBrake.  

{down = AirBrakeLeverOff,    up = AirBrakeLeverOn,    value_down = 0,    value_up = 1,    name = _('Airbrake Slider - Extend/Retract'),            category = {_('Flight Control'), _('Throttle Grip')}},  -- for Slider Switch on X56/X55 or any 2 Position Switch |UP = Pressed & DOWN = Released|

Edited October 25, 2023 by YSIAD_RIP

[6S.Duke]

Especially an ON Else OFF for AirBrake.  
{down = AirBrakeLeverOff,    up = AirBrakeLeverOn,    value_down = 0,    value_up = 1,    name = _('Airbrake Slider - Extend/Retract'),            category = {_('Flight Control'), _('Throttle Grip')}},  -- for Slider Switch on X56/X55 or any 2 Position Switch |UP = Pressed & DOWN = Released|

For the airbrake we have already the ON/OFF command and the "partialisation" command

Inviato dal mio ASUS_I005D utilizzando Tapatalk

[gulredrel]

I would like a keybind for the master caution/warning reset.

Binding the navigation master modes would also be great (TACAN, VOR, RNAV).

Nice to hear from bugfixing of data card and work on flight director 

Thanks

Jens

[YSIAD_RIP]

22 hours ago, 6S.Duke said:

For the airbrake we have already the ON/OFF command and the "partialisation" command

Inviato dal mio ASUS_I005D utilizzando Tapatalk
 

Hi @6S.Duke thanks but I am not sure what you mean by "partialisation" command. I did not see any reference in the bindings or the MB339 Manual.

The ON/OFF Command does not help for the toggle switch used as a flap like in the Logitech X56 throttle with a slider switch operating as an On - Else Off switch.

I am happily using Quaggles Command Input Injector so I am still pleased.  I am also looking forward to your next module.

Edited October 26, 2023 by YSIAD_RIP

[6S.Duke]

Hi @6S.Duke thanks but I am not sure what you mean by "partialisation" command. I did not see any reference in the bindings or the MB339 Manual.
The ON/OFF Command does not help for the toggle switch used as a flap like in the Logitech X56 throttle with a slider switch operating as an On - Else Off switch.
I am happily using Quaggles Command Input Injector so I am still pleased.  I am also looking forward to your next module.

Hi! There is the command extend airbrake extend and airbrake retract. Both can be mapped on the hotas.
It is not on/off but the extension/retraction is proportional to the the time you hold the button

Inviato dal mio ASUS_I005D utilizzando Tapatalk

[LordOrion]

On 10/25/2023 at 3:53 PM, 6S.Duke said:

Yes, list me the commands you think are necessary and we will do our best to add them

Inviato dal mio ASUS_I005D utilizzando Tapatalk

 

Small, non complete list:

• Nav Lights brt/dim:  add "Nav Lights Brt else Off" and  "Nav Lights Dim else Off"
• "Toggle Landing Lights switch" and "Toggle Taxi Lights switch": add "Landing Lights On else OFF" and  "Taxi Lights On else OFF"
• Master Armament On/Off: add "Master Armament On else OFF"
• Toggle fuel transfer switch: add "Fuel Tansfer Pyl else Tip"
• Toggle Windshield demist switch: add "Windshield demist switch On else Off"
• Toggle Rain RMVL: add "Rain RMVL switch On else Off"
• Toggle Navlights flash/steady switch: add  "Navlights flash else steady".
• Toggle beacon light switch: add "Beacon Light On else Off"

As a general rule of thumb, might be great if:

• For controls that can be toggled between "On or Off "(in general between "A or B"), please add a "On else Off" ( "A else B") bind.
• For controls that can be changed between "X <-> OFF <-> Y"  (between "X <-> Z<-> Y"), please add "X else Off" AND "Y else Off"  ( "X else Z" AND "Y else Z") binds.

Toggling is perfect to use when you have to deal with push buttons. However, most HOTAS sticks have 2 or 3 way switches, which whould be perfect for these kind of controls, provided we have a "X else Y" bind scheme

My english is not as good as I wish, so I hope this is clear enough for you to understand what I mean. In case just send me a PM (in Italian ).

Also (I almost forgot): please, add controls to rotate the Heading and Course knobs of HSI.

Edited October 27, 2023 by LordOrion

[gulredrel]

+1 for the course selection knob controls.

[Tusky]

En 25/10/2023 a las 8:31, 6S.Duke dijo:

* Radio kwybindings

A keybind for the channel preset knob of the AN/ARC-150(V)-2 would be appreciated. 

Edited October 30, 2023 by Tusky

[IvanK]

Course and heading selection knobs .

Master caution reset

And when the flight Director is done FD mode selectors

Edited November 20, 2023 by IvanK

[MirabelleBenou]

Would like axis for light, radios and course/heading.

Thanks !

[Mr.Jazzy]

I wish for more axis (light knobs, course heading knobs), and ability to launch aircraft without mouse interactions (some binds are missing). Also, crosshair mil pipper adjustment bindings, please.

[dresoccer4]

i just started flying this plane and was very confused I couldn't change the gunsight depression with a key binding. this is needed sorely.

also a g-force meter max/min reset

[MAXsenna]

Please add predefined keystrokes for every keybind like you had at release. You guys were the only 3rd party team, (not even ED does it), to have all the keybinds populated. This makes it so more easier to share profile for VoiceAttack, various macro keyboards and other peripherals/apps. 

Cheers! 

[scoobie]

There's something weird going on... maybe people don't know about "button off" feature? ED didn't advertise it, so... maybe?

"Else" commands have been redundant/unneccessary since... about a year ago. Or two years, can't remember. You can create "else" commands on the fly from "stateful" commands - any "else" commands you like - reasonable ones or crazy ones, you choose. Stateful commands are those which set an in-cockpit control to an explicit position, for example: "Master Arm - ARM" and "Master Arm - SAFE". They're not "relative", like "next position", "increase", "toggle", but explicit - or "stateful".

On top of that, the last time I checked "else" commands were still bugged. They are prone to "falling asleep", they WON'T react if you switch your toggle switch "ON" (it's got to be "ON"), then, for example, jump out of the cockpit with "F2" key, then jump back into the cockpit with "F1" and switch your toggle switch to "OFF". This "OFF" movement will be ignored. You now have to switch it back to "ON" (this "wakes up" the switch), and now again to "OFF".
In other words, DCS ignores ON->OFF transition sometimes. It never ignores OFF->ON transition, though.
There are more situation when "else" commands fall asleep, I think it's got something to do with "cockpit losing focus", but I've never exactly put my finger on it.
Stateful commands, in turn, are not bugged, they work every time.

For example, bind "Master Arm - ARM" to one of your toggle switches. Normal thing, no explanations needed.
And now "Master Arm - SAFE": bind it to THE SAME button, a "conflict" will be displayed (it will read that this button has been already assigned to "Master Arm - ARM"), don't worry about it, just click where the window shows "JOY_BTN15" (or whatever button that is), the list will unfold, now find "JOY_BTN15_OFF" and click it. There you go - your "else" command is ready.

The module authors only need to provide "stateful" commands. And "relative" commands, but that's a different topic.

Let's say I want to have flaps lever, which goes in 3 positions: "UP", "HALF", "DOWN".
Let's say my 3-way toggle switch (ON-OFF-ON type) is buttons 15 and 16 - switch up is button 15 pressed, switch down is button 16 pressed, switch in the mid position - both buttons are off.
Here's how the bindings will eventually look like:

Flaps UP: JOY_BTN15
Flaps HALF: JOY_BTN15_OFF, JOY_BTN16_OFF
Flaps DOWN: JOY_BTN16

For 3-way latching toggle switches you can even make weird assignments, if you choose to. For example: gear up/down (the upper "half" of the switch) combined with "landing light on/off" (the lower "half" of the switch). When the switch is up, gear is up. Switch it to the middle position - gear goes down. Switch it further to down position - gear is still down, but now landing light goes on.
You can mix 2 things that are related to each other - like in this example - or you can mix things mutually exclusive, if you like. For example AAR Fuel transfer ON/OFF and HUD approach mode OFF/ON - provided you don't often AAR while on the approach to the runway This way you may utilize a 3-way switch for 2 different things. I've just done it like this for Mirage F1 - had a spare 3-way switch. If it hadn't been for the "button off" feature in DCS, I would have NEVER been able to do it (without tinkering with Lua files, which some people just refuse to do).

 

Edited April 4, 2024 by scoobie

[LordOrion]

On 4/4/2024 at 8:35 AM, scoobie said:

There's something weird going on... maybe people don't know about "button off" feature? ED didn't advertise it, so... maybe?

"Else" commands have been redundant/unneccessary since... about a year ago. Or two years, can't remember. You can create "else" commands on the fly from "stateful" commands - any "else" commands you like - reasonable ones or crazy ones, you choose. Stateful commands are those which set an in-cockpit control to an explicit position, for example: "Master Arm - ARM" and "Master Arm - SAFE". They're not "relative", like "next position", "increase", "toggle", but explicit - or "stateful".

On top of that, the last time I checked "else" commands were still bugged. They are prone to "falling asleep", they WON'T react if you switch your toggle switch "ON" (it's got to be "ON"), then, for example, jump out of the cockpit with "F2" key, then jump back into the cockpit with "F1" and switch your toggle switch to "OFF". This "OFF" movement will be ignored. You now have to switch it back to "ON" (this "wakes up" the switch), and now again to "OFF".
In other words, DCS ignores ON->OFF transition sometimes. It never ignores OFF->ON transition, though.
There are more situation when "else" commands fall asleep, I think it's got something to do with "cockpit losing focus", but I've never exactly put my finger on it.
Stateful commands, in turn, are not bugged, they work every time.

For example, bind "Master Arm - ARM" to one of your toggle switches. Normal thing, no explanations needed.
And now "Master Arm - SAFE": bind it to THE SAME button, a "conflict" will be displayed (it will read that this button has been already assigned to "Master Arm - ARM"), don't worry about it, just click where the window shows "JOY_BTN15" (or whatever button that is), the list will unfold, now find "JOY_BTN15_OFF" and click it. There you go - your "else" command is ready.

The module authors only need to provide "stateful" commands. And "relative" commands, but that's a different topic.

Let's say I want to have flaps lever, which goes in 3 positions: "UP", "HALF", "DOWN".
Let's say my 3-way toggle switch (ON-OFF-ON type) is buttons 15 and 16 - switch up is button 15 pressed, switch down is button 16 pressed, switch in the mid position - both buttons are off.
Here's how the bindings will eventually look like:

Flaps UP: JOY_BTN15
Flaps HALF: JOY_BTN15_OFF, JOY_BTN16_OFF
Flaps DOWN: JOY_BTN16

For 3-way latching toggle switches you can even make weird assignments, if you choose to. For example: gear up/down (the upper "half" of the switch) combined with "landing light on/off" (the lower "half" of the switch). When the switch is up, gear is up. Switch it to the middle position - gear goes down. Switch it further to down position - gear is still down, but now landing light goes on.
You can mix 2 things that are related to each other - like in this example - or you can mix things mutually exclusive, if you like. For example AAR Fuel transfer ON/OFF and HUD approach mode OFF/ON - provided you don't often AAR while on the approach to the runway This way you may utilize a 3-way switch for 2 different things. I've just done it like this for Mirage F1 - had a spare 3-way switch. If it hadn't been for the "button off" feature in DCS, I would have NEVER been able to do it (without tinkering with Lua files, which some people just refuse to do).

 

 

It would have been very nice to know before... thank you!

[Tusky]

Any chance to have more key bindings in the next patch?

[Esa Ahonen]

Just bought this module and found out many of the binds are just toggles while I would like to use two or three way switches for them. When are the changes discussed here actually coming?

[6S.Duke]

Just bought this module and found out many of the binds are just toggles while I would like to use two or three way switches for them. When are the changes discussed here actually coming?

hi, they are planned.

Inviato dal mio SM-F731B utilizzando Tapatalk

Sorry but we worked to add other features and to fix critical issues recently so the keybindings priority changed

Inviato dal mio SM-F731B utilizzando Tapatalk

[Esa Ahonen]

I understood from this thread that they have been planned but I was interested if you have any estimate when they will actually be available?

[virgo47]

I'm surprised how many bindings seem to be missing - altimeter pressure inc/dec, depression thumb controls, sight brightness inc/dec, taxi/landing lights are only toggle, no 3 distinct positions (e.g. for k-switches on STECS)... I was nicely surprised by this module at first, the manual started very well, training missions are nicely voiced, but bindings are a weaker part of the module and so far I struggle how to add missing stuff with Quaggle.

Inspired by the Macro_sequencies.lua:

push_start_command(1.2,	{device = devices.SWITCHES,		action = TaxiLandingLight,		value = -1.0,   message = _("TAXI/LANDING Light Switch - TAXI"), message_timeout = short_message_timeout})

I tried to add this under Saved Games dcs folder - InputCommands\MB-339\Input\MB-339A\joystick\default.lua - this copies the structure from the installation directory:

{cockpit_device_id = devices.SWITCHES, down = TaxiLandingLight, value_down = 0, name = _('TAXI/LANDING Light Switch - OFF'), category = {_('Anti-Ice System'), _('Custom')}},

But nothing happened - the command was not added to the Controls options. I have other Quaggle stuff that works, so either I'm doing something wrong or the module does something differently. I even tried to just copy a line from joystick/default.lua from the module with a different name, but it doesn't work - the name does not appear.