Take Advantage of HOTAS Toggle Switches

[Nooch]

Hi guys,

 

 

Right now DCS doesn't allow the user to take full advantage of HOTAS toggle switches as we are limited to what's available in the "Special for joystick" section.

For example I can't use my rdr altm switch on my Warthog to toggle between baro and rdr altitude in the Hornet as it's not available in the list. I know we can edit some .lua file and add it manually but the process isn't quick and convenient at all.

 

 

So I would like to suggest something to the devs. Instead of doing things this way, why don't we have a check box in the key assignment window that, when checked, makes it work as a toggle?

Something that says "only when key is pressed" or "for HOTAS toggle switch" or something like that.

 

 

This way the user could effortlessly set anything he wants, for any aircraft. Also the devs wouldn't have to waste time adding a "special for joystick" binding list for every module. I've made a picture in gimp to illustrate exactly what I mean...

 

 

 

 

 

[Zaz0]

+1

[Emmy]

I’m confused...

 

I use the paddle switch on my TMWH as a modifier and it only functions as such while it’s being held. eg, I raise/lower my A-10C gear with the first stage of the trigger while the paddle is held in. I tune my radio presets up/down using the DMS / TMS / CMS buttons but while the paddle is held in. I also have six or seven other functions mapped that only work while the paddle switch is held in.

 

How would this work differently?

[DowntownSIX]

You're looking for the "Modifiers" menu - select the "Modifiers" from your screenshot, if I remember correctly you can select keybinds in "Shift" or "Mode". Shift initiating a shift state only while you hold the key and Mode initiating a shift state until you press the key again.

 

Apologies if that's not 100% accurate, I'm not looking at the screen right now but it should get you where you need to be.

[Nooch]

You guys didn't get it. I'm not talking about modifiers here, I know what they are. Maybe I didn't explain very well... sorry if it's the case. I will rephrase it.

 

 

Basically right now, toggle switches on your HOTAS act as button pressers if you bind them the normal way. To avoid that, and have them work as toggles, you need to use the "special for joystick" list of bindings. The problem is, what's available in there is very limited as you can see in that thread for example.

 

To avoid being limited and bind anything you want, you can always do some lua programming as shown right here. But it's complex and time consuming.

 

 

I'm asking that we get something that allows us to do just that but in the user interface so it can be quick and simple.

Edited February 11, 2019 by Nooch

[flyco]

I would support this suggestion. I routinely modded my .lua files to allow a simple On-Off switch to react in both directions. Unfortunately these are not universal, and because they are often updated as modules develop they need frequent changes.

[txmtb]

Was always in the same boat as OP with the throttle switches.

 

The solution OP suggest would make it easier for sure and has been requested for a while now.

 

Know many people refuse to use TARGET but it has it uses and this is one of them.

Started using the script from ReflexArc in this thread: https://forums.eagle.ru/showthread.php?t=226594

 

 

It allows all switches on the throttle an on/off DX switch number. So the off state can be mapped to toggle a switch back to the other position, and 3 position switches also have an off DX number so are also able to be completely mapped.

[DowntownSIX]

You guys didn't get it. I'm not talking about modifiers here, I know what they are. Maybe I didn't explain very well... sorry if it's the case. I will rephrase it.

 

 

Basically right now, toggle switches on your HOTAS act as button pressers if you bind them the normal way. To avoid that, and have them work as toggles, you need to use the "special for joystick" list of bindings. The problem is, what's available in there is very limited as you can see in that thread for example.

 

To avoid being limited and bind anything you want, you can always do some lua programming as shown right here. But it's complex and time consuming.

 

 

I'm asking that we get something that allows us to do just that but in the user interface so it can be quick and simple.

 

My bad, I haven't read your request properly.

 

I agree, it's surprising how few "special for joystick" type keybinds exist given MANY of us are using toggle switches as part of our HOTAS systems.

 

Big +1 from me.

[thezapper]

I'd love to see this functionality. The ability to fire another action when flipping a switch to off. Modifying the lua files is a pain and updates keep ruining your modifications.

 

For example, I'd like to map the EAC switch on my TM warthog to the Ka-50 laser on/off. Flip up - laser on, flip down - laser off. But currently the switch acts like a button, flip up - press and hold, flip down - release. You have to flip up and down, to turn it on, then up and down again to turn it off.

 

There should be an option to register joystick buttons as toggles, so you can assign a key bind to both the 'press' and 'release' portion of the action.

[Emmy]

You guys didn't get it. I'm not talking about modifiers here, I know what they are. Maybe I didn't explain very well... sorry if it's the case. I will rephrase it.

 

 

Basically right now, toggle switches on your HOTAS act as button pressers if you bind them the normal way. To avoid that, and have them work as toggles, you need to use the "special for joystick" list of bindings. The problem is, what's available in there is very limited as you can see in that thread for example.

 

To avoid being limited and bind anything you want, you can always do some lua programming as shown right here. But it's complex and time consuming.

 

 

I'm asking that we get something that allows us to do just that but in the user interface so it can be quick and simple.

 

 

Ah, now I get what you're saying and yes, I agree...

[ghost84]

There should be an option to register joystick buttons as toggles, so you can assign a key bind to both the 'press' and 'release' portion of the action.

This!

[Rowan]

+1 OP

[Hairysteed]

What I'd really would like is an option select whether the action is executed upon pressing or releasing the button.

 

Example:

Toggle# activated: gear up

Toggle# released: gear down

 

Or when the action is actuated by a single command

Toggle# activated: gear up/down

Toggle# released: gear up/down

[Notso]

I’m confused...

 

I use the paddle switch on my TMWH as a modifier and it only functions as such while it’s being held. eg, I raise/lower my A-10C gear with the first stage of the trigger while the paddle is held in. I tune my radio presets up/down using the DMS / TMS / CMS buttons but while the paddle is held in. I also have six or seven other functions mapped that only work while the paddle switch is held in.

 

How would this work differently?

 

That's very interesting. I hadn't thought about using the modifier function to hold the paddle switch or similar down to enable some of the normal HOTAS buttons to do double duty. This would be especially useful since I use VR.

 

As an aside, does the paddle switch do anything in the real Viper? Is it even there on the stick?

Currently I have it set to be my VR zoom. Hold it, zoom in - release it zooms back to normal.

 

FYI - I also use the WH flap switch as my gear handle up/down since the Viper uses auto-flaps and the switch is not needed.

[Tippis]

The funny thing is that this is already fully supported in the code — it's just not exposed in the binds menu and is instead left to the module makers to try to fit in based on their best guesses of what the player might want. If on-press/on-release activation options were available right in the binds menu, all those bespoke solutions would no longer need to be there since the player could use the built-in options to perfectly set it up to match their devices almost completely irrespective of how the base binds were implemented.

[Home Fries]

+1. Elegant solution.

 

The flip side would be having a "negative" checkbox with the switch being active if one or two buttons are not pressed. For example, if "Master Arm On" has the held checkbox, then "Master Arm Off" should enable the "negative" checkbox with the master arm on button selected.

[iborg]

I strongly support this suggestion as well.

[metzger]

+1!

 

There is something more, right now it work by adding an action on release. However, many times when you engage switch to "ON" after some time if you turn it OFF, the action on release doesn't work and you have to toggle the witch on off and click it with the mouse to sync and it starts to work again. So far I am unable to find what causes this or any pattern, but it seems like if it stays "ON" for certain time, then it stops working and needs to be cycled.

 

It also doesn't work after mission start before all controls are toggled. The setting to sync the controls fixes this partially but in many cases it doesn't or just messes it up even more. It also mess up air starts.

[Richard Dastardly]

The funny thing is that this is already fully supported in the code — it's just not exposed in the binds menu and is instead left to the module makers to try to fit in based on their best guesses of what the player might want. If on-press/on-release activation options were available right in the binds menu, all those bespoke solutions would no longer need to be there since the player could use the built-in options to perfectly set it up to match their devices almost completely irrespective of how the base binds were implemented.

 

Absolutely this - this is *already implemented*, the problem is the lack of keybinds *provided* for most things. Having to edit files in the install as opposed to user profile to fix it does not help matters.