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 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 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.