More keybinds needed

[MAXsenna]

I wouldn't know what to do with those Lua files. You should put them into a OVGME Mod pack and offer them as a download. 

Now, that's where Quaggles and Munkwolf's repository comes in handy. You just copy the files to the correct place!

Sent from my SM-A536B using Tapatalk

[_Hoss]

I don't use their software. 

[MAXsenna]

I don't use their software. 

Yeah, I know. We have established that before. While you should look into it. It's not even software per say. It's just a bunch of pre-made Lua files, so you don't have to mess with it. And only one file to copy/deploy after every update.

Sent from my SM-A536B using Tapatalk

[_Hoss]

"The correct place"............ If I were good at finding the lua files I probably wouldn't need the other two software items. I could just do it my self and create a mod I could install and uninstall. 

The controls he has done new lua for are not really a problem with me, I really want the fuel selector switch to work as the Jug and mustangs does.

 

 

Edited June 28 by _Hoss

[MAXsenna]

If I were good at finding the lua files I probably wouldn't need the other two software items. I could just do it my self and create a mod I could install and uninstall. 
 

That's the whole point. You don't need to make mod to install after every update. And you don't have to update said mod every time you need something new. You just apply the one mod after update, Quaggles. The rest is kept in Saved Games. I give up.

Sent from my SM-A536B using Tapatalk

[_Hoss]

2 minutes ago, MAXsenna said:

That's the whole point. You don't need to make mod to install after every update. And you don't have to update said mod every time you need something new. You just apply the one mod after update, Quaggles. The rest is kept in Saved Games. I give up.

Sent from my SM-A536B using Tapatalk
 

Thanks for the input, but like I said, the Hog as is, isn't that bad, and his fixes aren't a niggling necessity for me. 

Edited June 28 by _Hoss

[Steel Jaw]

Show pilot needs to be mappable to controller.

[Mistermann]

https://forum.dcs.world/topic/375336-show-pilot-body-hotas-bind-not-possible/#findComment-5660879

[LeCuvier]

The developer has fixed some of the weapons-related bindings. See edits in my earlier post: https://forum.dcs.world/topic/375038-more-keybinds-needed/#elControls_5662978_menu

[gdx65]

Posted a question in here about not able to key bind the auto start and auto stop, then found this dedicated F4I-1D section…

 

Edited July 6 by gdx65

[LeCuvier]

14 hours ago, gdx65 said:

Posted a question in here about not able to key bind the auto start and auto stop, then found this dedicated F4I-1D section…

If you want to bind it to a button on a game controller, you need to make a very simple edit in the file "default.lua" under "disk location:\Eagle Dynamics\DCS World\Mods\aircraft\F4U-1D\Input\joystick" by copying a line from the "default.lua" under "disk location\Eagle Dynamics\DCS World\Mods\aircraft\F4U-1D\Input\keyboard" and pasting it into the file under "...\joystick". Since most people don't want to get into that, I won't go into more detail now.

[gdx65]

Hi and thanks. I am familiar with editing the .lua file. Just did not think about that as I am not an expert into this type of details but can edit with confidence if guided.

Edited July 7 by gdx65

[LeCuvier]

12 hours ago, gdx65 said:

Hi and thanks. I am familiar with editing the .lua file. Just did not think about that as I am not an expert into this type of details but can edit with confidence if guided.

These are the two lua lines for auto-start and auto-stop:

{combos = {{key='Home',reformers={'LWin'}}}, down = device_commands.AutoStart, cockpit_device_id = devices.AUTOSTART, value_down = 1.0, name = _('Autostart Procedure'), category = _('Engine')},
{combos = {{key='End',reformers={'LWin'}}}, down = device_commands.AutoStop, cockpit_device_id = devices.AUTOSTART, value_down = 1.0, name = _('Autostop Procedure'), category = _('Engine')},

For general guidance on the subject, see here: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu

[gdx65]

Hi, fantastic, thanks for the script, I will give a try.

[gdx65]

On 7/8/2025 at 12:32 PM, LeCuvier said:

These are the two lua lines for auto-start and auto-stop:

{combos = {{key='Home',reformers={'LWin'}}}, down = device_commands.AutoStart, cockpit_device_id = devices.AUTOSTART, value_down = 1.0, name = _('Autostart Procedure'), category = _('Engine')},
{combos = {{key='End',reformers={'LWin'}}}, down = device_commands.AutoStop, cockpit_device_id = devices.AUTOSTART, value_down = 1.0, name = _('Autostop Procedure'), category = _('Engine')},

For general guidance on the subject, see here: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu

Hi,

Ok I finally found the time to check this in the LUA file. (By the way the pdf guide in the link you shared cannot download ?!?)

I have added the two scirt in teh F4U1D LUA file but cannot see any changes in the Controls section, Autostart and Autosop still disabled. Attached a screenshot of the LUA file now with the script. Maybe they should be placed not at the beginning? Thanks.

[Ala13_Kokakolo]

I would like to bind a key in my joy for the stopwatch to start/stop but I cannot see any on the list.

[LeCuvier]

9 hours ago, gdx65 said:

Hi,

Ok I finally found the time to check this in the LUA file. (By the way the pdf guide in the link you shared cannot download ?!?)

I have added the two scirt in teh F4U1D LUA file but cannot see any changes in the Controls section, Autostart and Autosop still disabled. Attached a screenshot of the LUA file now with the script. Maybe they should be placed not at the beginning? Thanks.

 

Sorry, I goofed. Forgot to remove the key commands. This should work for you:

{down = device_commands.AutoStart, cockpit_device_id = devices.AUTOSTART, value_down = 1.0, name = _('Autostart Procedure'), category = _('Engine')},
{down = device_commands.AutoStop, cockpit_device_id = devices.AUTOSTART, value_down = 1.0, name = _('Autostop Procedure'), category = _('Engine')},

I tested it this time and it works.

Edit: I went to the post with the PDF file and I downloaded it in the normal process. No idea what went wrong for you.

Edited yesterday at 07:27 AM by LeCuvier

[LeCuvier]

1 hour ago, Ala13_Kokakolo said:

I would like to bind a key in my joy for the stopwatch to start/stop but I cannot see any on the list.

If you are willing to add a line in the "default.lua" under "joystick\" or under "keyboard\" you can create it for yourself. This is the line:

{down = device_commands.Clock_Chronograph_Button, up = device_commands.Clock_Chronograph_Button, cockpit_device_id = devices.CLOCK, value_down = 1.0, value_up = 0.0, name = _('Chronometer Start/Stop/Reset'), category = _('Flight Control')},

I tested it and it works just fine. I don't like the category "Flight Control" for the chronometer, but I didn't find a suitable one. You can change it to whatever you want.

[gdx65]

9 hours ago, LeCuvier said:

Sorry, I goofed. Forgot to remove the key commands. This should work for you:

{down = device_commands.AutoStart, cockpit_device_id = devices.AUTOSTART, value_down = 1.0, name = _('Autostart Procedure'), category = _('Engine')},
{down = device_commands.AutoStop, cockpit_device_id = devices.AUTOSTART, value_down = 1.0, name = _('Autostop Procedure'), category = _('Engine')},

I tested it this time and it works.

Edit: I went to the post with the PDF file and I downloaded it in the normal process. No idea what went wrong for you.

Ok I have now added you new script under --/N/ Engine *********************************************************************************** and it works, thanks (for info, see screenshot LUA screen 03)

However I see at the bottom of the LUA file these scripts were there but under -- Autostart ****************************************** (See screenshot LUA screen02))

BTW I managed to download the pdf by using MS Edge, Chromes does not allow me (need check).

[LeCuvier]

13 minutes ago, gdx65 said:

 

Good catch! Actually embarrassing for the developer. These lines would have worked if they had put them into the key commands section of the file (after this line):
join(res.keyCommands,{

But they put them into the Axis section, (after this line):
join(res.axisCommands,{

And that obviously cannot work.

[Ala13_Kokakolo]

22 hours ago, LeCuvier said:

If you are willing to add a line in the "default.lua" under "joystick\" or under "keyboard\" you can create it for yourself. This is the line:

{down = device_commands.Clock_Chronograph_Button, up = device_commands.Clock_Chronograph_Button, cockpit_device_id = devices.CLOCK, value_down = 1.0, value_up = 0.0, name = _('Chronometer Start/Stop/Reset'), category = _('Flight Control')},

I tested it and it works just fine. I don't like the category "Flight Control" for the chronometer, but I didn't find a suitable one. You can change it to whatever you want.

Thanks!!

[Captain Orso]

Does anyone have discreet settings for the fuel mixture selector?:

Idle Cutoff
Auto Lean
Auto Rich

[LeCuvier]

2 hours ago, Captain Orso said:

Does anyone have discreet settings for the fuel mixture selector?:

Idle Cutoff
Auto Lean
Auto Rich

These lines seem to do it: 

{down = device_commands.Mixture_control, cockpit_device_id = devices.ENGINE, value_down = 0.0, name = _('Mixture Cutoff'), category = _('Engine')},
{down = device_commands.Mixture_control, cockpit_device_id = devices.ENGINE, value_down = 0.33, name = _('Mixture Auto-Lean'), category = _('Engine')},
{down = device_commands.Mixture_control, cockpit_device_id = devices.ENGINE, value_down = 0.66, name = _('Mixture Auto-Rich'), category = _('Engine')},

 

[Captain Orso]

15 minutes ago, LeCuvier said:

These lines seem to do it: 

{down = device_commands.Mixture_control, cockpit_device_id = devices.ENGINE, value_down = 0.0, name = _('Mixture Cutoff'), category = _('Engine')},
{down = device_commands.Mixture_control, cockpit_device_id = devices.ENGINE, value_down = 0.33, name = _('Mixture Auto-Lean'), category = _('Engine')},
{down = device_commands.Mixture_control, cockpit_device_id = devices.ENGINE, value_down = 0.66, name = _('Mixture Auto-Rich'), category = _('Engine')},

 

YES!! Thank you!! Most excellent!!