New keybindings for the Ka-50.

[Crash *]

Hello.

 

 

It would be nice to have some additional keybinds for the Ka-50.

 

 

Salvo on a three way switch.

Or the position lights. Only on key for all 4 stages.:(

[Fri13]

All switches should be operable with just left click and single button too. But as well all multiple choice ones have "up/down" or "clockwise/counterclockwise" bindings, as well direct bindings.

[Kailux]

+1 on this.

 

 

Full fidelity aircraft but the button assignment is on FC3 level.

 

 

Id totally fly this bird more often but i hate putting switched up-down-up-down-up to cycle the ingame switch when i could just bind it to some 3-way switch on my THWH.

[Schlomo1933]

+1000

[metzger]

+1

[jonsky7]

+1 on this.

 

 

Full fidelity aircraft but the button assignment is on FC3 level.

 

 

Id totally fly this bird more often but i hate putting switched up-down-up-down-up to cycle the ingame switch when i could just bind it to some 3-way switch on my THWH.

 

I have some modified switches to work as toggle switches, ie the switch in the heli is operated by either moving a TMWH switch up or down, instead of having to go up-down-up to toggle the switch. The switch position can get out of sync with the heli but can be resolved by mouse clicking a cockpit switch to match the TMWH position.

I honestly can't remember if I made them or got them from somewhere else.

 

The following can to be copied and pasted into

 

DCS world/Mods/aircraft/Ka-50/input/Ka-50/joystick/default.lua

 

I just put it under the line that says:

 

keyCommands = {

 

It shouldn't alter any of your current keybinds, it will make new entries in the keybind list

 

-- Custom
{down = iCommandPlaneModeCannon, up = iCommandPlaneModeCannon, name = _('Gun Select Toggle'), category = _('Custom')},
{down = iCommandSwitchMasterArm, up = iCommandSwitchMasterArm, name = _('Master arm on/off Toggle'),  category = _('Custom')},
{down = iCommandHelicopter_Rotor_Lock, up = iCommandHelicopter_Rotor_Lock, name = _('Rotor brake On/off toggle'),  category = _('Custom')},
{down = iCommandPlaneLaserRangerOnOff, up = iCommandPlaneLaserRangerOnOff, name = _('Laser standby On/Off switch toggle'),  category = _('Custom')},
{down = iCommandPlaneWheelParkingBrake, up = iCommandPlaneWheelParkingBrake,  name = _('Wheel brake parking toggle'),  category = _('Custom')},
{down = iCommandPlane_AmmoTypeSelect, up = iCommandPlane_AmmoTypeSelect, name = _('Cannon Round Selector toggle'),  category = _('Custom')},
{down = iCommandPlaneGear, up = iCommandPlaneGear,  name = _("Gear lever toggle"),  category = _('Custom')},
{down = iCommandPlane_WeaponMode_Manual_Auto, up = iCommandPlane_WeaponMode_Manual_Auto, name = _('Weapon system control switch Manual/Auto toggle'),  category = _('Custom')},
{down = iCommandPlane_AutomaticTracking_Gunsight_switch, up = iCommandPlane_AutomaticTracking_Gunsight_switch, name = _('Automatic tracking/gun sight toggle'),  category = _('Custom')},
{down = iCommandPlane_FireRate, up = iCommandPlane_FireRate,  name = _('Cannon rate of fire setting toggle'),  category = _('Custom')},
{down = iCommandPlaneModeHelmet, up = iCommandPlaneModeHelmet,  name = _('Helmet-mounted system On/Off toggle'),  category = _('Custom')},
{down = iCommandSwitchMasterArm, up = iCommandSwitchMasterArm, name = _('Master arm on/off toggle'),  category = _('Custom')},
{down = iCommandPlane_K041_Power, up = iCommandPlane_K041_Power, name = _('K-041 Targeting system power switch Toggle'), category = _('Ins Targeting Mode Controls Panel PVR')},
{down = iCommandPlane_RouteMode, up = iCommandPlane_RouteMode, name = _('Engage/Disengage Route Mode toggle'), category = _('Ins Collective Stick')},

Edited January 8, 2020 by jonsky7

[ghost84]

+10000

 

 

Gear Up / Down should have separate key bindings.

 

And there are many more missing.

[Bourrinopathe]

Yes please! We need more key bindings.

 

As mentioned above, many essential controls are just toggle switches: landing gear, master arm, laser standby/active, etc.

 

Additionally, brightness knobs axes could also be very useful (ABRIS, HUD, etc.).

[rrohde]

Yes please! We need more key bindings.

 

As mentioned above, many essential controls are just toggle switches: landing gear, master arm, laser standby/active, etc.

 

Additionally, brightness knobs axes could also be very useful (ABRIS, HUD, etc.).

 

Totally agree! :thumbup:

[Hunter_5E]

+1

 

It would be great if we could use switches properly like in the A10C module.

 

I'd also like to see some more axes added. The Shkval is always much darker in a viewport than in cockpit for some reason so I always have to adjust brightness/contrast for it at the start of a mission. Often have to adjust it in mission as well so those axes would be very welcome.

[Crash *]

A 8-way keybind for the skhval would be up-to-date.

 

 

A laser on and a seperate laser off.

 

 

Since BS1 there are much better HOTAS on most desks, with more more switches and buttons and hats. :smartass:

[flanker0ne]

Missing axis

{action = 3001, cockpit_device_id = 7, filter = {saturationX = 1, saturationY = 0.5, deadzone = 0, invert = true, slider = true, curvature = {0}}, name = _('HUD Brightness Knob')},
{action = 3002, cockpit_device_id = 8, name = _('IT-23 TV Brightness Axis')},
{action = 3003, cockpit_device_id = 8, name = _('IT-23 TV Contrast Axis')},
{action = 3008, cockpit_device_id = 9, name = _('ABRIS Brightness Axis')},
{action = 3001, cockpit_device_id = 23, name = _('Helmet device Brightness Axis')},
{action = 3006, cockpit_device_id = 46, name = _('ADF Volume Axis')},
{action = 3002, cockpit_device_id = 49, name = _('R-828 (VHF-1) Radio Volume Axis')},

Still require some finetuning to accept secondary settings (slider, invert, saturation ecc) by default, but it work

Edited March 19, 2020 by flanker0ne

[Bourrinopathe]

What a relief!

The most annoying controls for me were the Shkval TV brightness and the Night Vision Goggles and monocle reticle brightness.

 

Thank you, flanker0ne!

 

For those not familiar with the config file, the new lines should be placed below

axisCommands = {

(within this category)

[Kailux]

Posts here are very helpful (thanks for posting), but having it fully implemented by ED still is my no. 1 wishlist item for the BS.

Having all buttons and switches implemented in the controls setup like they are in the A-10C would be awesome.

[flanker0ne]

Yes, a merge can be usefull

 

From what i remember

HOTAS/Home cockpits Abstractions

Missing Axis

Flashlight

[Tone71]

Just wanted to add a +1 from me too and a thank you to all of the helpful posts!

[LeCuvier]

Here are my added commands for maintained 2- and 3-position switches. They actually use the cockpit commands defined in "clickabledata.lua":

{down = 3002, up = 3002, value_down = 1, value_up = 0, cockpit_device_id = 23, name = _('Helmet-mounted System 2-Pos. On/Off'), category = _('Ins Targeting Mode Controls Panel PVR')},
{down = 3001, up = 3001, value_down = 1, value_up = 0, cockpit_device_id = 11, name = _('Laser standby 2-Pos ON/OFF Switch'), category = _('Ins Targeting Mode Controls Panel PVR')},
{down = 3017, up = 3017, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Automatic tracking/gun sight 2-Pos AT/GS'), category = _('Ins Targeting Mode Controls Panel PVR')},
{down = 3001, up = 3001, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Master arm 2-Pos ON/OFF'), category = _('Ins Weapons Status and Control Panel PUI-800')},
{down = 3006, up = 3006, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Cannon round selector 2-Pos HE/API'), category = _('Ins Weapons Status and Control Panel PUI-800')},
{down = 3004, up = 3004, value_down = 0.2, value_up = 0.1, cockpit_device_id = 12, name = _('Weapon mode Burst Length 3-Pos HIGH/MEDIUM'), category = _('Ins Weapons Status and Control Panel PUI-800')},
{down = 3004, up = 3004, value_down = 0.0, value_up = 0.1, cockpit_device_id = 12, name = _('Weapon mode Burst Length 3-Pos LOW/MEDIUM'), category = _('Ins Weapons Status and Control Panel PUI-800')},
{down = 3020, up = 3020, value_down = 1.0, value_up = 0.0, cockpit_device_id = 12, name = _('Cannon rate of fire 2-Pos LOW/HIGH'), category = _('Ins Weapons Status and Control Panel PUI-800')},
{down = 3005, up = 3005, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Weapon Control 2-Pos MAN/AUTO'), category = _('Ins Weapons Status and Control Panel PUI-800')},
{down = 3007, up = 3007, value_down = 1.0, value_up = -1.0, cockpit_device_id = 51, name = _('Lighting Night Vision Cockpit Switch 2-Pos ON/OFF'), category = _('Ins Wall panel')},

These commands avoid the synchronization problems mentioned by Jonsky.

[LeCuvier]

Missing axis

{action = 3001, cockpit_device_id = 7, filter = {saturationX = 1, saturationY = 0.5, deadzone = 0, invert = true, slider = true, curvature = {0}}, name = _('HUD Brightness Knob')},
{action = 3002, cockpit_device_id = 8, name = _('IT-23 TV Brightness Axis')},
{action = 3003, cockpit_device_id = 8, name = _('IT-23 TV Contrast Axis')},
{action = 3008, cockpit_device_id = 9, name = _('ABRIS Brightness Axis')},
{action = 3001, cockpit_device_id = 23, name = _('Helmet device Brightness Axis')},
{action = 3006, cockpit_device_id = 46, name = _('ADF Volume Axis')},
{action = 3002, cockpit_device_id = 49, name = _('R-828 (VHF-1) Radio Volume Axis')},

Still require some finetuning to accept secondary settings (slider, invert, saturation ecc) by default, but it work

For the IT-23 commands I noted that they need to be used with Saturation Y = 50%, Slider = TRUE, Invert = TRUE.

I have not implemented the other axes as I do not have any spare axis; but they might require similar settings, as the software tends to use only the upper or lower 50% of available signal range.

[flanker0ne]

From my attempts, I realize that the pre-settings (filter) for axis work only if you pre-assign a joystick axis.

If the line start with {action = ... and not with {combos = ... DCS ignore any pre-setting (filter)

Edited April 23, 2020 by flanker0ne

[kingpinda]

yeah man at least have more than 1 bind for 3 way switches. I want to be able to map the desired heading track to my warthog path altitude switch but in game there is just one command for the switch. at least have 1 bind for up and 1 bind for down. now it cycles in 1 direction.

[Razor5-1]

On 2/21/2020 at 8:03 AM, ghost84 said:

+10000

 

 

Gear Up / Down should have separate key bindings.

 

And there are many more missing.

Literally went looking for what you've said! 

I am getting a Virpil control panel with the gear lever. But the KA50 is literally a button for the gear unfortunately! 

[LeCuvier]

For Landing gear UP/DOWN separate bindings add these to "default.lua":

1. For a pair of pushbutton-type switches:

{down = 3001, value_down = 1.0,cockpit_device_id = 34, name = _('Gear Lever DOWN'), category = _('Ins Forward panel and gauges')},
{down = 3001, value_down = -1.0,cockpit_device_id = 34, name = _('Gear Lever UP'), category = _('Ins Forward panel and gauges')},

2. For a single maintained ON/OFF switch (ON => UP, OFF => DOWN):
 

{down = 3001, up = 3001, value_down = -1.0, value_up = 1.0, cockpit_device_id = 34, name = _('Gear Lever 2-Pos UP/DOWN'), category = _('Ins Forward panel and gauges')},

 

[Schlomo1933]

@LeCuvier : could you please make a mod for all the relevant switches ? Gear, Laser, Helmet sight, gunrate and ammotype ? 

 

that would be realy nice and helpfull

[LeCuvier]

Here are all the specials I created, some for myself and some for other simmers:

{down = 3002, up = 3002, value_down = 1, value_up = 0, cockpit_device_id = 23, name = _('Helmet-mounted System 2-Pos. On/Off'), category = _('Ins Targeting Mode Controls Panel PVR')},
{down = 3001, up = 3001, value_down = 1, value_up = 0, cockpit_device_id = 11, name = _('Laser standby 2-Pos ON/OFF Switch'), category = _('Ins Targeting Mode Controls Panel PVR')},
{down = 3017, up = 3017, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Automatic tracking/gun sight 2-Pos AT/GS'), category = _('Ins Targeting Mode Controls Panel PVR')},
{down = 3001, up = 3001, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Master arm 2-Pos ON/OFF'), category = _('Ins Weapons Status and Control Panel PUI-800')},
{down = 3006, up = 3006, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Cannon round selector 2-Pos HE/API'), category = _('Ins Weapons Status and Control Panel PUI-800')},
{down = 3004, up = 3004, value_down = 0.2, value_up = 0.1, cockpit_device_id = 12, name = _('Weapon mode Burst Length 3-Pos HIGH/MEDIUM'), category = _('Ins Weapons Status and Control Panel PUI-800')},
{down = 3004, up = 3004, value_down = 0.0, value_up = 0.1, cockpit_device_id = 12, name = _('Weapon mode Burst Length 3-Pos LOW/MEDIUM'), category = _('Ins Weapons Status and Control Panel PUI-800')},
{down = 3020, up = 3020, value_down = 1.0, value_up = 0.0, cockpit_device_id = 12, name = _('Cannon rate of fire 2-Pos LOW/HIGH'), category = _('Ins Weapons Status and Control Panel PUI-800')},
{down = 3005, up = 3005, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Weapon Control 2-Pos MAN/AUTO'), category = _('Ins Weapons Status and Control Panel PUI-800')},
{down = 3007, up = 3007, value_down = 1.0, value_up = -1.0, cockpit_device_id = 51, name = _('Lighting Night Vision Cockpit Switch 2-Pos ON/OFF'), category = _('Ins Wall panel')},
{down = 3006, value_down = 1.0,cockpit_device_id = 2, name = _('Battery 1 Cover Open'), category = _('MODDED')},
{down = 3006, value_down = -1.0,cockpit_device_id = 2, name = _('Battery 1 Cover Close'), category = _('MODDED')},
{down = 3001, value_down = 1.0,cockpit_device_id = 34, name = _('Gear Lever DOWN'), category = _('Ins Forward panel and gauges')},
{down = 3001, value_down = -1.0,cockpit_device_id = 34, name = _('Gear Lever UP'), category = _('Ins Forward panel and gauges')},
{down = 3001, up = 3001, value_down = -1.0, value_up = 1.0, cockpit_device_id = 34, name = _('Gear Lever 2-Pos UP/DOWN'), category = _('Ins Forward panel and gauges')},
{down = 3022, up = 3022, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Jettison Fuse 2-Pos ARM/DISARM'), category = _('Ins Weapons Status and Control Panel PUI-800')},
{down = 3002, up = 3002, value_down = 1.0, value_up = -1.0, cockpit_device_id = 59, name = _('K-041 Targeting Power 2-Pos Switch ON/OFF'), category = _('Ins Targeting Mode Controls Panel PVR')},
{down = 3006, up = 3006, value_down = -1.0, value_up = 1.0, cockpit_device_id = 33, name = _('Autopilot Altitude Hold Mode 2-Pos BARO/RALT'), category = _('Autopilot Panel')},
{down = 3003, up = 3003, value_down = -1.0, value_up = 1.0, cockpit_device_id = 28, name = _('Autopilot Desired Heading/Desired Track 2-Pos DH/DT'), category = _('Autopilot Panel')},

Note: most of the lines I created for myself are for maintained 2-position ON/OFF switches. You can easily create two separate bindings for pushbuttons. Take the first line of code above. It switches the HMD ON when the switch goes from OFF to ON, and it switches the HMD OFF when the switch goes from ON to OFF. For a pair of pushbuttons, we split this into two lines:

{down = 3002, value_down = 1, cockpit_device_id = 23, name = _('Helmet-mounted System ON'), category = _('Ins Targeting Mode Controls Panel PVR')},
{down = 3002, value_down = 0, cockpit_device_id = 23, name = _('Helmet-mounted System OFF'), category = _('Ins Targeting Mode Controls Panel PVR')},

The two lines are almost identical, only the value_down is = 1 for ON and =0 for OFF; and of course the names must be different.

[Bvv.Fr]

On 2/28/2020 at 7:33 PM, Crash * said:

A 8-way keybind for the skhval would be up-to-date.

hello

 

any solution for that? ican't make a macro with voiceattack or other app but i would prefer directly in DCS.

i can write every simple one key mapping/binding but this one il more complex, i wrote some  complex  function for the F14 but not try yet for the KA-50 if someone has already done the job? 

 

i think we won't have any improvement because the BS3 is coming....

Edited May 17, 2021 by Bvv.Fr