Toggle buttons

[Abburo]

Hello ED,

 

While I do appreciate the key customization flexibility that is currently in place with all modules, I am still wondering if you can consider adding a new feature to that menu so that a TOGGLE or HOLD option to be available where needed.

 

Reason for request:

Those of us which are using various controllers for custom builds can benefit and can use fewer controller inputs to achieve the same functionality.

 

Example for Airbrake:

- current implementation - Airbrake ON - 1 controller input (could be considered as default TOGGLE)

...................................- Airbrake OFF - 1 controller input (could be considered as default TOGGLE)

 

- proposed implementation - Airbrake ON (as HOLD) - 1 controller input

.......................................- Airbrake OFF - no input - just release the above button/switch

 

So, in the first situation there are 2 inputs used to achieve same functionality as in the second option with only one input.

Pumps, lights, APUs.. and many others could be easily adapted into a more ergonomic manner.

 

I am fully aware this feature could be already achieved by adding them in .LUA files. However changing LUAs is not straightforward for all users and more than that, they are subject of altering during updates.

I could actively participate in LUA adaptions if ED officials decides to add a GUI implementation to the already possible feature.

 

Thank you,

Edited April 25, 2018 by Abburo

[uri_ba]

That's not the "correct way" to do it.

Airbreaks work differently on different aircraft. And the keys should always reflect it.

 

For example, A-10 has springy "Open" where the airbreaks open as long as you hold the switch. Once released, airbreaks hold position. The CLOSE switch does the same, as long as it is pressed, airbreaks will close. (This switch is normal switch). F-16 works the same way.

 

The M2K is also correctly implemnted. It only has OPEN and CLOSED position (no middle way), and two SB switch options, MON where speed breaks are OPEN when pressed, and ON where speed breaks are also open. The middle position OFF has them closed.

 

So a correct thing will be to allow via the UI to preform "on release" actions.

This way, you should be able to assign ON-open OFF-closed on your hotas for your own preference.

 

It's currently available only by manually editing the input Lua files.

Again, the implementation is different between modules. Some allow those type of settings. Personally, I would find this more useful on Radar ON/OFF for FC3 aircraft.

[Insonia]

https://forums.eagle.ru/showthread.php?t=89226

 

i think

down = AirbrakeON, up=AirbrakeOFF is what you looking for

 

ic.

GUI feature..

Edited April 25, 2018 by Insonia

[Abburo]

It was just an example and I also mentioned where applicable. Please try be more constructive :D. By starting with "not corect way" you just destroyed initial idea :) :) :)

[Abburo]

https://forums.eagle.ru/showthread.php?t=89226

 

i think

down = AirbrakeON, up=AirbrakeOFF is what you looking for

 

Yes, you are right, I already mentioned ... pffff :pilotfly:

[David OC]

Your asking for the different lua switches to be standard for all modules and to have the flies in place already, this would allow any home built pit to easily set their pit for the IFFCC 3 way switch and not rely on DCS BIOS or the a controller software to modify what the switch does (Held) (momentary) or on release.

 

I did consider playing with some switches at one point and looked a little into it, makes sense to have them toggle just like how the A-10C warthog can do this with no middle man.

 

-

Edited April 25, 2018 by David OC

[some1]

Yes, it would be great if we could assign different function to "down" button event, and "up" button event directly in the DCS GUI. This way we could program all the various hotas and physical switches without the need to edit lua files or ask 3rd party devs to create special "hotas" assignments (which they usually forget).

 

The functionality is already there in lua, just not exposed in the GUI.