DOCUMENTATION: DCS Advanced Input Configuration

[H-var]

Dear forums.eagle.ru,

 

I searched through this forum and, unfortunately, was not able to find a proper, full documentation for an advanced input configuration. I would like to get an explanatory documentation for each command, like "iCommandPlaneStabHorizon", for example, and for each condition, like "pressed", "up", "down", and so on. Where can the most complete documentation can be found? Does it even exist? If no, can you create it?

 

Thank you for your kind help.

 

Best regards,

WoAyumi

Edited March 22, 2014 by H-var

[tietze]

Where can the most complete documentation can be found? Does it even exist? If no, can you create it?

 

If you do a bit of research in the lua files you can get some of the way. You still have to work some by trial and error. This is aimed at binding specific states of clickable switches in the cockpit to keys for the KA-50, but it works the same way with other modules. Happy hunting!

 

Hi,

 

The main problem I had was the fact most commands in BS toggle the switch rather than set its state. I realised though that most switches can easily be set to toggle using info from the clickabledata.lua and devices.lua

 

You then edit the appropriate controls lua file (Saved Games...\config\input\KA-50...

 

Here is an example from mine:

 

{combos = {{key = "JOY_BTN22"}, }, down = 3004, up = 3004, cockpit_device_id = 12, value_down = 0.2, value_up = 0.1, name = "Burst length - long", category = "Ins Weapons Status and Control Panel PUI-800"},

{combos = {{key = "JOY_BTN23"}, }, down = 3004, up = 3004, cockpit_device_id = 12, value_down = 0, value_up = 0.1, name = "Burst length - short", category = "Ins Weapons Status and Control Panel PUI-800"},

 

You can create this by looking up the control you want in clickabledata.lua and then cross referencing the devices.lua and command_defs.lua files to get the values.

 

 

This is the appropriate clickabledata line:

 

elements["SR-PTR"] = {class = {class_type.TUMB,class_type.TUMB}, hint = LOCALIZE("Weapon mode switch - Burst Length"), device = devices.WEAP_INTERFACE, action = {device_commands.Button_4,device_commands.Button_4} , stop_action = {}, arg = {400,400}, arg_value = {-direction*0.1,direction*0.1}, arg_lim = {{0.0, 0.2},{0.0, 0.2}}, use_OBB = true, updatable = true}

 

 

and from devices.lua:

 

devices["WEAP_INTERFACE"] = 12

 

 

The final relevant cross referencing is the device)commands.Button_4 being equal to 3004. You don't need to cross ref it every time as it is simply 3000 plus the button number. The relevant info is in command_defs.lua towards the end...

 

start_command = 3000

device_commands =

{

Button_1 = start_command + 1;

Button_2 = start_command + 2;

Button_3 = start_command + 3;

Button_4 = start_command + 4;

..........

 

 

Try as I might though, I cannot find a way of setting the AP route mode, I can only toggle it on/off - it isn't in clickable data. This is really annoying me so if anyone knows how to, please enlighten me :-)

 

I haven't tried but I wonder whether you can map a single 'joybtn' to two outputs - the first the cover and the second the switch.

The HELIOS software is quite good and can solve the issue of flipping the cover when you move the switch. However, I could not get the states of the switches to sync at the start of the mission so I abandonned it.

 

PM

 

Link: http://forums.eagle.ru/showthread.php?t=89226#16