Quaggles

Unfortunately I can't replicate that issue, at first I just brought your Mirage F1 binds in and it worked as expected, then I thought it might be that you had hit some limit on the total amount of input commands that can exist in DCS haha So I brought your entire package in and closed and opened DCS a bunch of times going right into the control menu for the Mirage F1 CE and always had the common and Mirage F1 CE keyCommands and axisCommands show up, even the `Aircrafts\common_joystick_binding.lua` bindings I have were working on top of that. This was the only input related code I saw in dcs.log but it was all still working for me: 2022-07-25 14:51:17.598 INFO INPUT: Key combo skipped. Layer[InputOptionsView] key = [KEY_L] device = [Keyboard] modifiers[key = [KEY_RCONTROL] device = [Keyboard]] switches[] action[down = -166, ]. Combo already mapped to action [down = -72, ] 2022-07-25 14:51:17.598 INFO INPUT: Key combo skipped. Layer[InputOptionsView] key = [KEY_J] device = [Keyboard] modifiers[key = [KEY_LSHIFT] device = [Keyboard]] switches[] action[down = -199, ]. Combo already mapped to action [down = -61, ] 2022-07-25 14:51:17.598 INFO INPUT: Key combo skipped. Layer[InputOptionsView] key = [KEY_K] device = [Keyboard] modifiers[key = [KEY_RCONTROL] device = [Keyboard]] switches[] action[down = -208, ]. Combo already mapped to action [down = -27, ] 2022-07-25 14:51:17.599 INFO INPUT: Key combo skipped. Layer[InputOptionsView] key = [KEY_T] device = [Keyboard] modifiers[] switches[] action[down = -305, ]. Combo already mapped to action [down = -266, ] 2022-07-25 14:51:17.599 INFO INPUT: Key combo skipped. Layer[InputOptionsView] key = [KEY_P] device = [Keyboard] modifiers[key = [KEY_RSHIFT] device = [Keyboard]] switches[] action[down = -315, ]. Combo already mapped to action [down = -52, ] 2022-07-25 14:51:17.600 INFO INPUT: Key combo skipped. Layer[InputOptionsView] key = [KEY_Z] device = [Keyboard] modifiers[key = [KEY_LALT] device = [Keyboard]; key = [KEY_LSHIFT] device = [Keyboard]] switches[] action[down = -344, ]. Combo already mapped to action [down = -62, ] If you haven't already set `quagglesLoggingEnabled = true` in the Data.lua file then reproduce the problem on your end and upload dcs.log here.

Can confirm the lua datamine values are correct and that it's been set correctly as a 914kg warhead for at least as long as the datamine has existed, the warhead table is more complex than the `expl_mass` parameter since ED is simulating a shaped charge warhead so I've written up an explanation here: https://github.com/Quaggles/dcs-lua-datamine/issues/6

If it was working before the patch then maybe the mod didn't reinstall correctly? Try going to`DCS World/Scripts/Input/Data.lua` once you've installed the mod and search for "Quaggles" if it doesn't find any results then your mod manager isn't overwriting the script correctly. If that doesn't lead to anything you can try following the guide on the Github: https://github.com/Quaggles/dcs-input-command-injector#my-new-input-commands-arent-showing-up-ingame That should determine why it's not hooking the custom commands if the mod is installed.

Still working for me, no changes in this patch to the file that the mod changes. Are the custom controls just not showing up ingame?

Ah good advice Munkwolf, I've never owned a device that had those device specific luas configured so I completely forgot about them for custom input stuff, they just happen to work with the injector since I hook into the DCS function that handles all lua input files and not just the generic ones, so that's fortunate haha

Did you put them in a "joystick/default.lua" as shown in the instructions on the github? If you only put them in "keyboard/default.lua" they can't be assigned to HOTAS.

I've done some temporary hold ones for my X-55 Throttle: { down = control_commands.SpdBrk, up = control_commands.SpdBrk, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1, value_up = 1.0, name = _('Speed Brake Hold'), category = {_('Quaggles Custom')}}, { down = control_commands.SpdBrk, up = control_commands.SpdBrk, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 1.0, value_up = -1, name = _('Speed Brake Hold (Inverted)'), category = {_('Quaggles Custom')}},

Version 1.0.6 released: https://github.com/Quaggles/dcs-input-command-injector/releases/tag/1.0.6 Updated mod to be compatible with DCS 2.7.15.26783 Data.lua changes

Version 1.0.5 released: https://github.com/Quaggles/dcs-input-command-injector/releases/tag/1.0.5 Allows `Config/Input` files to be merged, useful for merging `Aircrafts\common_joystick_binding.lua`, this allows you to add binds that will be automatically merged with most modules from a single file (Thanks @Ryuk47) Updated data.lua to current DCS World Version, adds SideWinder Force Feedback 2 Joystick in the default assignments. (Thanks @Ryuk47) Updated `InputCommands.zip` skeleton to contain AH-64D paths and `Aircrafts\common_joystick_binding.lua` + `Aircrafts\common_keyboard_binding.lua`

Ah good to see it's all sorted, not sure what went wrong but as Munkwolf said if it happens again check dcs.log in C:\Users\USERNAME\Saved Games\DCS\Logs. That should give some hints about the problem.

The first thing I'd do is enable your mod then open /Scripts/Input/Data.lua in the DCS install, go to around line 80 and confirm you see a bunch of lines with Quaggles in it, for example lines 78 to 84 should be this: --[[ Insert this code into "DCSWorld\Scripts\Input\Data.lua" above the function "loadDeviceProfileFromFile" Then add the line: QuagglesInputCommandInjector(filename, folder, env, result) into the "loadDeviceProfileFromFile" function below the line: status, result = pcall(f) ]]-- If that exists then the mod is installed to the correct location. Also the new keybinds won't necessarily be in a 'Quaggles Custom' category, that's just the category I set for keybinds I make. If you are using the community keybinds mod they will have picked categories for their own keybinds, for example if you look at their F-86 ones you can see the categories in the last table for each line, in the case of "Drop Tank Selector Switch ALL TANKS OFF" it is in the categories: 'Drop Tank Control Panel', 'Fuel System' and 'Custom' {down = fuel_commands.F86_CockpitDeviceCommand_TankSelector_Sw, cockpit_device_id = devices.FUEL_INTERFACE, value_down = 0.0, name=_('Drop Tank Selector Switch ALL TANKS OFF'), category = {_('Drop Tank Control Panel'), _('Fuel System'), _('Custom')}},

Hardlinking isn't required, just makes things nicer since it will keep the joystick and keyboard default.lua files linked so they will always match when you modify one. You can just have a separate copy of the default.lua in the joystick and keyboard folders if hardlinking doesn't work, just keep them matching manually to avoid weird issues.

Version 1.0.4 released: https://github.com/Quaggles/dcs-input-command-injector/releases/tag/1.0.4 Allows UiLayer input commands to be injected (Thanks @davidp57) Supports DCS 2.7.7.14727 Data.lua changes

I recommend using Visual Studio Code with the vscode-lua extension, it will highlight your syntax errors and can save a lot of time troubleshooting

Yes, I just tested it and this works: {down = iCommandPlaneCobra, up = iCommandPlaneCobra, value_down = 1.0, value_up = 0.0, name = _('ASC Direct Control (Cobra) (Hold)'), category = _('Quaggles Custom')},

Thanks, I'll link to your GitHub for the community keybinds as well once it's up

Yeah I'd try using that skeleton template that was posted and if that's still failing read the section on the GitHub page about enabling logs. Can I get your permission to put this directly on the GitHub to make it easier for first time setup?

You might find this mod I just posted useful, allows you to put all your custom inputs in your `Saved Games` folder so you don't need to merge them with the module input changes when DCS updates.

Newest Update: 12/07/2024: Version 1.0.12 released: https://github.com/Quaggles/dcs-input-command-injector/releases/tag/1.0.12 * Updated mod to be compatible with DCS 2.9.6.57650 Data.lua changes Summary A mod that allows you to configure custom input commands inside your Saved Games/DCS/ folder instead of inside your game folder, when DCS is run these commands are merged in with the default aircraft commands. This method avoids having to manually merge your command changes into each aircrafts default commands when DCS updates. After reading the install guide I'd recommend also looking at the DCS Community Keybinds project by Munkwolf, it uses this mod and contains many community requested input commands without you needing to code them manually. The goal of this mod Commonly in DCS users with unique input systems will need to create custom input commands to allow them to use certain aircraft functions with their HOTAS. Some examples are: Configuring 3 way switches on a Thrustmaster Warthog HOTAS to control switches the module developer never intended to be controlled by a 3 way switch Configuring actions that only trigger a cockpit switch while a button is held, for example using the trigger safety on a VKB Gunfighter Pro to turn on Master Arm while it's flipped down and then turn off Master Arm when flipped up Adding control entries that the developer forgot, for example the Ka-50 has no individual "Gear Up" and Gear Down" commands, only a gear toggle In my case, on my Saitek X-55 Throttle there is an airbrake slider switch that when engaged registers as a single button being held down, when the slider is disengaged the button is released. In DCS by default few aircraft support this type of input so a custom input command is needed, in my case for the F/A-18C: {down = hotas_commands.THROTTLE_SPEED_BRAKE, up = hotas_commands.THROTTLE_SPEED_BRAKE, cockpit_device_id = devices.HOTAS, value_down = -1.0, value_up = 1.0, name = 'Speed Brake Hold', category = {'Quaggles Custom'}}, Until now the solution was to find the control definition file DCSWorld\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua and insert your custom command somewhere inside of it, if you weren't using a mod manager then every time the game was updated your change would be erased and you'd need reinsert your commands into the files for every aircraft you changed. If you were using a mod manager such as OVGME if you reapplied your mod after an update and the developers had changed the input commands things could break and conflict. With this mod you should just need to re-enable it after every DCS update with OVGME and your custom commands are safe with no need no change anything. Link with install instructions, download and some examples: https://github.com/Quaggles/dcs-input-command-injector

Problem: Mission Editor triggered failures to the Hydraulic Pumps/Transfer Pump or the Wing Sweep will persist even after restarting a mission Reproduction: 1. Play the attached mission, Hydraulic Pumps/Transfer Pump and Wing Sweep should fail within 1 minute of flight 2. Play another mission such as a free flight 3. Observe that the Hydraulic Pumps/Transfer and Wing Sweep are still broken. Game restart is required for them to work again. DCS Version: 2.5.6.52196 Notes: This potentially could be the source of other issues people are having such as the right engine startup bug, it's possible other aircraft states are not being reset. For example after running the failure mission then joining a multiplayer server and choosing different slots wouldn't fix the issue. Doing a repair however did fix the failures. F-14 Failures.miz

Problem: Changing scan bars in TWS AUTO causes scan elevation to become stuck in RWS and sometimes TWS Manual/BIAS. I can't find a consistent workaround to get it working again, sometimes designating an empty space on the ATTACK RADAR fixes it but often not. Reproduction: 1. Open AA Radar 2. Change to TWS 3. Change to AUTO steering 4. Click the elevation bar pushbutton 5. Change to RWS mode 6. Observe that you can't change scan elevation anymore DCS Version: 2.5.6.52196

Problem: In NAV or AG master mode having a WPDSG while using the AIR submode of the Attack Radar page prevents you from changing the range scale and antenna elevation. I assume this occurs because the jet is trying to set the automatic range and antenna elevation for the AG radar to focus on the designated point but isn't checking the submode is actually SURF. To Reproduce: 1. Be in NAV or AG master mode 2. WPDSG a waypoint 3. Bring up ATTACK RADAR in AIR mode 4. Can't change elevation or range DCS Version: 2.5.6.52196 FA-18C Designation AA Radar Bug.trk

You could set the Computer Address Panel to the NAV category and then press "OWN A/C" to hook your own aircraft again (Same result as TID half action).

Here is another example of it happening in a 2 ship formation with the same setup as my previous example: ${1}