No key bind for arming ejection seat

[Scorpion27]

I can't find in "options/adj conrol" a key bind for arming ejection seat (EJECTION CONTROLS ARMED) lever - left front of seat.

It is a kind of pain in the neck for home cockpit VR to search blind for mouse just to arm ejection seat, while everything else can be done by buttons etc.

Cheers

 

[LeCuvier]

adding the line of code below to the file "default.lua" gives you a command binding for a maintained 2-position ON/OFF switch. ON = Locked, OFF = Armed:

{down = cpt_commands.EjectionSafetyLever, up = cpt_commands.EjectionSafetyLever, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.CPT_MECH, name = _('Ejection Safety Lever 2-Pos ARMED/LOCKED'), category = {_('Systems')}},

If you don't have such a switch or prefer to use a pair of pushbuttons, you need to add these 2 lines of code:

{down = cpt_commands.EjectionSafetyLever, value_down = 1.0, cockpit_device_id = devices.CPT_MECH, name = _('Ejection Safety Lever ARMED'), category = {_('Systems')}},
{down = cpt_commands.EjectionSafetyLever, value_down = 0.0, cockpit_device_id = devices.CPT_MECH, name = _('Ejection Safety Lever LOCKED'), category = {_('Systems')}},

 

[Skligmund]

Excellent, I was just coming on here to ask about the same thing. I can currently fly an entire mission starting cold and dark without touching my keyboard or mouse other than the ejection seat arming and AI comms.

[AKA_Clutter]

Hi all,

I am trying to get this to work and am having some trouble.  I have added the above line to both the DCS Install folder\mods\aircraft\F-16c\input\joystick\default.lua and the  DCS Install folder\mods\aircraft\F-16c\input\keyboard\default.lua files.  It shows up int the control setup as an assignable keyboard command but it doesn't show up as an assignable joystick/throttle command.  I also tried adding it to just the joystick dafault.lua file, but that didn't work either.

I added the command at the bottom of the file, just before the end of rile/return.

Any idea of what I'm doing wrong?

Edited May 22, 2023 by AKA_Clutter

[LeCuvier]

14 hours ago, AKA_Clutter said:

...I added the command at the bottom of the file, just before the end of rile/return.

 

That's definitively the wrong insert point. It must be inserted after these lines (beginning of the file)

local cockpit = folder.."../../../Cockpit/Scripts/"
dofile(cockpit.."devices.lua")
dofile(cockpit.."command_defs.lua")

local res = external_profile("Config/Input/Aircrafts/common_joystick_binding.lua")

join(res.keyCommands,{

and before these lines (near the end of file):

})

-- joystick axes 
join(res.axisCommands,{

I recommend to insert near the beginning of the file.

[AKA_Clutter]

2 hours ago, LeCuvier said:

... .... .....

and before these lines (near the end of file):

})

-- joystick axes 
join(res.axisCommands,{

I recommend to insert near the beginning of the file.

Works like a charm now.

And it makes sense.  With them at the bottom of the file, it would treat the line as an axes.

Thanks!

[Aronis]

Was looking for same thing, will this modification make you have issues on-line gaming???

 

Mike

[Pribs86]

Can DCS make this change? I don't really like going into the code or whatever it's called. Don't want to screw something up worse or violate any multiplayer authentication as well.

[LeCuvier]

6 hours ago, Pribs86 said:

Can DCS make this change? I don't really like going into the code or whatever it's called. Don't want to screw something up worse or violate any multiplayer authentication as well.

Of course they can. But they obviously don't see this as a priority. This thread starts in January 2021 and they have never responded in any way.

[Pribs86]

On 4/14/2025 at 2:56 AM, LeCuvier said:

Of course they can. But they obviously don't see this as a priority. This thread starts in January 2021 and they have never responded in any way.

It was a rhetorical question, sorry.

[YoYo]

On 1/23/2021 at 10:14 AM, Scorpion27 said:

I can't find in "options/adj conrol" a key bind for arming ejection seat (EJECTION CONTROLS ARMED) lever - left front of seat.

It is a kind of pain in the neck for home cockpit VR to search blind for mouse just to arm ejection seat, while everything else can be done by buttons etc.

Cheers

 

Hello ED, can you add it too? F-16C hasnt still this 2 buttons ....

The other topic:

@Flappie , any chances? Maybe it's just a small matter and half an hour of work?

[Scott-S6]

This is the one startup element which requires me to use the mouse, which is very annoying. Everything else is bound in my cockpit.

[Red Dog]

Kind bump for this to be added please

[Mapi]

@ ED

How long does it take?

3 to 4 weeks?

[LeCuvier]

12 hours ago, Mapi said:

@ ED

How long does it take?

3 to 4 weeks?

 

It took me about 15 minutes plus a bit of testing time, to add a line into the "default.lua" for "UI Layer", so it works across all aircraft modules. 

[Pribs86]

3 hours ago, LeCuvier said:

It took me about 15 minutes plus a bit of testing time, to add a line into the "default.lua" for "UI Layer", so it works across all aircraft modules. 

Any other fixes for those of us who don't know how to code or add lua lines? Thanks in advance!

[MAXsenna]

Any other fixes for those of us who don't know how to code or add lua lines? Thanks in advance!

Don't remember if I have suggested this to you before, but have a look at Quaggles Keybind Injector. It's a small single file you can push after every update, (with a mod manager), and doesn't break IC. Then you can keep all your edits in your Saved Games. Add Munkwolf's Keybind Repository, and you will have many missing keybinds premade for you.

Cheers!

Sent from my SM-A536B using Tapatalk

[MAXsenna]

4 hours ago, LeCuvier said:

It took me about 15 minutes plus a bit of testing time, to add a line into the "default.lua" for "UI Layer", so it works across all aircraft modules. 

Hold on! You can add both the triple and single press keybind for ejection to the UI Layer? And it works in every module, even 3rd parties? That's pretty neat, and I guess it works because as @BIGNEWY told me in another thread today that it's hard coded in the core. The triple sequence that is.

Edit: If this works in the UI Layer, it should work in the General category too, and that's probably a better place, and should absolutely be implemented by ED. 

Edited yesterday at 04:08 PM by MAXsenna

[BIGNEWY]

19 minutes ago, MAXsenna said:

because as @BIGNEWY told me in another thread today that it's hard coded in the core.

x3 ctrl + e is hardcoded in dcs has been for over 16 years, as I mentioned we do have a request for a single button eject and have done for some time, but it is very low priority. 

thank you 

[MAXsenna]

10 minutes ago, BIGNEWY said:

x3 ctrl + e is hardcoded in dcs has been for over 16 years, as I mentioned we do have a request for a single button eject and have done for some time, but it is very low priority. 

thank you 

Yeah, I know. Apologies for pestering you yet again. But if this can implemented in two simple commands as both 3x and 1x in the general category across all modules, it would be worth pursuing IMHO.

[BIGNEWY]

8 minutes ago, MAXsenna said:

Yeah, I know. Apologies for pestering you yet again. But if this can implemented in two simple commands as both 3x and 1x in the general category across all modules, it would be worth pursuing IMHO.

as mentioned if we do it for one we would have to do it for all, then we have to pull a dev from other tasks to do it, and it just isn't high enough priority to do that. The most I can do is bump the report internally. 

thank you 

 

[Pribs86]

I personally don't care for the 1x button press for the ejection seat, but I know some do, which is great. But I just want a binding so I can arm the seat with my button box - same button box I use to close the canopy and open/close the canopy safety latch. So it's in the same place like all the other jets I fly and don't have to keep clicking it with the mouse. Thanks for the consideration and passing this along! Appreciate you!

[MAXsenna]

6 minutes ago, BIGNEWY said:

as mentioned if we do it for one we would have to do it for all, then we have to pull a dev from other tasks to do it, and it just isn't high enough priority to do that. The most I can do is bump the report internally. 

thank you 

 

Yes, I'm well aware, and I pinged you by mistake. Not trying to argue at all.  The UI Layer and General are global for all modules, that's my point. And neither ED nor 3rd party devs would ever have to touch the ejection sequence in any module ever after. After all it's obvious your devs are heading in that direction seeing more and keybinds that are identical across modules are moved to common categories and that's awesome for us users!

I know you have brought the request further, so I don't expect anymore than that.  

3 minutes ago, Pribs86 said:

I personally don't care for the 1x button press for the ejection seat, but I know some do, which is great.

Personally, I use a macro on one of macro keyboards on an Esc key, which is even lighted red. VoiceAttack too for good measure. But I plan to make a handle, and that's where it comes in handy, and I'll add the arming keybind to the same contraption.

[LeCuvier]

1 hour ago, MAXsenna said:

Hold on! You can add both the triple and single press keybind for ejection to the UI Layer? And it works in every module, even 3rd parties? That's pretty neat, and I guess it works because as @BIGNEWY told me in another thread today that it's hard coded in the core. The triple sequence that is.

Edit: If this works in the UI Layer, it should work in the General category too, and that's probably a better place, and should absolutely be implemented by ED. 

My added line actually triggers the "Eject" command 3 times with a single button press. Twice when you push the button down, and once when you release the button.
This is the LUA line:

{down = iCommandPlaneEject,	pressed = iCommandPlaneEject, up = iCommandPlaneEject,	name = _('Eject (press once)'),	category = _('Systems')},		

And of course I have all modded "default.lua" files under saved games, using the Command Injector by @Quaggles, so I don't have to mess around after every update. 
Is "General" a better place than "UI Layer"? I wouldn't know why.

[MAXsenna]

12 minutes ago, LeCuvier said:

Is "General" a better place than "UI Layer"? I wouldn't know why.

Just my personal opinion for consistency, as in General we have commands that are identical across the modules, while the UI Layer have more of the User Interface commands.