"Special For Joystick" binding for Master Arm

I'm missing a "Special For Joystick" binding for the master arm switch (so "up" is ARM, and "down" is SAFE). I love that you have added it for Battery and APU, but would really like to see a similar option for master arm as well.

..and for the Hook and the rdr/baro switch.

+1 to both!

go to Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lau and add these lines for the barometric radar and masterarm

{ down = SMS_commands.MasterArmSw, up = SMS_commands.MasterArmSw, cockpit_device_id = devices.SMS, value_down = 1.0, value_up = 0.0, name = _('Master Arm Switch - ARM Else SAFE'), category = {_('Specific switch abstraction')}},

{ down = HUD_commands.HUD_AltitudeSw, up = HUD_commands.HUD_AltitudeSw, cockpit_device_id = devices.HUD, value_down = 1.0, value_up = 0.0, name = _('Radar alt Else Barometric'), category = {_('Specific switch abstraction')}},

This will create a new category in DCS, map the switches to those settings and you should be good to go.

Cool, thanks!

go to Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lau and add these lines for the barometric radar and masterarm

 

{ down = SMS_commands.MasterArmSw, up = SMS_commands.MasterArmSw, cockpit_device_id = devices.SMS, value_down = 1.0, value_up = 0.0, name = _('Master Arm Switch - ARM Else SAFE'), category = {_('Specific switch abstraction')}},

{ down = HUD_commands.HUD_AltitudeSw, up = HUD_commands.HUD_AltitudeSw, cockpit_device_id = devices.HUD, value_down = 1.0, value_up = 0.0, name = _('Radar alt Else Barometric'), category = {_('Specific switch abstraction')}},

 

 

This will create a new category in DCS, map the switches to those settings and you should be good to go.

A well known procedure, but every update I have to reinsert the lines again or rewrite the file from the backup directory.

..and for the Hook and the rdr/baro switch.

Gotta love my cheap X-56, i could bind the Hook, external lights, Master Arm to the flip switches on the Throttle base. :)

A well known procedure, but every update I have to reinsert the lines again or rewrite the file from the backup directory.

+1 again. I want it to official instead of a mod :thumbup:

A well known procedure, but every update I have to reinsert the lines again or rewrite the file from the backup directory.

Perhaps use OvGME. It will take you, oh, 4 seconds after every patch.

Perhaps use OvGME. It will take you, oh, 4 seconds after every patch.

F-18 is in EA so sometime they update the file, and using JSGME or similar you could overwrite the file with an old version.

Could someone share their edits on this file?

I'm still missing commands for the landing gear and hook atleast.

+1 again. I want it to official instead of a mod :thumbup:

+2:thumbup::thumbup:

I'd like the same thing for launch bar please.. Oddly, in quick action missions, the launch bar switch works properly, when I start the aircraft up on my own, the switch takes 2 throws to toggle the launch bar.. (flick the switch up to drop the bar, click the switch down and back up to raise the bar again..) Maybe this is a bug.. It's inconsistent from quick action mission and self starting..

Sent from my SM-G965U using Tapatalk

It's always great to have these officially in the module. Especially since it's in early access, the devs basically get what's needed and are able to implement it, often even without writing the code themselves because often there's someone who did it already on their own. I also use edited lua files for input that I load via JSGME, but I always have to check after updates if changes have been made to the original files and update mine then.

I'd like the same thing for launch bar please.. Oddly, in quick action missions, the launch bar switch works properly, when I start the aircraft up on my own, the switch takes 2 throws to toggle the launch bar.. (flick the switch up to drop the bar, click the switch down and back up to raise the bar again..) Maybe this is a bug.. It's inconsistent from quick action mission and self starting..

 

Sent from my SM-G965U using Tapatalk

Same here. It would be great if Launch Bar was added as a "Special for Joystick "

OBOGS too please!

A well known procedure, but every update I have to reinsert the lines again or rewrite the file from the backup directory.

+1, I have the same pain every update

+1 and here is the code for the Arrestor Hook:

it would be awesome to have a custom_input.lua for every plane that dont get overwritten

Wish I could make a BRT/OFF toggle for the Strobe light. Can't believe with 8 other Strobe commands (for a 3 position switch) there is no toggle.

I am pretty sure you can edit joystick default.lua to create the command you want. Search the input/output forum for "How To Edit Control Binding Files".

go to Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lau and add these lines for the barometric radar and masterarm

 

{ down = SMS_commands.MasterArmSw, up = SMS_commands.MasterArmSw, cockpit_device_id = devices.SMS, value_down = 1.0, value_up = 0.0, name = _('Master Arm Switch - ARM Else SAFE'), category = {_('Specific switch abstraction')}},

{ down = HUD_commands.HUD_AltitudeSw, up = HUD_commands.HUD_AltitudeSw, cockpit_device_id = devices.HUD, value_down = 1.0, value_up = 0.0, name = _('Radar alt Else Barometric'), category = {_('Specific switch abstraction')}},

 

 

This will create a new category in DCS, map the switches to those settings and you should be good to go.

Will this make your Client un pure?

go to Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lau and add these lines for the barometric radar and masterarm

 

{ down = SMS_commands.MasterArmSw, up = SMS_commands.MasterArmSw, cockpit_device_id = devices.SMS, value_down = 1.0, value_up = 0.0, name = _('Master Arm Switch - ARM Else SAFE'), category = {_('Specific switch abstraction')}},

{ down = HUD_commands.HUD_AltitudeSw, up = HUD_commands.HUD_AltitudeSw, cockpit_device_id = devices.HUD, value_down = 1.0, value_up = 0.0, name = _('Radar alt Else Barometric'), category = {_('Specific switch abstraction')}},

 

 

This will create a new category in DCS, map the switches to those settings and you should be good to go.

Wish I’d seen this months ago.

Also wish ED would’ve fixed this months ago.

I'm trying to do this for the Anti Skid and Hook Bypass switches (using the Fuel Norm/Override switches on the Warthog throttle). Anti Skid works fine, but Hook Bypass simply toggles between Field and Carrier each time I turn the switch ON.

Any ideas what's wrong here?

{ down = gear_commands.AntiSkidSw, up = gear_commands.AntiSkidSw, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Anti Skid Switch - ON/OFF'), category = {_('Specific switch abstraction')}},

{ down = cptlights_commands.HookBypass, up = cptlights_commands.HookBypass, cockpit_device_id = devices.CPT_LIGTHS, value_down = 1.0, value_up = 0.0, name = _('Hook Bypass Switch - FIELD/CARRIER'), category = {_('Specific switch abstraction')}},

Also, what does orange indicate in the input editor? It's actually the Anti Skid binding which is orange but that's the one which works ok.

Weird that there's a default binding for speed brake Retract/Off but not one for Extend. I added the following (changing the down value to '-1.0') and am happy to report it works as expected...

{ down = hotas_commands.THROTTLE_SPEED_BRAKE, up = hotas_commands.THROTTLE_SPEED_BRAKE, cockpit_device_id = devices.HOTAS, value_down = -1.0, value_up = 0.0, name = _('Speed Brake Switch - EXTEND/OFF'), category = {_('Special For Joystick'), _('Throttle Grip'), _('HOTAS')}},

Heatblur's "Running request - Bindable Button / Axis options" thread is a good example in the beginning of EA I had to run modified file and now it's pretty much has all the key binds I need.