3 position switches

[evilnate]

Hi Deka team,

 

Many of your customers have three position switches for their HOTAS controllers. Unfortunately the control options for the JF-17 doesn't seem to be setup to take advantage of our three position hardware.

 

Let's take the master mode and thrustmaster warthog throttle as example.

 

Switch options INTC, NAV, and AG.

 

Currently a user needs to assign three specific buttons for this, making a three position switch non-workable. What others have done, is make it so that if INTC switch not activated, NAV mode. If AG not activated NAV mode.

 

Button x = INTC else NAV

Button y = AG else NAV

 

Is this something that can be arranged?

[mtd2811]

I would love that for my warthog

 

 

Sent from my iPhone using Tapatalk

[Panthir]

I used Boat Switch

[evilnate]

I used Boat Switch

 

The boat switch only has two inputs though, right?

 

How do you get all three functions to respond?

[AeriaGloria]

I use Gizzys script and TARGET for everything. Adds functionality for every module. I know it’s not perfect and a native solution would be great, but is an option if anyone is using Thrustmaster

Edited December 21, 2019 by AeriaGloria

[Panthir]

The boat switch only has two inputs though, right?

 

How do you get all three functions to respond?

 

Find default.lua at C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\JF-17\Input\JF-17\joystick and add the following two lines under the T1: MMS

 

{down = key_cmds.HOTAS_Throttle_T1_Forward, up = key_cmds.HOTAS_Throttle_T1_Center, value_down = 1, value_up = 0.5, name = _(cmd_names.HOTAS_Throttle_T1_Forward), category = _('HOTAS_TOGGLE')},

{down = key_cmds.HOTAS_Throttle_T1_Backward, up = key_cmds.HOTAS_Throttle_T1_Center, value_down = 0, value_up = 0.5, name = _(cmd_names.HOTAS_Throttle_T1_Backward), category = _('HOTAS_TOGGLE')},

 

You create a new category HOTAS_TOGGLE, there you will assign BOAT switch front and back position to A/A and A/G respectively. The middle position will be the NAV mode.

[evilnate]

Find default.lua at C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\JF-17\Input\JF-17\joystick and add the following two lines under the T1: MMS

 

{down = key_cmds.HOTAS_Throttle_T1_Forward, up = key_cmds.HOTAS_Throttle_T1_Center, value_down = 1, value_up = 0.5, name = _(cmd_names.HOTAS_Throttle_T1_Forward), category = _('HOTAS_TOGGLE')},

{down = key_cmds.HOTAS_Throttle_T1_Backward, up = key_cmds.HOTAS_Throttle_T1_Center, value_down = 0, value_up = 0.5, name = _(cmd_names.HOTAS_Throttle_T1_Backward), category = _('HOTAS_TOGGLE')},

 

You create a new category HOTAS_TOGGLE, there you will assign BOAT switch front and back position to A/A and A/G respectively. The middle position will be the NAV mode.

 

Brilliant!

 

I'll study that and see if I can figure out how to apply that logic to other keys (stores config, other two way switches). It would be great if Deka could add this so it's ready out of the box.

[ButterCookie]

Here is what i made so far. Just add it into the default.lua in DCS World\Mods\aircraft\JF-17\Input\JF-17\joystick and place it in a free line after "join(res.keyCommands,{".

 

This includes keybinds for:

-Master mode Intercept/Nav/AG

-Airbrakre On/Off

-Parking brake On/Off

-Gear Up/down

- Master arm On/Off

-Flaps Up/Middle/Down

 

{down = key_cmds.HOTAS_Throttle_T1_Forward, up = key_cmds.HOTAS_Throttle_T1_Center,        name = _('Master Mode Forward, else Center'),         category = {_('Switch abstractions')} },
{down = key_cmds.HOTAS_Throttle_T1_Backward, up = key_cmds.HOTAS_Throttle_T1_Center,        name = _('Master Mode Backward, else Center'),         category = {_('Switch abstractions')} },
{down = key_cmds.AirBrake, up = key_cmds.AirBrake,  value_down = 1.0, value_up = 0.0,    name = _('AirBrake On, else Off'),      cockpit_device_id = devices.FCS, category = {_('Switch abstractions')} },
{  down = click_cmds.PNT_511, up = click_cmds.PNT_511, cockpit_device_id = devices.GEAR, value_down = 1.0, value_up = -1.0, name = _('Parking Brake on, else off'), category = {_('Switch abstractions') } },
{  down = click_cmds.PNT_505, up = click_cmds.PNT_505, cockpit_device_id = devices.GEAR, value_down = 1.0, value_up = 0.0,  name = _('Gear up, else down'), category = {_('Switch abstractions') } },
{  down = click_cmds.PNT_509, up = click_cmds.PNT_509,  cockpit_device_id = devices.WCS, value_down = 1.0,  value_up = 0.0, name = _('Master arm on, else off'), category = {_('Switch abstractions') } },
{  down = click_cmds.PNT_513, up = click_cmds.PNT_513,  cockpit_device_id = devices.FCS, value_down = 1.0, value_up = 0.0, name = _('Flaps up, else stop'), category = {_('Switch abstractions')} },
{  down = click_cmds.PNT_513, up = click_cmds.PNT_513,  cockpit_device_id = devices.FCS, value_down = -1.0, value_up = 0.0, name = _('Flaps down, else stop'), category = {_('Switch abstractions')} },

[Harlikwin]

Does this work for the cougar throttle switches?

[ButterCookie]

Does this work for the cougar throttle switches?

I dont have that stick, but it should.

This is made for switches that you cant bind als states to, for example a 2-stage switch you can only map in the "up" position.

[Spiceman]

Find default.lua at C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\JF-17\Input\JF-17\joystick and add the following two lines under the T1: MMS

 

{down = key_cmds.HOTAS_Throttle_T1_Forward, up = key_cmds.HOTAS_Throttle_T1_Center, value_down = 1, value_up = 0.5, name = _(cmd_names.HOTAS_Throttle_T1_Forward), category = _('HOTAS_TOGGLE')},

{down = key_cmds.HOTAS_Throttle_T1_Backward, up = key_cmds.HOTAS_Throttle_T1_Center, value_down = 0, value_up = 0.5, name = _(cmd_names.HOTAS_Throttle_T1_Backward), category = _('HOTAS_TOGGLE')},

 

You create a new category HOTAS_TOGGLE, there you will assign BOAT switch front and back position to A/A and A/G respectively. The middle position will be the NAV mode.

 

Hopefully Deka takes the user-friendly approach like Heatblur and incorporates the useful key binds that users send them. Heatblur took the extra step of having a thread where they actually solicited user keybinds to incorporate into the module. You’ll have to manually re-enter these commands with every release Deka produces until their keybinds reach a level of stability and then you can just make backup copies of the input files.