key bindings - more axis commands for several light brightness / contrast settings

[v2tec]

all mentioned in the topic

[Schlomo1933]

+1 

Pls make all buttons possible for 2 and 3 position switches, and all rotary’s bindable as an axis. 
 

and pls make the switches with a safetycap so that the cap will open automatically when u flip the switch . Like Heatblur did in the F14. 
it makes no sense if we need to flip a switch, that we need to waste a second switch just to open and close the safetycap 

How it is at the moment is just not more up to date. Many users build for their favorite modules homecockpits. To use the mouse or the keyboard in flight is just nerve testing.
But this is not only related for the BS3 , it’s related to all modules.

Edited December 24, 2022 by Schlomo1933

[ROOBi]

Am 25.12.2022 um 00:38 schrieb Schlomo1933:

+1 

Pls make all buttons possible for 2 and 3 position switches, and all rotary’s bindable as an axis. 
 

and pls make the switches with a safetycap so that the cap will open automatically when u flip the switch . Like Heatblur did in the F14. 
it makes no sense if we need to flip a switch, that we need to waste a second switch just to open and close the safetycap 

How it is at the moment is just not more up to date. Many users build for their favorite modules homecockpits. To use the mouse or the keyboard in flight is just nerve testing.
But this is not only related for the BS3 , it’s related to all modules.

 

If possible adjust the "ratio""duration""resolution" of the Keybindings like RCtrl+RShift+H or RShift+RAlt+H for the HUD Brightness, so that we can press the Keys and the brightness doesn't go that fast up or down with the keystroke, as for now we have still to use the mose wheel to fine rotate the Brightness knops? I hope it's good enogh weitten, english is not my native language. Plese don't forget the other Brightness knobs as well, pretty please

[Poor Yurik]

100% agree with the OP. There are a ton of 0-100 brightness knobs in the cockpit. All should be bindable to an axis. My two big axis dials on my Virpil Control Panel #1 have zero use in the BS3 (my favorite module) right now

[Temetre]

I got VKBs in a HOTAS setup, I would love if I could use their little "throttle levers" to control stuff like the 3-position switch on the F-18 flap selector, the F-16 autopilot switches, maybe landing gerar.

Maybe I should check if external software like joy2key or so has the function, but it would be nice to have a way to do this ingame. At least for "big" stuff you commonly use. Or a function to set up axis to do action at certain positions, inside of the game?

Edited May 1, 2023 by Temetre

[LeCuvier]

@v2tec: I see 4 lighting control knobs in the cockpit. I could probably create bindings for axis commands by adding 4 lines to "default.lua". Would you be willing to a little LUA editing (just copying and pasting 4 lines of code)?
If you want to wait for ED doing this: good luck!

[xfirf]

Yes please:

• HUD Brightness
• HMD Brightness
• IT-23 Brightness
• IT-23 Contrast
• ABRIS Brightness
• ABRIS Cursor Control

[LeCuvier]

I have added these lines to "default.lua":

{action = device_commands.Button_1, cockpit_device_id = devices.HUD, name = _('HUD Brightness Axis')},
{action = device_commands.Button_1, cockpit_device_id = devices.HELMET, name = _('Helmet Device Brightness Axis')},
{action = device_commands.Button_2, cockpit_device_id = devices.SHKVAL, name = _('IT-23 Display Brightness Axis')},
{action = device_commands.Button_3, cockpit_device_id = devices.SHKVAL, name = _('IT-23 Display Contrast Axis')},
{action = device_commands.Button_8, cockpit_device_id = devices.ABRIS, name = _('ABRIS Brightness Axis')},
{action = device_commands.Button_6, cockpit_device_id = devices.ABRIS, name = _('ABRIS Cursor Axis')},

Results:
HUD Brightness: Works but uses only upper 50% of input range; set to INVERT
HMD Brightness: Works fine; set to INVERT
IT-23 Brightness: Works but uses only upper 50% of input range; set to INVERT
IT-23 Contrast: Works fine
ABRIS Brightness: Works but uses only upper 50% of input range; set to INVERT
ABRIS Cursor Control : Seems to rotate the knob (Set to INVERT!), you have to test as I'm not familiar with that functionality

As you see, some of the knobs use only 50% of the slider signal range. There is nothing I can do about that.

The lines of code must be inserted near the end of the file, after this line:

axisCommands = {

but before these lines:

},
}

 

[xfirf]

vor 1 Stunde schrieb LeCuvier:

I have added these lines to "default.lua":

{action = device_commands.Button_1, cockpit_device_id = devices.HUD, name = _('HUD Brightness Axis')},
{action = device_commands.Button_1, cockpit_device_id = devices.HELMET, name = _('Helmet Device Brightness Axis')},
{action = device_commands.Button_2, cockpit_device_id = devices.SHKVAL, name = _('IT-23 Display Brightness Axis')},
{action = device_commands.Button_3, cockpit_device_id = devices.SHKVAL, name = _('IT-23 Display Contrast Axis')},
{action = device_commands.Button_8, cockpit_device_id = devices.ABRIS, name = _('ABRIS Brightness Axis')},
{action = device_commands.Button_6, cockpit_device_id = devices.ABRIS, name = _('ABRIS Cursor Axis')},

Results:
HUD Brightness: Works but uses only upper 50% of input range; set to INVERT
HMD Brightness: Works fine; set to INVERT
IT-23 Brightness: Works but uses only upper 50% of input range; set to INVERT
IT-23 Contrast: Works fine
ABRIS Brightness: Works but uses only upper 50% of input range; set to INVERT
ABRIS Cursor Control : Seems to rotate the knob (Set to INVERT!), you have to test as I'm not familiar with that functionality

As you see, some of the knobs use only 50% of the slider signal range. There is nothing I can do about that.

The lines of code must be inserted near the end of the file, after this line:

axisCommands = {

but before these lines:

},
}

 

Could you please provide the filepath too?

[LeCuvier]

File path is "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Ka-50_3\Input\ka-50_3\joystick"

[MortalMando]

The external lights don’t have separate on - off buttons but on that does both. So instead of a ON/OFF It would be great to have ON or OFF for:
 

Rotor  tip lights, navigation light, formation lights, anticollision. 
 

concerning Nav and Form lights, since it’s a 100%/50%/10% (if I remember correctly) some bindings for „switch up, down“ would be appreciated. 

[LeCuvier]

For Rotor Tip and Anti-Collision Lights, it's possible to create separate ON and OFF pushbutton commands, or commands for 2-position switches, by simple LUA editiing.
For the multi-position commands I don't see a way to do that.

[MarcT-NL]

Don't forget axis's for the radio-volumes

[Sindbadius]

+1 for axis commands

[Poor Yurik]

On 5/24/2023 at 10:47 AM, LeCuvier said:

I have added these lines to "default.lua":

{action = device_commands.Button_1, cockpit_device_id = devices.HUD, name = _('HUD Brightness Axis')},
{action = device_commands.Button_1, cockpit_device_id = devices.HELMET, name = _('Helmet Device Brightness Axis')},
{action = device_commands.Button_2, cockpit_device_id = devices.SHKVAL, name = _('IT-23 Display Brightness Axis')},
{action = device_commands.Button_3, cockpit_device_id = devices.SHKVAL, name = _('IT-23 Display Contrast Axis')},
{action = device_commands.Button_8, cockpit_device_id = devices.ABRIS, name = _('ABRIS Brightness Axis')},
{action = device_commands.Button_6, cockpit_device_id = devices.ABRIS, name = _('ABRIS Cursor Axis')},

Results:
HUD Brightness: Works but uses only upper 50% of input range; set to INVERT
HMD Brightness: Works fine; set to INVERT
IT-23 Brightness: Works but uses only upper 50% of input range; set to INVERT
IT-23 Contrast: Works fine
ABRIS Brightness: Works but uses only upper 50% of input range; set to INVERT
ABRIS Cursor Control : Seems to rotate the knob (Set to INVERT!), you have to test as I'm not familiar with that functionality

As you see, some of the knobs use only 50% of the slider signal range. There is nothing I can do about that.

The lines of code must be inserted near the end of the file, after this line:

axisCommands = {

but before these lines:

},
}

 

This is great, unfortunately I believe we need an official solution as editing this file likely will prevent us from joining protected multiplayer servers. I ran into a similar issue when I edited my ABRIS behavior in the LUA to speed up the slew speed and had to revert it.

ED: please please please add Axis binds for the Black Shark 3's dials. So many button boxes have dials on them that would be perfect for the Shark.

Edited November 22, 2023 by Poor Yurik

[LeCuvier]

4 hours ago, Poor Yurik said:

This is great, unfortunately I believe we need an official solution as editing this file likely will prevent us from joining protected multiplayer servers. I ran into a similar issue when I edited my ABRIS behavior in the LUA to speed up the slew speed and had to revert it.

ED: please please please add Axis binds for the Black Shark 3's dials. So many button boxes have dials on them that would be perfect for the Shark.

 

In my experience, user-edited "default.lua" cause no problem with MP integrity check.

Note: Nowadys I have all my edits in separate "default.lua" under "Saved Games", using the solution developed by @Quaggles.
You can find this here: https://forum.dcs.world/topic/270487-quaggles-dcs-input-command-injector-mod-v1010-store-custom-input-commands-safely-in-saved-games-instead-of-merging-them-with-developer-changes-each-update/#elControls_4651461_menu
This solution uses a modified "Data.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Scripts\Input".
I have tried this in MP and it passes integrity check, even if the server specifies "pure script".

[Poor Yurik]

On 11/22/2023 at 3:13 AM, LeCuvier said:

In my experience, user-edited "default.lua" cause no problem with MP integrity check.

Note: Nowadys I have all my edits in separate "default.lua" under "Saved Games", using the solution developed by @Quaggles.
You can find this here: https://forum.dcs.world/topic/270487-quaggles-dcs-input-command-injector-mod-v1010-store-custom-input-commands-safely-in-saved-games-instead-of-merging-them-with-developer-changes-each-update/#elControls_4651461_menu
This solution uses a modified "Data.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Scripts\Input".
I have tried this in MP and it passes integrity check, even if the server specifies "pure script".

I will try that, thank you! Still hoping ultimately for an official solution so that the range of motion issues you listed are corrected as well.