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

[Gabreil]

HI, 

I got this all installed last night and it appears to be working... I see custom fields in the Huey for example.  However, when i select the Gazelle, I do not see any of the custom options listed.   I was trying to use it to allow the keybinds for the Artifical Horizion button.   

I'll assume its working correctly as said above, i do see custom options.    What would be the reason for the cutsom options not appearing in the Gazelle SA342 Pilot list?

 

[RedeyeStorm]

The most simple answer would be that none are made. You can check in the mods control lua if there are any custom inputs there. Sorry that I am vage about where and what file you need but I am away from pc.

[Gabreil]

Thanks,  i've checked the column and expanded it out, but nothing there for the custom binds.  I did a copy/paste of some of the custom binds in the community keybinds directly into the actual SA342 .lua and those immediatly showed up..   As said, the custom binds show for the UH-1.   Bit strange nothing appears for the SA342.   No big deal, all i really needed was the keybind to reset the Artifical Horizon.

I'd still be interested to hear anything else that i could check to get this working.

[speed-of-heat]

I wonder if the folder structure needs to change to accommodate the new pilot gunner co-pilot  pilot split ?

[Gabreil]

As in the script files might not at this time take that into account, thus mine not working?   I guess if thats the case and someone new has these issues, then at least reading this will give them a steer in the right direction and prevent hours of trying to get it to work.  

[speed-of-heat]

1 hour ago, Gabreil said:

As in the script files might not at this time take that into account, thus mine not working?   I guess if thats the case and someone new has these issues, then at least reading this will give them a steer in the right direction and prevent hours of trying to get it to work.  

yeah its a complete WAG ... but 

[jeni1976]

 

Good afternoon, Guys! Who has a configured config code for 'zoom' in the cockpit? I use Trakir5 and mouse control instead of joy.

I would be grateful for any help

Source link in description https://www.digitalcombatsimulator.com/en/files/3311376/

Below is a code example. I don’t know if it’s correct or not.

 

return {
    keyCommands = {
        -- COCKPIT VIEW FOV / ZOOM PRESETS
        {down = iCommandViewAngleDefault, name = _('Default zoom'), category =  _('View Cockpit absolute FOV')},

        {down = iCommandViewZoomAbs, up = iCommandViewAngleDefault, value_down =  1.00, name = _('Instant +1.00 zoom until release'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, up = iCommandViewAngleDefault, value_down =  0.80, name = _('Instant +0.80 zoom until release'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, up = iCommandViewAngleDefault, value_down =  0.60, name = _('Instant +0.60 zoom until release'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, up = iCommandViewAngleDefault, value_down =  0.40, name = _('Instant +0.40 zoom until release'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, up = iCommandViewAngleDefault, value_down =  0.20, name = _('Instant +0.20 zoom until release'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, up = iCommandViewAngleDefault, value_down =  0.00, name = _('Instant  0.00 zoom until release'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, up = iCommandViewAngleDefault, value_down = -0.20, name = _('Instant -0.20 zoom until release'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, up = iCommandViewAngleDefault, value_down = -0.40, name = _('Instant -0.40 zoom until release'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, up = iCommandViewAngleDefault, value_down = -0.60, name = _('Instant -0.60 zoom until release'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, up = iCommandViewAngleDefault, value_down = -0.80, name = _('Instant -0.80 zoom until release'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, up = iCommandViewAngleDefault, value_down = -1.00, name = _('Instant -1.00 zoom until release'), category =  _('View Cockpit absolute FOV')},

        {down = iCommandViewZoomAbs, value_down =  1.00, name = _('Instant +1.00 zoom'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, value_down =  0.80, name = _('Instant +0.80 zoom'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, value_down =  0.60, name = _('Instant +0.60 zoom'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, value_down =  0.40, name = _('Instant +0.40 zoom'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, value_down =  0.20, name = _('Instant +0.20 zoom'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, value_down =  0.00, name = _('Instant  0.00 zoom'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, value_down = -0.20, name = _('Instant -0.20 zoom'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, value_down = -0.40, name = _('Instant -0.40 zoom'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, value_down = -0.60, name = _('Instant -0.60 zoom'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, value_down = -0.80, name = _('Instant -0.80 zoom'), category =  _('View Cockpit absolute FOV')},
        {down = iCommandViewZoomAbs, value_down = -1.00, name = _('Instant -1.00 zoom'), category =  _('View Cockpit absolute FOV')},

        {down = iHeadTrackerZoomToggle, value_down = 1.0, name = _('VR Zoom IN'), category =  _('VR extra')},
        {down = iHeadTrackerZoomToggle, value_down = 0.0, name = _('VR Zoom OUT'), category =  _('VR extra')},

        {down = iHeadTrackerSpyglassZoomToggle, value_down = 1.0, name = _('VR Spyglass Zoom IN'), category =  _('VR extra')},
        {down = iHeadTrackerSpyglassZoomToggle, value_down = 0.0, name = _('VR Spyglass Zoom OUT'), category =  _('VR extra')}
    }
}

Thank you very much for the wonderful mod! 

Made it myself on a Su-25T

c:\Users\Admin\Saved Games\DCS\InputCommands\Su-25T\input\Su-25T\keyboard\default.lua

default.lua

Edited August 10, 2024 by jeni1976

[Quaggles]

@jeni1976 if you want to use those commands for all aircraft you should be able to put that lua file in:

"~\Saved Games\DCS\InputCommands\UiLayer\keyboard\default.lua" and 

"~\Saved Games\DCS\InputCommands\UiLayer\joystick\default.lua"

That way you won't have to set it it up again for every plane you fly, that looks like how the mod author intended it to be used.

[jeni1976]

В 10.08.2024 в 22:24, Quaggles сказал:

@jeni1976 if you want to use those commands for all aircraft you should be able to put that lua file in:

"~\Saved Games\DCS\InputCommands\UiLayer\keyboard\default.lua" and 

"~\Saved Games\DCS\InputCommands\UiLayer\joystick\default.lua"

That way you won't have to set it it up again for every plane you fly, that looks like how the mod author intended it to be used.

Good afternoon Thank you very much, I tried to register it this way, but the sub/panel of the 'zoom' configuration settings does not work in any aircraft. It seems like I’m registering all the paths correctly!!?

[Quaggles]

11 minutes ago, jeni1976 said:

Good afternoon Thank you very much, I tried to register it this way, but the sub/panel of the 'zoom' configuration settings does not work in any aircraft. It seems like I’m registering all the paths correctly!!?

Hmm it worked for me, when you inject 'InputCommands\UiLayer' commands you find them in 'UI Layer' category, are you checking there?

 

[jeni1976]

3 часа назад, Quaggles сказал:

Hmm it worked for me, when you inject 'InputCommands\UiLayer' commands you find them in 'UI Layer' category, are you checking there?

 

I'm sorry, I was looking in the wrong place. Thanks for the clarification and Screenshot of the settings

[jeni1976]

Good day, Guys. Please tell me the name of the folders for the Su 30 mod. I tried to register it, but it didn’t work for me. Thank you

https://forum.dcs.world/topic/247098-dcs-su-30mk-mod/

[MAXsenna]

Good day, Guys. Please tell me the name of the folders for the Su 30 mod. I tried to register it, but it didn’t work for me. Thank you
https://forum.dcs.world/topic/247098-dcs-su-30mk-mod/

What do you mean? Like for making an input folder, liveries etc? Just look in your input folder I guess.

Sent from my SM-A536B using Tapatalk

[jeni1976]

46 минут назад, MAXsenna сказал:

What do you mean? Like for making an input folder, liveries etc? Just look in your input folder I guess.

Sent from my SM-A536B using Tapatalk
 

I can’t figure out how to name the folder correctly so that my commands appear in the keyboard settings of the Su-30 mod

 

Where is the Question Mark I don’t know what to name the folder for the Su 30 mod A clear example c:\Users\Admin\Saved Games\DCS\InputCommands\???? \input\???? \keyboard\default.lua

Edited October 14, 2024 by jeni1976

[MAXsenna]

I can’t figure out how to name the folder correctly so that my commands appear in the keyboard settings of the Su-30 mod

Right. Don't have that one. It's in the files of it somewhere.

Sent from my SM-A536B using Tapatalk

[rrutko]

In the last few game updates, when I reenable this mod other modules controls will just disapear completly. Example I have AH64 binds I use but when i go to check on A10C2 controls they are non existant (all controls, blank screen). The only way to fix that is to repair DCS and then it resets the command injector mod. any thoughts? Injector mod has the latest update.

Edited December 7, 2024 by rrutko

[MAXsenna]

In the last few game updates, when I reenable this mod other modules controls will just disapear completly. Example I have AH64 binds I use but when i go to check on A10C2 controls they are non existant (all controls, blank screen). The only way to fix that is to repair DCS and then it resets the command injector mod. any thoughts? Injector mod has the latest update.

That's really strange. Work's perfectly for me. No issues.

Sent from my SM-A536B using Tapatalk

[Quaggles]

2 hours ago, rrutko said:

In the last few game updates, when I reenable this mod other modules controls will just disapear completly. Example I have AH64 binds I use but when i go to check on A10C2 controls they are non existant (all controls, blank screen). The only way to fix that is to repair DCS and then it resets the command injector mod. any thoughts? Injector mod has the latest update.

Upload a copy of `C:\Users\<USERNAME>\Saved Games\DCS\Logs\dcs.log` here when the blank control screen happens, that might give some hints.

[rrutko]

dcs.logSorry for the delay. My A10C2 controls are blank. I have not checked any others yet.

 

Edited December 15, 2024 by rrutko

[Quaggles]

I just retested in the lastest DCS version with the latest version of the mod and using the A-10C II keybinds from https://github.com/Munkwolf/dcs-community-keybinds and it's working for me. It looks like the error is happening because the lua command entry files you are trying to inject aren't returning a lua table.

Also just double check you are using the latest version of the mod (1.0.12). I just realised that the first post of this thread said 1.0.12 but was actually linking to the 1.0.11 release due to some weird behaviour when I edited the post (I've fixed it now), so you might have downloaded the older version that's incompatible with the newest DCS version. Latest version is here https://github.com/Quaggles/dcs-input-command-injector/releases/tag/1.0.12.

If that doesn't work could you send me the InputCommands lua files you are trying to inject so I can try to replicate, I might write a check in the mod so it won't break the controls menu if an invalid lua file is injected.

[rrutko]

Ok that fixed the blank controls pages, But now the custom inputs are not listed at all (no "custom" in the drop down menu OR custom input controls listed). I installed the "InputCommands" into saved games/dcsopenbeta

EDIT: I got it to work via hand replacing the files instead of OvGME. I just need to dig deeper into that on my end I think. Thank you for the correct file.

 

 

 

Edited December 15, 2024 by rrutko

[LeCuvier]

There is no point trying to manage the custom Input files with OvGME because they are under "Saved Games" and updates don't affect them.
The only file that needs to be managed with OvGME is the "Data.lua".

[LeCuvier]

F-4E Phantom issue:

I was trying to make WSO commands (e.g. Radar Mode) available for the pilot. So I added "...\Saved Games\DCS\InputCommands\F-4E-Pilot\joystick" to the "InputCommands" folder with files "default.lua" and "Throttle - HOTAS Warthog.lua", and added this line of code into the skeleton structure of both:

knob('Radar Mode', { 'BST', 'Radar', 'Map', 'Air-Ground', 'Beacon', 'TV' }, nil, device_commands.RADAR_Mode_Knob_RIO, device_commands.RADAR_Mode_Knob_RIO_INC_DEC, device_commands.RADAR_Mode_Knob_RIO_NEXT, device_commands.RADAR_Mode_Knob_RIO_AXIS, bind_templates.radar_panel()),

Unfortunately, the command "Radar Mode" is still not available for the pilot.
When I added the LUA line directly into the files in the game folder structure, the command became available for the pilot. So there is nothing wrong with the LUA line.
I tried to find inspiration in @Munkwolf's community project, but did not see anything for the F-4E. Is there a structural problem with that aircraft module?

Edit: I corrected the folder structure under "InputCommands" to "...\Saved Games\DCS\InputCommands\F-4E\F-4E-Pilot\joystick" but that did not solve the issue.

Edited December 17, 2024 by LeCuvier

[sobe]

LeCuvier

Please explain:  When I added the LUA line directly into the files in the game folder structure.   Exactly where did you put it?

 

[LeCuvier]

10 hours ago, sobe said:

LeCuvier

Please explain:  When I added the LUA line directly into the files in the game folder structure.   Exactly where did you put it?

 

In the file "K:\Eagle Dynamics\DCS World\Mods\aircraft\F-4E\Input\F-4E-Pilot\keyboard\default.lua", local function "binds".
Through some magic which I cannot figure out, the commands defined in "...\keyboard\default.lua" are made available to all game controllers.

This module is really different!