SpeedyE420 Posted June 29, 2019 Posted June 29, 2019 Can we get Bright else off, dim else off, and strobe on else off for 3 way switch controls. Like the rest of the controls in the special for joystick category. Thanks. Owned Modules: F-18, F-16, F-14, AV-8B, A-10c, Huey, Hip, KA-50, Gazelle, Mig 15, Mig 19, Mig 21, FC3, P-51, BF-109, C-101, L-39, F-5, YAK-52 PC Specs- 8700k at 5.1GHz on Asrock z370 Fata1ity k6, EVGA 1080ti SSC2, 32 GB G.Skill TridentZ, 1TB NVMe m.2 Drive for DCS with a 500gb NVMe M.2 boot drive, Oculus Rift S
Jak525 Posted June 30, 2019 Posted June 30, 2019 Would like this for the exterior lights master switch on the throttle as well.
SpeedyE420 Posted June 30, 2019 Author Posted June 30, 2019 Yes all exterior lights would be awesome. Owned Modules: F-18, F-16, F-14, AV-8B, A-10c, Huey, Hip, KA-50, Gazelle, Mig 15, Mig 19, Mig 21, FC3, P-51, BF-109, C-101, L-39, F-5, YAK-52 PC Specs- 8700k at 5.1GHz on Asrock z370 Fata1ity k6, EVGA 1080ti SSC2, 32 GB G.Skill TridentZ, 1TB NVMe m.2 Drive for DCS with a 500gb NVMe M.2 boot drive, Oculus Rift S
Rennes Posted July 2, 2019 Posted July 2, 2019 (edited) I made my own for the master exterior lights switch. Just paste this into the file C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua Put it just below the line at the top that read: join(res.keyCommands,{ { down = hotas_commands.THROTTLE_EXTERIOR_LIGTHS, up = hotas_commands.THROTTLE_EXTERIOR_LIGTHS, cockpit_device_id = devices.HOTAS, value_down = 1.0, value_up = 0.0, name = _('Exterior Lights Switch'), category = {_('Custom Special For Joystick'), _('Throttle Grip'), _('HOTAS')}}, You'll have to redo it after each update though. Edited July 2, 2019 by Rennes Typo
fael097 Posted July 19, 2019 Posted July 19, 2019 (edited) I made my own for the master exterior lights switch. Just paste this into the file C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua Put it just below the line at the top that read: join(res.keyCommands,{ { down = hotas_commands.THROTTLE_EXTERIOR_LIGTHS, up = hotas_commands.THROTTLE_EXTERIOR_LIGTHS, cockpit_device_id = devices.HOTAS, value_down = 1.0, value_up = 0.0, name = _('Exterior Lights Switch'), category = {_('Custom Special For Joystick'), _('Throttle Grip'), _('HOTAS')}}, You'll have to redo it after each update though. the easiest way to redo it after each update: -download and install notepad++ -make a shortcut for it wherever you want -set the shortcut to run as administrator - this is very important as it's the only way to save the files if you install DCS into the default directory -open the default.lua file that you want to mod - in this case C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua as mentioned above -create a new file and save it with any name .lua anywhere you want, you will script your changes here and then paste it into the default.lua and save both files. why do this specifically? because notepad++ keeps the files you opened on its memory. next time you open it those two files will be there in two tabs just like when you closed it. so if you update DCS, next time you open notepad++ you will have the default.lua file back to its default state, without your modifications, and you will have your other file on another tab, so you just have to copy and paste it into the default.lua again. it's still a manual process, but trust me, it's way easier than opening windows explorer, browsing for your txt file where you saved your mods, opening with windows notepad, copying it, then browsing for default.lua, opening it with notepad, pasting it, trying to save just to realize you are not in administrator mode, then saving it elsewhere like your desktop, then realizing you saved your file as .lua.txt because notepad defaults to that and you forgot to change, then manually erasing the .txt from the file name, copying it, browsing for the default.lua folder again cause you just closed it without realizing you would need it again, then replacing the file. and repeating that every update. and also repeating that for other .lua files that you modified. seems like it's not too much trouble and that you could avoid many mistakes here and there, but it becomes a chore quickly. compare that with opening notepad++, both files are already opened that in tabs, then copying the text from one file and pasting into the other and clicking save. done. other tips: -make a new section for your custom commands on top of the original Cheats section, by adding a new header, such as --------------------------------------------- -- Mods ------------------------------------ --------------------------------------------- -Name your commands so that you won't mistake them for official commands, like adding _MOD after their names -create your own category so you can easily find in game all your custom commands. in my case I added them to the existing categories and also one called Mods that I made. like this: category = {_('Special For Joystick'), [b]_('Mods'),[/b] _('Right Vertical Panel')}}, here's what I added to my default.lua: --------------------------------------------- -- Mods ------------------------------------ --------------------------------------------- { down = hotas_commands.THROTTLE_EXTERIOR_LIGTHS, up = hotas_commands.THROTTLE_EXTERIOR_LIGTHS, cockpit_device_id = devices.HOTAS, value_down = 0.0, value_up = 1.0, name = _('Exterior Lights Switch_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Throttle Grip'), _('HOTAS')}}, { down = extlights_commands.LdgTaxi, up = extlights_commands.LdgTaxi, cockpit_device_id = devices.EXT_LIGHTS, value_down = 1.0, value_up = 0.0, name = _('Landing Gear/Taxi Lights Switch_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { 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_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = gear_commands.LaunchBarSw, up = gear_commands.LaunchBarSw, cockpit_device_id = devices.GEAR_INTERFACE, value_down = -1.0, value_up = 1.0, name = _('Launch Bar Control Switch_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = iCommandPlaneGearUp, up = iCommandPlaneGearDown, name = _('Landing Gear Control Handle_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = gear_commands.HookHandle, up = gear_commands.HookHandle, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Arresting Hook Handle_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Right Vertical Panel')}}, { down = fuel_commands.ProbeControlSw, up = fuel_commands.ProbeControlSw, cockpit_device_id = devices.FUEL_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Probe Control Switch_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = gear_commands.EmergParkHandleOnOff, up = gear_commands.EmergParkHandleOnOff, cockpit_device_id = devices.GEAR_INTERFACE, value_down = -1.0, value_up = 1.0, name = _('Parking Brake Switch_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = ctrl_commands.WingFoldSelect, up = ctrl_commands.WingFoldSelect, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0, value_up = 1.0, name = _('Wing Fold Control Handle TURN_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Right Vertical Panel')}}, { down = SMS_commands.MasterArmSw, up = SMS_commands.MasterArmSw, cockpit_device_id = devices.SMS, value_down = 0.0, value_up = 1.0, name = _('Master Arm Switch - SAFE/ARM_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Instrument Panel'), _('Master Arm Panel')}}, { down = cpt_commands.CanopySwitchOpen, up = cpt_commands.CanopySwitchOpen, cockpit_device_id = devices.CPT_MECHANICS, value_down = 1.0, value_up = -1.0, name = _('Canopy Control Switch - OPEN_MOD'), category = {_('Special For Joystick'), _('Mods'), _('Right Wall'), _('Systems')}}, I added some functionality to the TM warthog hotas. the actual hornet hotas' pinky switch is only 2 position while the warthog is 3, so I wanted to add the landing gear taxi lights to it, but since the switch is ON-OFF-ON it would be weird, I'd have to chose between having the exterior lights or the taxi lights on. so I had to add a mod to invert the behavior of the exterior lights switch, so when button is down, value is 0 (off) and when it's up value is 1. now my pinky switch works like this: both OFF / only exterior lights ON / exterior AND taxi lights ON. you can't have the taxi lights on with the exterior lights off, but that's a trade off I was willing to make. did something like this for many commands, I posted a picture of my hotas assignments somewhere once, but I changed a lot of useless stuff since then. perhaps will do it again someday. but I guess OP can work from there. I also modded a command on the default.lua file for my keyboard because some commands have the keyboard shortcut assignment disabled when you add them on your joystick default.lua. I believe it was the speedbrake, not sure hope this helps! Edited July 19, 2019 by fael097 Rafael Ryzen 7 1800x @ 4ghz | MSI GTX 980ti | 32gb DDR4 Ballistix 2400Mhz | Asus ROG Crosshair VII Hero (wi-fi) | 480Gb Kingston NVMe ssd | Western Digital 1TB x2 | EVGA 850w PSU | Noctua NH-D14 | NZXT S240 | Windows 10 Pro 64bit | 4k 50" Philips android TV | Dell P2418D | Oculus Rift S | Thrustmaster Warthog Hotas
Recommended Posts