Quaggles - DCS Input Command Injector Mod - Store custom input commands safely in Saved Games instead of merging them with developer changes each update

[X-Ray]

Wooow finally!

For example..

I want to make the FC3 pilots visor animations working (up/down)

The Argument number is 98 (for all Mig-29s, Su-27/33 and J-11

Wich procedure do I have to follow to keep 'em working?

 

[LeCuvier]

Has anybody managed to make this mod work with the F-4E Phantom? I couldn't make it work, and in the end I had to remove the sub-folders for the Phantom under "..\Input Commands\" because it blocked the DCS software completely. Heatblur uses a different structure in its "default.lua" files and I suspect that the @Quaggles mod doesn't handle that correctly.

Edit:
I also didn't see anything for the F-4E on the Github page owned by @Munkwolf. @Munkwolf do you intend to provide bindings for the Phantom?
Edit: I seem to make progress, using the "traditional" format in the "default.lua" under Saved Games. Example:
I wanted to make "slow" versions of the Pitch Trim Nose-up and Nose-down commands. The original command lines have this form:

{ name = _('Trim - Nose Up (Hat Aft)'), up = iCommandPlaneTrimPitch, pressed = iCommandPlaneTrimPitch, value_up = 0, value_pressed = 1, category = { categories.flight_controls, categories.stick, categories.essentials } },
{ name = _('Trim - Nose Down (Hat Forward)'), up = iCommandPlaneTrimPitch, pressed = iCommandPlaneTrimPitch, value_up = 0, value_pressed = -1, category = { categories.flight_controls, categories.stick, categories.essentials } },

In the original "default.lua" (under "keyboard") I could use these modified lines and they worked fine:

{ name = _('Trim - Nose Up Slow (Hat Aft)'), up = iCommandPlaneTrimPitch, pressed = iCommandPlaneTrimPitch, value_up = 0, value_pressed = 0.3, category = { categories.flight_controls, categories.stick, categories.essentials } },
{ name = _('Trim - Nose Down Slow (Hat Forward)'), up = iCommandPlaneTrimPitch, pressed = iCommandPlaneTrimPitch, value_up = 0, value_pressed = -0.3, category = { categories.flight_controls, categories.stick, categories.essentials } },

But when I used these lines under "Input Commands" in "Saved Games", DCS World stopped running when I opened Options/Controls or tried to run a mission with the Phantom. So now I used the traditional command line format under Saved Games:

{pressed = iCommandPlaneTrimPitch, up = iCommandPlaneTrimPitch, value_pressed = 0.3, value_up = 0,	name = _('Trim - Nose Up Slow(Hat Aft)'), category = {categories.flight_controls, categories.stick}},
{pressed = iCommandPlaneTrimPitch, up = iCommandPlaneTrimPitch, value_pressed = -0.3, value_up = 0,	name = _('Trim - Nose Down Slow (Hat Forward)'), category = {categories.flight_controls, categories.stick}},

I entered these lines under "C:\Users\MyName\Saved Games\DCS\InputCommands\F-4E\Input\F-4E-Pilot\joystick.

Edited October 24, 2025 by LeCuvier

[TAIPAN_]

19 hours ago, LeCuvier said:

Has anybody managed to make this mod work with the F-4E Phantom? I couldn't make it work, and in the end I had to remove the sub-folders for the Phantom under "..\Input Commands\" because it blocked the DCS software completely. Heatblur uses a different structure in its "default.lua" files and I suspect that the @Quaggles mod doesn't handle that correctly.

 

Yes I have a few custom commands in C:\Users\<username>\Saved Games\DCS.openbeta\InputCommands\F-4E\Input\F-4E-Pilot\keyboard\default.lua

Attached my custom additional commands. I didn't add anything to the WSO, only the pilot.

default.lua

Edited October 25, 2025 by TAIPAN_

[LeCuvier]

5 hours ago, TAIPAN_ said:

Yes I have a few custom commands in C:\Users\<username>\Saved Games\DCS.openbeta\InputCommands\F-4E\Input\F-4E-Pilot\keyboard\default.lua

Attached my custom additional commands. I didn't add anything to the WSO, only the pilot.

default.lua 3.6 kB · 5 downloads

I see, you also used the "traditional" format of the .lua lines. That seems to work fine.

[CPS_Bomber]

Hi,

Just getting started with the idea of adding custom commands, so a question for the experienced modders:

If a function in a cockpit can be controlled by the mouse, but has no keyboard or joystick binding entry in the controls menu (for example the TACAN radio in the MB-339A), does that mean for definite that a custom command can be created for those functions by editing the appropriate lua file?

 

[LeCuvier]

6 hours ago, CPS_Bomber said:

Hi,

Just getting started with the idea of adding custom commands, so a question for the experienced modders:

If a function in a cockpit can be controlled by the mouse, but has no keyboard or joystick binding entry in the controls menu (for example the TACAN radio in the MB-339A), does that mean for definite that a custom command can be created for those functions by editing the appropriate lua file?

 

Yes. I have posted a how-to document under https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu

It explains, among other topics, how to use information from the file "clickabledata.lua" to create custom commands.

[CPS_Bomber]

2 hours ago, LeCuvier said:

Yes. I have posted a how-to document under https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu

It explains, among other topics, how to use information from the file "clickabledata.lua" to create custom commands.

Thanks - yes I've been following your excellent guide and using notepad++, so it has to be user error on my part (this is my first time trying to mod and work lua)!

So I've got the ejector seat pin working in the MB-339A, and I've got other commands that are now showing up in the control menu.....

I can assign key commands or controller buttons to these custom controls but they refuse to work when I'm in the cockpit, however they still work with mouse input

 

[LeCuvier]

15 minutes ago, CPS_Bomber said:

Thanks - yes I've been following your excellent guide and using notepad++, so it has to be user error on my part (this is my first time trying to mod and work lua)!

So I've got the ejector seat pin working in the MB-339A, and I've got other commands that are now showing up in the control menu.....

I can assign key commands or controller buttons to these custom controls but they refuse to work when I'm in the cockpit, however they still work with mouse input

 

Sorry I don't have that aircraft and can therefore not help you.

[LeCuvier]

3 hours ago, LeCuvier said:

Sorry I don't have that aircraft and can therefore not help you.

@CPS_Bomber I've downloaded the trial for the MB-339 to see what it's like. Please let me know exactly what you are trying to create, and post the lines of code.
Also, please let me know where this control is in the cockpit. If it's the ejection seat pin, I cannot spot it.

[LeCuvier]

@CPS_Bomber I think I found the darn thing. And these two lines seem to move it:
 

{down = SeatPinToCanopy, name = ('Ejection Seat Pin To Canopy V2'), category = _('Systems')},
{down = SeatPinToSeat, name = ('Ejection Seat Pin To Seat V2'), category = _('Systems')},

But I have no idea where it puts the seat pin when I hit "Seat Pin to Canopy".

[CPS_Bomber]

37 minutes ago, LeCuvier said:

@CPS_Bomber I've downloaded the trial for the MB-339 to see what it's like. Please let me know exactly what you are trying to create, and post the lines of code.
Also, please let me know where this control is in the cockpit. If it's the ejection seat pin, I cannot spot it.

Wow, thank you! 

OK I'll get info/code together and post back here

1 minute ago, LeCuvier said:

@CPS_Bomber I think I found the darn thing. And these two lines seem to move it:
 

{down = SeatPinToCanopy, name = ('Ejection Seat Pin To Canopy V2'), category = _('Systems')},
{down = SeatPinToSeat, name = ('Ejection Seat Pin To Seat V2'), category = _('Systems')},

But I have no idea where it puts the seat pin when I hit "Seat Pin to Canopy".

So the pin gets stored in the left side of the canopy frame in the front cockpit

[CPS_Bomber]

-- Eject {down = SeatPinToCanopy,377, name = _('Ejection safety pin to canopy'), category = 'Systems'}, {down = SeatPinToSeat,376, name = _('Ejection safety pin to seat'), category = 'Systems'}, -- Bus Reset                                                                 {down = BusResetGuard,233, name = _('Guard Bus Reset'), category = _('Electric Systems')}, {down = BusResetSwitch,231, name = _('Bus Reset'), category = _('Electric Systems')}, -- Internal Lights {down = iCommandPlaneCockpitIllumination,    name = _('Flood Lights'), category = _('Systems')}, {down = iCommandPlaneCockpitIllumination,    name = _('Intrument Lights'), category = _('Systems')}, {down = iCommandPlaneCockpitIllumination,    name = _('Console Lights'), category = _('Systems')}, -- Master Caution and Warning Lights {down = WarningTestButton,304, name = _('WARN LT TEST'), category = _('Electric Systems')}, -- Fuel                                                                  {down = FwdFuelQtyTest,258, name = _('Fuel Test'), category = _('Fuel Systems')}, -- Flight Instruments -- Chrono --{down = FwdCronoButton, name = _('Start/Stop/Reset Crono Aft'), category = _('Clock'}, --{down = TimeFwdDcsReal, name = _('Time Real / Mission'), category = _('Clock'},                                                          -- ADI                                                             --{down = 10040, name = _('ADI Set Pitch rotate right'), category = _('Systems'}, --{down = 10050, name = _('ADI Set Pitch rotate left'), category = _('Systems'}, -- Altimeter                                                             --{down = AltimeterPressInc, name = _('Altimeter Press Adj Right'), category = _('Systems'}, --{down = AltimeterPressDec, name = _('Altimeter Press Adj left'), category = _('Systems'}, -- HSI             --{pressed = iCommandHSI_HeadingRotaryLeft, name = _('HSI Heading rotate left'), category = _('Systems')}, --{pressed = iCommandHSI_HeadingRotaryRight, name = _('HSI Heading rotate right'), category = _('Systems')}, --{pressed = iCommandHSI_CourseRotaryLeft, name = _('HSI Course rotate left'), category = _('Systems')}, --{pressed = iCommandHSI_CourseRotaryRight, name = _('HSI Course rotate right'), category = _('Systems')}, -- Parking Brake --{down = iCommandPlaneWheelBrakeLeftOn, up = iCommandPlaneWheelBrakeLeftOff, name = _('Wheel Brake Left On/Off'), category = _('Systems')}, --{down = iCommandPlaneWheelBrakeRightOn, up = iCommandPlaneWheelBrakeRightOff,name = _('Wheel Brake Right On/Off'), category = _('Systems')}, -- Visor {down = 10601, name = 'Visor Pilot', category = 'Pilot'},

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

@LeCuvier

Ok so here's what I've been trying to work on so far regarding the keyboard lua for the MB-339A.

As I mentioned earlier I am completely new to this, so I have no doubt that there are errors aplenty here and I have much to learn!

Only the ejection seat pin commands are functioning correctly.
(the '--' at the start of some of the lines is deliberate on my part while I've been work in progress!)
The master caution, fuel. bus reset and visor commands are appearing in the control menu and will accept key binds, but nothing appears to function1 - the switches still work when using the mouse.

As far as other custom controls go, my  goal is to get everything possible functioning within the MB-339 cockpits (flight instruments, TACAN, comms radios, oxygen, breakers etc etc) to allow both keyboard and joystick/controller assigning.

Thank you for taking a look at this!

[LeCuvier]

The SeatPinToCanopy command in your list includes the argument number from "clickabledata.lua". My version does not include that argument and it works. If your version works then the argument is just useless. The stock files do not include the argument, so it's better to leave it out.

I see that a lot of the lines in your list are also commented out (-- prefix) in the stock files. That means they are work in progress and ypu should not expect them to work. It does not help to uncomment them, the software isn't ready.

I had some success creating HSI commands, using info from "clickabledata.lua". These 4 commands do work:

{pressed = FwdHsiHeadingKnob, value_pressed = 0.01, name = ('Fwd HSI Heading Decrease'), category = _('Systems')},
{pressed = FwdHsiHeadingKnob, value_pressed = -0.01, name = ('Fwd HSI Heading Increase'), category = _('Systems')},
{pressed = FwdHsiCourseKnob, value_pressed = 0.01, name = ('Fwd HSI Course Decrease'), category = _('Systems')},
{pressed = FwdHsiCourseKnob, value_pressed = -0.01, name = ('Fwd HSI Course Increase'), category = _('Systems')},

However, they are a bit "fast" when used with normal buttons. They work fine with rotary encoders though. Unfortunately, the value_pressed parameter has no effect on the "speed" of the movement.

I also tried to create an axis command with this line:

{action = FwdHsiHeadingKnob, name = ('Fwd HSI Heading Axis')},

I did get the heading pointer to move, but nothing useful.

As the HSI commands show, you will generally be able to create custom commands for elements defined in "clickabledata.lua".

However, this module seems to be far from ready, and most of the commands you create now will eventually be produced by the developers. So I'm not sure that this is time well spent.
If you want to continue, I may be able to help you with specific issues, as long as my trial period lasts. Good luck!

[CPS_Bomber]

@LeCuvier

Thank you for the response and the examples of commands you've created - again this has helped to address some misunderstanding/confusion on my part!

So from your notes it is better to work on the assumption that any lines with the '--' prefix included in the 'clickabledata.lua' should just be ignored 

I'm hoping that the developer will at some point address the lack of commands, but it has been quite some time since any meaningful updates were released for the MB-339. For my part I'm happy to continue experimenting and learning about adding custom commands in the meantime 

Cheers!


 

[LeCuvier]

2 hours ago, CPS_Bomber said:

@LeCuvier

...So from your notes it is better to work on the assumption that any lines with the '--' prefix included in the 'clickabledata.lua' should just be ignored 

 

Yes, these lines were entered maybe as reminders for work to be done going forward, or lines that were put "on ice" due to something not working as intended. In either case they are not operational.
I certainly don't want to discourage you; you obviously like the challenge. Good luck, and enjoy!

[mukisuki]

Maybe someone can help me on this topic..

As i am using two Key bindings on my Joystick for collective up and down, i find this new Keybinding  for MI-24 very useful.. as the collective is moving more slowly then normal, even i can it slow down more by changing the values...

{cockpit_device_id = devices.ENGINE_INTERFACE, pressed = engine_commands.COLLECTIVE, value_pressed = -0.0025,  name=_('Collective Stick - DOWN (Very Slow)'), category = {_('Ins Collective Stick'), _('Flight Control'), _('Custom')}

Can something similar be injected to the KA50-3, OH58 Kiowa, Gazelle ? As i am to old and maybe to stupid  to learning to program this things, i would ask for help here

Thanks in advance 

[LeCuvier]

3 hours ago, mukisuki said:

Maybe someone can help me on this topic..

As i am using two Key bindings on my Joystick for collective up and down, i find this new Keybinding  for MI-24 very useful.. as the collective is moving more slowly then normal, even i can it slow down more by changing the values...

{cockpit_device_id = devices.ENGINE_INTERFACE, pressed = engine_commands.COLLECTIVE, value_pressed = -0.0025,  name=_('Collective Stick - DOWN (Very Slow)'), category = {_('Ins Collective Stick'), _('Flight Control'), _('Custom')}

Can something similar be injected to the KA50-3, OH58 Kiowa, Gazelle ? As i am to old and maybe to stupid  to learning to program this things, i would ask for help here

Thanks in advance 

The Ka-50 III unfortunately uses "hardcoded" commands like "iCommandPlaneCollectiveIncrease". They have no arguments that you could modify. Also, these commands are not clickable and therefore are not represented in "clickabledata.lua". I see no way for these commands to create variants.
In the AH-64 it's the same situation.
I don't have the other choppers, so can't try.

[Gabreil]

You know when you just cannot get your head around something - be it simple or complicated..  I just can't get my head around getting this to work.   I've got custom key binds for the SA342 and the CH47 both of which I get working by editing the main core default.lua files.    I'd like to do it via Quaggles.   I use OVGME as my mod manager.. but I just can't seem to get it to work.. I'm doing something wrong.    Could someone give some step by step in terms a 5 year old can understand..  I'd be very grateful!

 

[virgo47]

4 hours ago, Gabreil said:

You know when you just cannot get your head around something - be it simple or complicated..  I just can't get my head around getting this to work.   I've got custom key binds for the SA342 and the CH47 both of which I get working by editing the main core default.lua files.    I'd like to do it via Quaggles.   I use OVGME as my mod manager.. but I just can't seem to get it to work.. I'm doing something wrong.    Could someone give some step by step in terms a 5 year old can understand..  I'd be very grateful!

I've made a few posts about Quaggles and how essential it is - so check this one:

There is no gain without at least some pain - but the point is: a) Quaggles go to installation dir and needs to be cared for after updates (e.g. in my case, when I see update is available, I start OpenMod Man, remove all active mods, install the update and then reapply the mods); b) the rest of the magic, and most importantly, all your custom configuration, happens under Saved Games and you don't have to do anything after updates (unless the update is incompatible with current Quaggles, but the guy(s) typically fix it within hours, crazy support really).

That's it. Except... sometimes you have to figure out where exactly should the configs be. Most modules follow one structure, but not all.

Edited February 7 by virgo47

[Gabreil]

@virgo47  Well that certainly helped.   Reading though your post and going back over the Quaggles instructions I figured where I was going wrong..   On the Quaggles page is says:

3. Extract the zip
4. Find the DCS-Input-Command-Injector-Quaggles/Scripts folder
5. Move it into your DCSWorld/ folder
   
   What I was doing was moving the full DCS-Input-Command....\Script to the root of DCSWorld   -  My mistake was its on the Scripts folder that moves!    By just moving the Scripts folder with the data.lua to DCSWord (and overwriting the current data.lua)  It then started to work.   Finally after many attempts I'm up and working with it
   
   Thanks for the pointers, it focused my mind and got it working

[imacken]

Is anyone able to do some code to input an axis for HUD brightness in A-10C II?