2/3-Position Switches

[Chain]

Thanks! This helped a lot :thumbup:

 

One mystery remains. I can't figure out how to create a bind for the COMM1 and COMM2 channel selector pull/push option.

 

 

However, most of them only start working after half of the dial has been turned. So it's best to add a user defined curve like this

 

My list

{action = int_light_commands.Knob_Instr_Lights,       cockpit_device_id = devices.LTINT, name = _('FF Instruments Lights')},
{action = int_light_commands.Knob_Console_Lights,     cockpit_device_id = devices.LTINT, name = _('FF Console Lights')},
{action = int_light_commands.Knob_Flood_Lights,       cockpit_device_id = devices.LTINT, name = _('FF Flood Lights')},
{action = int_light_commands.Knob_Annunciator_Lights, cockpit_device_id = devices.LTINT, name = _('FF Annunciator Lights')},

{action = int_light_commands.Flood_Right_Canopy_Frame_Top, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp Canopy Right Top')},
{action = int_light_commands.Flood_Right_Canopy_Frame_Btm, cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp Canopy Right Bottom')},
{action = int_light_commands.Flood_Right_BH_FWD,           cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Right Forward')},
{action = int_light_commands.Flood_Right_BH_AFT_Front,     cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Right Aft Front')},
{action = int_light_commands.Flood_Right_BH_AFT_Back,      cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Right Aft Back')},
{action = int_light_commands.Flood_Left_BH_AFT_Back,       cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Left Aft Back')},
{action = int_light_commands.Flood_Left_BH_AFT_Front,      cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Left Aft Front')},
{action = int_light_commands.Flood_Left_BH_FWD,            cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp BH Left Forward')},
{action = int_light_commands.Flood_Left_Canopy_Frame_Btm,  cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp Canopy Left Bottom')},
{action = int_light_commands.Flood_Left_Canopy_Frame_Top,  cockpit_device_id = devices.LTINT, name = _('FF Flood Lamp Canopy Left Top')},

{action = edp_commands.BRT_Knob, cockpit_device_id = devices.EDP, name = _('FF EDP Brightness Control')},

{action = hud_commands.DisplayBRTKnob, cockpit_device_id = devices.HUDCONTROL, name = _('FF HUD Off/Brightness Control')},
{action = hud_commands.VideoBRTKnob,   cockpit_device_id = devices.HUDCONTROL, name = _('FF HUD Video Brightness Control')},
{action = hud_commands.VideoCONTKnob,  cockpit_device_id = devices.HUDCONTROL, name = _('FF HUD Video Contrast Control')},

{action = ufc_commands.Knob_BRT,        cockpit_device_id = devices.UFCCONTROL, name = _('FF Display Brightness Control')},
{action = ufc_commands.Knob_Comm1_Vol,  cockpit_device_id = devices.UFCCONTROL, name = _('FF Comm 1 Volume Control')},
{action = ufc_commands.Knob_Comm2_Vol,  cockpit_device_id = devices.UFCCONTROL, name = _('FF Comm 2 Volume Control')},
{action = ufc_commands.Knob_Comm1_Chnl, cockpit_device_id = devices.UFCCONTROL, name = _('FF Comm 1 Channel Selector'), category = _('_My Buttons')},
{action = ufc_commands.Knob_Comm2_Chnl, cockpit_device_id = devices.UFCCONTROL, name = _('FF Comm 2 Channel Selector'), category = _('_My Buttons')},

{action = fqi_commands.BingoSet, cockpit_device_id = devices.FQIS, name = _('FF Bingo Fuel Set Knob')},

{action = mpcd_l_commands.Knob_OFF_BRT, cockpit_device_id = devices.MPCD_LEFT,  name = _('FF MPCD Left Off/Brightness Control')},
{action = mpcd_r_commands.Knob_OFF_BRT, cockpit_device_id = devices.MPCD_RIGHT, name = _('FF MPCD Right Off/Brightness Control')},

{action = inst_commands.Knob_Altimeter, cockpit_device_id = devices.ADC, name = _('FF Barometric Pressure Calibration')},

{action = fcs_commands.Knob_FRICTION_LEFT,  cockpit_device_id = devices.FLIGHTCONTROLS, name = _('FF Throttle Lever Friction Knob')},
{action = fcs_commands.Knob_FRICTION_RIGHT, cockpit_device_id = devices.FLIGHTCONTROLS, name = _('FF Nozzle Lever Friction Knob')},

{action = engine_commands.Handle_NOZZLE_CONTROL,  cockpit_device_id = devices.VREST, name = _('FF Nozzle Control Lever')},
{action = engine_commands.Handle_NOZZLE_STO_STOP, cockpit_device_id = devices.VREST, name = _('FF STO Stop Lever')},

{action = ext_light_commands.Knob_FORM_LT, cockpit_device_id = devices.LTEXT, name = _('FF Formation Lights Knob')},

{action = radio_commands.Knob_VOLUME,    cockpit_device_id = devices.RSC, name = _('FF V/UHF RSC Volume Knob')},
{action = radio_commands.Knob_CHAN_FREQ, cockpit_device_id = devices.RSC, name = _('FF V/UHF RSC Chan/Freq Knob')},

{action = acnip_commands.Knob_AUX_VOL, cockpit_device_id = devices.INTERCOM, name = _('FF ICS Aux Volume Knob')},
{action = acnip_commands.Knob_GND_VOL, cockpit_device_id = devices.INTERCOM, name = _('FF ICS Ground Volume Knob')},

Edited December 30, 2017 by Chain

[hansangb]

How are you guys coming up with this code?

 

Nero.ger,

Your code works, Thanks

 

 

If you have a little background in programming, it helps But it's certainly note required.

 

If you read +/- 15 posts or so from this post, you should start to understand what the lua codes are doing

[EinsteinEP]

I can't figure out how to create a bind for the COMM1 and COMM2 channel selector pull/push option.

 

	{down = ufc_commands.Button_Comm1, up = ufc_commands.Button_Comm1, cockpit_device_id = devices.UFCCONTROL, value_down = 1, value_up = 0, name = _('Comm1 Button'), category = _('Up Front Control')},
{down = ufc_commands.Button_Comm2, up = ufc_commands.Button_Comm2, cockpit_device_id = devices.UFCCONTROL, value_down = 1, value_up = 0, name = _('Comm2 Button'), category = _('Up Front Control')},

 

Note that the Comm 2 button motion isn't animated, currently.

[The LT]

Anyone got the CMBT thrust button mapping oneliner?

Is it even modeled in yet?

 

To answer my own question

 

{down = engine_commands.Button_CMBT, up = engine_commands.Button_CMBT, cockpit_device_id = devices.DECS, value_down=1, value_up=0, name = _('CMBT Thrust Button'), category = _('Custom Commands')},

 

And yes, it is modeled.

[Chain]

    {down = ufc_commands.Button_Comm1, up = ufc_commands.Button_Comm1, cockpit_device_id = devices.UFCCONTROL, value_down = 1, value_up = 0, name = _('Comm1 Button'), category = _('Up Front Control')},
   {down = ufc_commands.Button_Comm2, up = ufc_commands.Button_Comm2, cockpit_device_id = devices.UFCCONTROL, value_down = 1, value_up = 0, name = _('Comm2 Button'), category = _('Up Front Control')},

Note that the Comm 2 button motion isn't animated, currently.

 

That's really nice of you. Thank you!

[Wicaeed]

Kind of a stupid question, but is there any way to increase the sensitivity of the mouse scroll for knobs like the lights/radio volume knobs?

 

Currently 1 mouse scroll equals about 1mm of knob movement, so I have to scroll for something like 30 seconds to even get about halfway through the knobs complete rotation movement.

 

Small nitpick...

[Tirak]

Kind of a stupid question, but is there any way to increase the sensitivity of the mouse scroll for knobs like the lights/radio volume knobs?

 

Currently 1 mouse scroll equals about 1mm of knob movement, so I have to scroll for something like 30 seconds to even get about halfway through the knobs complete rotation movement.

 

Small nitpick...

 

You can click and drag those as well.

[Delareon]

Increase Mouse Sensitivity on the Buttons would be interesting, since even if you click and drag you have to do that Multiple times in order to get full Rotation....

At least on the Harrier on the other Modules it works way better i think.

[horus-DCS]

I have a question here.

 

Do COMM channel selectors only work for axis? Don't they have increase/decrease values for buttons or rotary encoders?

[funkyfranky]

Don't they have increase/decrease values for buttons or rotary encoders?

No, they don't (yet). Hope RAZBAM will add that feature :)

[metzger]

Zeus, F-5 (and the rest of belsimtek) is very good example how to handle switches and rotaries/position knobs, in addition include like in the m2000 (on else off) And it should be good. I thought after those years this should be already cleared and standartized.

Honestly I find razbam controls setting complete mess m2000 and now harrier (regardless of on else off which is a good idea) m2000 misses any rottaries and now the harrier even the simple toggles are messed.

 

I am not a cockpit builder but I have warthog hotas and 2 button boxes with rottaries and positional knobs to handle mostly radios and other important controls.

 

Sent from my Redmi 4 using Tapatalk

[smurfarama]

Hi guys

 

 

I'm REALLY new to this, so if it is obvious, I apologise now.

 

 

I have placed Vladinskys' keybind.rar into JSGME and therefore into the DCS AV8B. I have mapped the STO stop onto my Warthog China Hat, but now the STO Stop only moves 1 click at a time no matter how long I hold the China Hat forward or backwards, whereas before it would slide all the way up/down until I released the China Hat.

 

 

Is there an easy way to keep all of the great benefits that the keybind.rar brings, but have my STO Stop control back to 'sliding'.

 

 

Cheers.

[dannyq8]

Replace

 

	{down = iCommandHelicopter_CollectiveStopper_Up,		up = iCommandPlaneCollectiveStop,	name = _('STO STOP UP'),			category = _('Flight Control')},
{down = iCommandHelicopter_CollectiveStopper_Down,		up = iCommandPlaneCollectiveStop,	name = _('STO STOP DOWN'),			category = _('Flight Control')},

 

With

 

	{pressed = iCommandHelicopter_CollectiveStopper_Up,		up = iCommandPlaneCollectiveStop,	name = _('STO STOP UP'),			category = _('Flight Control')},
{pressed = iCommandHelicopter_CollectiveStopper_Down,	up = iCommandPlaneCollectiveStop,	name = _('STO STOP DOWN'),			category = _('Flight Control')},

 

in the joystick\default.lua that you downloaded

[smurfarama]

Replace

 

    {down = iCommandHelicopter_CollectiveStopper_Up,        up = iCommandPlaneCollectiveStop,    name = _('STO STOP UP'),            category = _('Flight Control')},
   {down = iCommandHelicopter_CollectiveStopper_Down,        up = iCommandPlaneCollectiveStop,    name = _('STO STOP DOWN'),            category = _('Flight Control')},

With

 

    {pressed = iCommandHelicopter_CollectiveStopper_Up,        up = iCommandPlaneCollectiveStop,    name = _('STO STOP UP'),            category = _('Flight Control')},    {pressed = iCommandHelicopter_CollectiveStopper_Down,    up = iCommandPlaneCollectiveStop,    name = _('STO STOP DOWN'),            category = _('Flight Control')},

in the joystick\default.lua that you downloaded

 

 

 

dannyq8

 

 

Works great (once I had found the correct default.lua).

 

 

Thanks very much.

[Soundwave197]

Hi, can someone put together the lines for RWR, EXP, ECM as axis and each position of that rotary switch on the fuelpanel?

I wasnt able to find the ID's in all the configs to do it myself.

[Ruebban]

Hi!

 

I'm using the AV8 rar

https://drive.google.com/file/d/17bvF17DFoyLwBvGGbvCrbUgsWj0yK1Jy/view

 

But for some reason when I use it, I can't slew the TPOD with Axis in Open Beta, as soon as i inactivate the mod, i can slew it on axis. Any clue?

[Soundwave197]

Hi!

 

I'm using the AV8 rar

https://drive.google.com/file/d/17bvF17DFoyLwBvGGbvCrbUgsWj0yK1Jy/view

 

But for some reason when I use it, I can't slew the TPOD with Axis in Open Beta, as soon as i inactivate the mod, i can slew it on axis. Any clue?

 

They enabled slewing in the latest update but the date you are using is befor the update.

I bet thats why its not working. You can try to use the 2 lines in the newest unmodified joystick.lua and put it in the modified old joystick.lua but you have to delete the old 2 lines. they should be at the last few lines. its called "--HOTAS TDC"

[Beazle]

Hey guys,

 

I don't know if it's whos dumb or it is just very complicated. I know it is a Harrier thread but I am trying to get some swticehs working on the f-5. I have read the whole thread and compared the cilckabledata.lua file of the f-5 with whats on this thread and it just seems so different and I can'T understand how to get me switches to work :(

 

Is someone able to give me a guideline on how the f-5 2/3 way switches work? No infos is available out here :/

 

regards

Billy

[firmek]

Hey guys,

 

I don't know if it's whos dumb or it is just very complicated. I know it is a Harrier thread but I am trying to get some swticehs working on the f-5. I have read the whole thread and compared the cilckabledata.lua file of the f-5 with whats on this thread and it just seems so different and I can'T understand how to get me switches to work :(

 

Is someone able to give me a guideline on how the f-5 2/3 way switches work? No infos is available out here :/

 

regards

Billy

They work basically the same way. You need an up and down action for 2 position switch and two up and one down action for a 3 position one.

Look for a similar thread under F-5 section. I'm sure it's there, if not start it. It would help to write which keys are you interested in.

[Beazle]

thanks for the reply firmek.

 

I am looking to get both external central tank switch and pylon ext tank switches which are 2 ways.

 

I've read what to had like the up down position switch but I am not sure where to had the line. like this one:

 

{down = hud_commands.RejectSwitch, up = hud_commands.RejectSwitch, cockpit_device_id = devices.HUDCONTROL, value_down = 1, value_ up = 0.5, name = _('COMMAND NAME 1'), category = { _('CATEGORY NAME 1'), _('CATEGORY NAME 2')}},

 

Here is the paragraph which contains the 2 ways witches in the clickabledata.luda file from the f-5e I think I need to modify:

elements["PTR-CVR-LVP-SHOOTOFF-L-359"] = default_red_cover(_("Left Fuel Shutoff Switch Cover, OPEN/CLOSED"), devices.FUEL_INTERFACE, fuel_commands.FuelShutoffCover_Left, 359)

elements["PTR-TMB-LVP-SHOOTOFF-L-360"] = default_2_position_tumb2(_("Left Fuel Shutoff Switch, OPEN/CLOSED"), devices.FUEL_INTERFACE, fuel_commands.FuelShutoff_Left, 360)

elements["PTR-CVR-LVP-SHOOTOFF-R-361"] = default_red_cover(_("Right Fuel Shutoff Switch Cover, OPEN/CLOSED"), devices.FUEL_INTERFACE, fuel_commands.FuelShutoffCover_Right, 361)

elements["PTR-TMB-LVP-SHOOTOFF-R-362"] = default_2_position_tumb2(_("Right Fuel Shutoff Switch, OPEN/CLOSED"), devices.FUEL_INTERFACE, fuel_commands.FuelShutoff_Right, 362)

elements["PTR-TMB-VRP-FUEL-TRANS-FUZ-377"] = default_2_position_tumb2(_("Ext Fuel Cl Switch, ON/OFF"), devices.FUEL_INTERFACE, fuel_commands.ExtFuelTransfer_Cl, 377)

elements["PTR-TMB-VRP-FUEL-TRANS-PYL-378"] = default_2_position_tumb2(_("Ext Fuel Pylons Switch, ON/OFF"), devices.FUEL_INTERFACE, fuel_commands.ExtFuelTransfer_Pylon, 378)

elements["PTR-TMB-VRP-LFT-BOOST-380"] = default_2_position_tumb(_("Left Boost Pump Switch, ON/OFF"), devices.FUEL_INTERFACE, fuel_commands.FuelBoostPump_Left, 380, 9.6)

elements["PTR-TMB-VRP-CRSS-BOOST-381"] = default_2_position_tumb2(_("Crossfeed Switch, OPEN/CLOSED"), devices.FUEL_INTERFACE, fuel_commands.FuelCrossfeed, 381)

elements["PTR-TMB-VRP-RGT-BOOST-382"] = default_2_position_tumb(_("Right Boost Pump Switch, ON/OFF"), devices.FUEL_INTERFACE, fuel_commands.FuelBoostPump_Right, 382, 9.6)

elements["PTR-TMB-VRP-AUTO-BAL-383"] = springloaded_3_pos_tumb(_("Autobalance Switch, LEFT/NEUT/RIGHT"), devices.FUEL_INTERFACE, fuel_commands.FuelAutoLeft, fuel_commands.FuelAutoRight, 383)

[comie1]

Hey guys!

 

Don't suppose any of you would be kind enough to make an ON else OFF switch command for the Auto pilot switches would you?

 

Thanks for the other anyway :thumbup:

[Nero.ger]

there is a problem, the switches are spring loaded and jump back themselves. so your Pysical switch is no longer correct

[comie1]

there is a problem, the switches are spring loaded and jump back themselves. so your Pysical switch is no longer correct

 

:huh:

:book:

This is true :smartass:

:lol: Thanks dude!

[Schlomo1933]

Pls, can somebody make a toggle 2/3 Pos switch for the MiG-15:

landinggear, the lockswitch and for the flaps

 

Pls, pls, pls

 

(without target)

[firmek]

Pls, can somebody make a toggle 2/3 Pos switch for the MiG-15:

landinggear, the lockswitch and for the flaps

 

Pls, pls, pls

 

(without target)

Flaps is a 4 position switch - not much use of it, you'll have to stay with keys for moving the lever up and down. On top of that, for most of the switches MiG-15 doesn't have a separate on/off action - just toggle.

Anyway, I'll share the .lua later on - though for the reason above the bindings don't work fully correct.