How to set up toggle switches (a tutorial)

It took a while for me to find it, so here's a link to save others the hassle...

Thanks for the tutorial LeCuvier !

Thanks for the link. I lost this file a while back and couldn't find it myself.

Hi LeCuvier,

I read your tutorial for the coding. Thanks for your effort. I plan to build panels for black shark. On the last page of your tutorial you mentioned that process 5.7 will not be satisfactory for BS toggle switches, why do you think so? cause I tried the 5.7 process for the master arms toggle switch and it worked. i am just a layman, just want to know why do you think so.

Hi LeCuvier,

... i am just a layman, just want to know why do you think so.

The approach per 5.7 seems to work and it may be good enough for you, but it can be fooled so that the switch in the cockpit will be in the opposite position.

The approach per 5.8 is more rugged. I have just tested that statement a few minutes ago. Using the HMD power switch example, the approach per 5.8 would use code like this:

{down = 3002, up = 3002, value_down = 1, value_up = 0, cockpit_device_id = 23, name = _('Helmet-mounted System true  2-Pos. On/Off'), category = _('Ins Targeting Mode Controls Panel PVR')},

The command per 5.7 could be "fooled", the one per 5.8 could not.

I learned approach 5.8 when I had this problem with 5.7, and after some trial and error found 5.8.

i wonder, editing the original file for keybindings. example the su25t, adding night vision goggles.

when the game updates, then you are also a peer (uploading small parts of the game, contributing the torrent). will it also upload the edited (keyboard.lua)?

I would expect that there is integrity checking built into the process and that modified files are rejected.

LeCuvier,

I'm stuck trying to make a 3 position switch for the Mig 15 that has Gear Up/Neutral and then Down/Neutral.

This is what I've tried, but it's not being interpreted or even showing up in the in game keybind screen.

-- 2/3 Custom

{down = iCommandPlaneGearUp, up = gear_commands.Mig15_Command_LandingGearHandle, cockpit_device_id = devices.GEAR_INTERFACE, value_down = -1, value_up = 0, name = _('Gear Handle Up/Neutral'), category = {_('Left Cockpit Side')}},

{down = iCommandPlaneGearDown, up = gear_commands.Mig15_Command_LandingGearHandle, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1, value_up = 0, name = _('Gear Handle Dn/Neutral'), category = {_('Left Cockpit Side')}},

Any ideas?

thanks again!:pilotfly:

I don't have the Mig-15, so I cannot do any research. If these 2 commands don't show in the Options/Controls screen there is something fundamentally wrong. The syntax looks ok though.

Have you put the added commands in the right block (key commands)?

The command "gear_commands.Mig15_Command_LandingGearHandle" makes me wonder. Where did you find it? What I'm suspecting is that this command belongs to the device "devices.GEAR_INTERFACE" and the two other commands (iCommandPlane...) don't, and that this combination may not be allowed.

Maybe if you post the files "default.lua" and "clickabledata.lua" I can figure it out, but that's not certain as I cannot test anything.

I don't have the Mig-15, so I cannot do any research. If these 2 commands don't show in the Options/Controls screen there is something fundamentally wrong. The syntax looks ok though.

Have you put the added commands in the right block (key commands)?

The command "gear_commands.Mig15_Command_LandingGearHandle" makes me wonder. Where did you find it? What I'm suspecting is that this command belongs to the device "devices.GEAR_INTERFACE" and the two other commands (iCommandPlane...) don't, and that this combination may not be allowed.

 

Maybe if you post the files "default.lua" and "clickabledata.lua" I can figure it out, but that's not certain as I cannot test anything.

sorry took so long:

File 1:

https://www.dropbox.com/s/g11rki1npyxcxsn/clickabledata.lua?dl=0

File 2:

https://www.dropbox.com/s/zd2dkbfq3kahkpl/default.lua?dl=0

I have inserted 3 lines (starting at line 9) into "default.lua".

They should provide the following 2 commands under category "Systems":

Landing Gear Handle DOWN/NEUTRAL

Landing Gear Handle UP/NEUTRAL

Try this file please. I would expect that the commands should have at least some visible effect on the landing gear. You may have to experiment with the values for value_down and value_up.

Also, I suppose you must open the lock cover before you can use the commands. Good luck!

default.lua

I have inserted 3 lines (starting at line 9) into "default.lua".

They should provide the following 2 commands under category "Systems":

Landing Gear Handle DOWN/NEUTRAL

Landing Gear Handle UP/NEUTRAL

Try this file please. I would expect that the commands should have at least some visible effect on the landing gear. You may have to experiment with the values for value_down and value_up.

Also, I suppose you must open the lock cover before you can use the commands. Good luck!

thanks!

I'll give it a try tonight!:pilotfly:

LeCuvier

Thanks works!

Thanks for your hard work and documentation on this LeCuvier...it made making the desired modifications to my .lua files much easier to understand :pilotfly:

Thanks for your hard work and documentation on this LeCuvier...it made making the desired modifications to my .lua files much easier to understand :pilotfly:

:thumbup:

You seem to have a lot of knowledge about input and controls.

Could I change the lua files to make my devices available for binding?

You seem to have a lot of knowledge about input and controls.

Could I change the lua files to make my devices available for binding?

That's a very open question.

What kind of devices?

If these devices are game controllers you should be able to bind them mostly without changing the .lua files. .LUA editing is necessary onyl to create additional commands that for some reason the developers have omitted to create.

You seem to have a lot of knowledge about input and controls.

Could I change the lua files to make my devices available for binding?

What devices are you using that aren't mappable? I have a DIY device that DCS picks up just dandy.

That's a very open question.

What kind of devices?

If these devices are game controllers you should be able to bind them mostly without changing the .lua files. .LUA editing is necessary onyl to create additional commands that for some reason the developers have omitted to create.

What devices are you using that aren't mappable? I have a DIY device that DCS picks up just dandy.

Issue solved.

It seems some F16 MFD lua files from my older configuration were messing my curreny setups, with two more USB devices.

Thank you guys.

I am stuck with Viggen. Formerly, I did something with Mirage - it was rather easy - I could find the buttons from clickabledata.lua and do my changes accordingly. I am, however stuck with Viggen.

The clickable data looks a bit different from Mirage. For example, I would like to have separate On and Off buttons, better to map that way to Warthog HOTAS.

One example would be like radar altimeter, Barometer vs. Radar Altimeter switch. It is an On/Off toggle.

In clickabledata we have:

elements["HojdSI-PTR"] = default_2_position_tumb(_("HÖJD CISI"), devices.FLIGHTDATAUNIT, 3200, 324)

In default.lua there is:

    {combos = {{key = "X", reformers = {"RShift","RCtrl"}}}, down = 3200, cockpit_device_id = devices.FLIGHTDATAUNIT, value_down = 1.0, name = _("HÖJD CISI"), category = _("Navigation")},

I try adding the separate buttons, for example, with:

    {down = 3200, cockpit_device_id = devices.FLIGHTDATAUNIT, value_down = 1.0,   name = _('HÖJD CISI RHM - Radar Altimeter'),  category = _('Navigation')},
   {down = 3200, cockpit_device_id = devices.FLIGHTDATAUNIT, value_down = -1.0,   name = _('HÖJD CISI LD - Barometric'),  category = _('Navigation')},

I have been trying up and down putting them both to -1 or 1 respectively, the best I can achieve is two additional keybindings that just toggle the cockpit switch on and off.

Would it help to remove the original toggle mapping?

@Jyge: I don't see a solution. Although the switch visible in the cockpit has 2 stable positions, it's not implemented as it should. A correctly mplemented switch would go to the UP position on Mouse Right-Click, and DOWN on Mouse Left-Click, or vice versa.

This switch however always goes to the respective opposite position (it toggles) irrespective of which mouse button you click. The Radar Altimeter switch has the same problem. And we can still not change control bindings via Options/Controls without getting the black screen.

I'm clearly not impressed with Heatblur's implementation quality. And now they will want to sell us the F-14.... good luck!

@Jyge: I don't see a solution. Although the switch visible in the cockpit has 2 stable positions, it's not implemented as it should. A correctly mplemented switch would go to the UP position on Mouse Right-Click, and DOWN on Mouse Left-Click, or vice versa.

This switch however always goes to the respective opposite position (it toggles) irrespective of which mouse button you click. The Radar Altimeter switch has the same problem. And we can still not change control bindings via Options/Controls without getting the black screen.

 

I'm clearly not impressed with Heatblur's implementation quality. And now they will want to sell us the F-14.... good luck!

Ah, ok so I am chasing ghosts here. Damn, that's irritating. Well it is understandable in some respects as Viggen is already a bit older I think and the logic with clickable cockpits is still evolving, but yes it would be nice if they patched it to left click - right click logic.

Ah, ok so I am chasing ghosts here. Damn, that's irritating. Well it is understandable in some respects as Viggen is already a bit older I think and the logic with clickable cockpits is still evolving, but yes it would be nice if they patched it to left click - right click logic.

‘A bit older’? The Viggen is not even out of beta yet!

This left/right click issue is not unique to Viggen. Inconsistencies exist in all modules in this respect. Been discussed many times here.

‘A bit older’? The Viggen is not even out of beta yet?

This left/right click issue is not unique to Viggen. Inconsistencies exist in all modules in this respect. Been discussed many times here.

FA-18c has that, "inconsistencies". To rearrange all these, which, mind you, categorically is not a bug but a - design - wish, a design clean-up, one has to go with a fine comb through all of the present coding of all of the interface, which probably is a hell of a job. If one had to choose, we want our lightning pod, don't we.

Yes, trying to fix all the past design inconsistencies would be hell for any software engineer. These guys want to write new code - not review and correct old code written by someone else.

But it would help going forward, if ED established design rules for this kind of thing. At least then new modules would cause less user rework ("mods") and frustration, and improve custome satisfaction.

this work only with Throttle - Hotas Warthog???Cause i have an BU0836X and i want to make the same there