LeCuvier

It looks like Work In Progress. When you open the file "clickabledata.lua" with Notepad++ and go to the section "HOTAS Stick" you will see that there are lines for all HOTAS buttons, but the majority of them is commented out (preceded by a "--" and therefore displayed in green.
This indicates to me, that the animation of these button is intended but the related code is not ready. The Weapon Release Button line is black and therefore active, and this button is indeed animated and clickable in the cockpit. See attached screenshot.

Edit:
Don't forget, the Hornet is still in Early Access!
Edit 2:
I just realize this post is tagged with "Cannot reproduce". That seems inappropriate. It should be tagged "W.I.P."

The work-around requires addition of this line of code
{down = device_commands.Button_3, up = device_commands.Button_3, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 1.0, value_up = 0.0, name = _('Master Arm 2-Pos. ON/OFF'), category = _('Weapon System')}, to the file "default.lua" under "K:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FW-190D9\Input\FW-190D9\joystick".
Go to https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu for a how-to document for making such edits.

I'm a lazy fellow. Therefore, instead of writing a very long post about the basic process, I attach a how-to document I wrote mostly for myself. Please read through this and I hope it makes sense to you! It's somewhat complex as you need to add a .lua file for the monitor configuration, and make entries in Options/System that essentially allocate the real estate on your monitor(s), plus appropriate Windows display settings.
The basic process as described in the document works perfectly for those displays that ED has enabled for export, like the MFD's. ED apparently think that the RWR is not worth exporting and therefore have not made provision for it. So we need to add a few lines into the file "RWR_ALR56_init.lua" located under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Cockpit\Scripts\EWS\RWR\indicator". When you open the file with Notepadd++ you will see these lines at the beginning:
 
dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.8 shaderLineDefaultFuzziness = 0.4 shaderLineDrawAsWire = false shaderLineUseSpecularPass = true and so forth... Add these lines below "indicator_type = indicator_types.COMMON":
------------------------ added by HWF dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("RWR") ------------------------ end of added by HWF So now the file looks like this:
dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON ------------------------ added by HWF dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("RWR") ------------------------ end of added by HWF shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.8 shaderLineDefaultFuzziness = 0.4 shaderLineDrawAsWire = false shaderLineUseSpecularPass = true This makes the RWR available for export.
Edit: Remember that ED will replace this file with the original when you update or repair, so be sure you keep a backup for the modified file. Plus a backup of the original file of course.
Next, you have to create your monitor config file, and the detail depends on what you want to see on your screens. I used the attached file "Camera+LMFCD+RWR.lua" under "C:\Users\USER_NAME\Saved Games\DCS.openbeta\Config\MonitorSetup" to test the export.
I realize this is a bit of a stretch for a 4-year old 😃, so just take it step by step and let me know if you get stuck somewhere!
DCS MultiMonitor Setup.pdf Camera+LMFCD+RWR.lua

I have experienced the "problem" after manoeuvering wildly between the mountains to escape an AA missile. Betty bitched a lot and the flight back to base was difficult because the aircraft kept rolling left and right, no way to stabilize the roll axis. I was flying with G-effects disabled; otherwise I'm sure I would have suffered blackout or red-out. Seems realistic that the aircraft suffered some damage. A pity that the damage is not indicated in the de-briefing!

I struggle to understand the issue.
1. With ground power ON, you set the throttle to OFF using the command "Throttle  - Stop Engine" (or [End] key).
2. Flip the battery switch down to "Starter" briefly and then all the way up,
3. At  3% RPM, move the throttle forward to the detent, using the command "Throttle - Start Engine" (or [Home] key).
4. At 6% RPM, move the throttle forward to IDLE, using the command "Throttle - Start Engine" (or [Home] key) again.
The engine will spin up to Idle rev rate.
You should be able to bind the commands "Throttle  - Stop Engine" and "Throttle - Start Engine" to the your Cutoff resp. Idle buttons.
Yes, you will use the same "Idle" button twice as you move the throttle forward in two steps. Is that an issue?
Am I missing something?

@maikchaos: Here are the LUA lines for the added commands.
{down = 3006, cockpit_device_id = devices.ELEC_INTERFACE, value_down = 1.0, name = _('Battery Power Switch ON'), category = _('Electrical Control Panel')}, {down = 3006, cockpit_device_id = devices.ELEC_INTERFACE, value_down = 0.0, name = _('Battery Power Switch OFF'), category = _('Electrical Control Panel')}, {down = 3001, cockpit_device_id = devices.ELEC_INTERFACE , value_down = 1.0, name = _('APU Gen Power ON'), category = _('Electrical power control panel')}, {down = 3001, cockpit_device_id = devices.ELEC_INTERFACE , value_down = 1.0, name = _('APU Gen Power ON'), category = _('Electrical power control panel')}, {down = 3004, cockpit_device_id = devices.AHCP, value_down = 1.0, name = _('TGP switch ON'), category = _('Armament HUD Control Panel')}, {down = 3004, cockpit_device_id = devices.AHCP, value_down = 0.0, name = _('TGP switch OFF'), category = _('Armament HUD Control Panel')}, {down = 3006, up = 3007,cockpit_device_id = devices.CPT_MECH, value_down = 0.0, value_up = 0.0, name = _('Canopy CLOSE/HOLD'), category = _('Systems')}, {down = 3007, cockpit_device_id = devices.CPT_MECH, value_down = 1.0, name = _('Canopy OPEN'), category = _('Systems')}, I had no time to test them, let me know if something doesn't work!
Note: The battery power command looks different from what @Insonia posted, but it's the same. When I wrote the document he refers to you had to use the numerical DeviceID which you had to look up in "devices.lua". But meanwhile ED has made it smarter and you can use the mnemonic DeviceID which makes the lines more readable.
Note: The Canopy Close command works like in the cockpit: The closing movement stops when you release the button. If you don't like that, you need to remove the "up" and the "value_up" parts.

I guess everybody would have this issue if they wanted to use VOIP on the original A-10C.
The file "Throttle - HOTAS Warthog.lua" in the folder "...\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C_2\Input\A-10C_2\joystick" contains some lines that are missing in the file for the A-10C:
-- start VoIP radio global commands -- in case you need to open commands in the cockpit {down = iCommandVoIPRadioPushToTalkEnableDisableVoice, up = iCommandVoIPRadioPushToTalkEnableDisableVoice, value_down = 1.0, value_up = 0.0, name = ('HOTAS MIC Switch Down (VOIP)'), category = _('HOTAS')}, {down = iCommandVoIPRadioPushToTalkEnableDisableVoice_2, up = iCommandVoIPRadioPushToTalkEnableDisableVoice_2, value_down = 1.0, value_up = 0.0, name = ('HOTAS MIC Switch Aft (VOIP)'), category = _('HOTAS')}, {down = iCommandVoIPRadioPushToTalkEnableDisableVoice_1, up = iCommandVoIPRadioPushToTalkEnableDisableVoice_1, value_down = 1.0, value_up = 0.0, name = ('HOTAS MIC Switch Forward (VOIP)'), category = _('HOTAS')}, -- end VoIP radio commands The file "default.lua" for the A-10C does contain these lines and that's why you can bind them to any game controller that doesn't have a dedicated .lua file.
You can wait for ED to fix this omission, or you can help yourself by copy & pasting these lines into the file for the A-10C. If you want to do that:
1. use the free Notepad++ editor and set "Language" to "Lua".
2. insert the lines just after the line that reads
keyCommands = { 3. Note that the file will be overwritten by the stock file if you do a Repair or Update. Therefore, make a backup copy of the changed file.
 

In fact, the "F10 View Options" under Gameplay was set to All.
But there is a related option "F10 AWACS View" in the MISC tab which I had forgotten because I set it to TRUE a long time ago. And this is one of the many options the last update had changed. I have now set it TRUE and the F10 view now works.
These two options should be side by side on the same tab.
And Updates should not make a mess of our option settings.
I do not expect ED to follow my advice, and I will need to work out a solution that captures my Options settings and allows me to restore everything ED's faulty process has messed up.

Why is that function not appropriate? It's exactly the way it should be.
You could add the commands for ARM and OFF to the file "Throttle - HOTAS Warthog.lua" and use Button 24 and Button 24 OFF. It would then do exactly the same thing as the existing command "EAC 2-pos Switch : ARM<>OFF". Seems pointless.

There is a way. I understand you want to use a rotary encoder on your keyboard. Therefore you need to modify the file "default.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard". It has 2 relevant lines of code:
{pressed = ufc_commands.SYM_Knob_ITER, cockpit_device_id = devices.UFC, value_pressed = 0.3, name = _('ICP HUD Symbology Intensity Knob - Up/Increase'), category = {_('Instrument Panel'), _('ICP')}}, {pressed = ufc_commands.SYM_Knob_ITER, cockpit_device_id = devices.UFC, value_pressed = -0.3, name = _('ICP HUD Symbology Intensity Knob - Down/Decrease'), category = {_('Instrument Panel'), _('ICP')}}, The value of the parameter "value_pressed" determines how fast the knob in the cockpit rotates. I recommend you leave the original lines alone and add the two lines below for a "fast" version of the command:
{pressed = ufc_commands.SYM_Knob_ITER, cockpit_device_id = devices.UFC, value_pressed = 1.0, name = _('ICP HUD Symbology Intensity Knob - Up/Increase Fast'), category = {_('Instrument Panel'), _('ICP')}}, {pressed = ufc_commands.SYM_Knob_ITER, cockpit_device_id = devices.UFC, value_pressed = -1.0, name = _('ICP HUD Symbology Intensity Knob - Down/Decrease Fast'), category = {_('Instrument Panel'), _('ICP')}}, Alternatively, you could change the values of the original lines. If you do that you must still change the name so it's different from that of the original command. This is because the command also exists in the "default.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick". So, if you change just the values and not the names, the Options/Controls screen would show you duplicate lines in orange font, because you have different commands with the same name. And you would not know which lines to bind.
And don't forget: Any update or repair will restore the original file. So you need to back up your modified file.
 

It's funny; I had added a bunch of axis comands before ED had added them. Fortunately, I didn't delete my additions. Here they are:
{action = 3001, cockpit_device_id = 49, name = _('Engine Instruments Lights Axis')}, {action = 3002, cockpit_device_id = 49, name = _('Flight Instruments Lights Axis')}, {action = 3003, cockpit_device_id = 49, name = _('Auxiliary Instruments Lights Axis')}, {action = 3005, cockpit_device_id = 49, name = _('Flood Light Axis')}, {action = 3006, cockpit_device_id = 49, name = _('Console Light Axis')}, {action = 3011, cockpit_device_id = 54, name = _('UHF Radio Volume Axis')}, {action = 3005, cockpit_device_id = 55, name = _('VHF AM Radio Volume Axis')}, {action = 3005, cockpit_device_id = 56, name = _('VHF FM Radio Volume Axis')}, {action = 3013, cockpit_device_id = 38, name = _('Yaw Trim Knob Axis')}, I think these will still work.
You probably know: the "action" number is = Button_No + 3000.
The device ID for "LIGHT_SYSTEM" = 49 is good for most of your items. You find other device ID numbers in "devices.lua".

If you use a US-ASCII keyboard iIt's LAlt + '  (left Alt plus apostrophy).
On my German keyboard it's LAlt + Ä

This keybind exists already for the TM Warhog throttle. I suspect you want it for use with a different kind of game controller.
ED have disabled the related line of LUA code in the file "default.lua" by adding "--" at the beginning of the line.
You could easily enable the line by removing the "--" using Notepad++
It's line 261 in my rig and it currently looks like this:
--{down = iCommandPlane_HOTAS_MIC_SwitchUp, up = iCommandPlane_HOTAS_MIC_SwitchOff, name = _('HOTAS MIC Switch Up (no function)'), category = _('HOTAS')}, Notepad++ shows the entire line in green because the "--" comments it out.

1. I'm referring to the file "default.lua" under "K:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick" (K being the Drive).
2. The best place for adding key commands is just below these lines at the top of the file so you can easily find your edits.
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,{ 3. Make sure you don't miss any of the commas, parentheses, curly braces. Syntax errors may invalidate the entire file
4. Use a program editor like Notepad++ (no office program!)
 

These command bindings are already available. Look for "Mode Knob - CCW" and "Mode Knob - CW"!

In the air-start missions the jug is clearly not trimmed for the flight conditions at mission start. All 3 trim axes are in their neutral positions. This costs precious time especially in the instant action missions where you need to be instantly ready to fight.
I have created for myself a custom binding for a rapid "Trim Preset". which requires addition of one line in "default.lua" under "...\DCS World OpenBeta\Mods\aircraft\P-47D-30\Input\P-47D-30\joystick".
{down = device_commands.Button_6, pressed = device_commands.Button_9, up = device_commands.Button_3, cockpit_device_id = devices.CONTROLS, value_down = -0.25, value_pressed = 0.35, value_up = -0.1, name = _('Trim Preset Elevator_Rudder_Aileron'), category = {_('Flight Control')}}, This line sets
Elevator Trim = -0.25 (25% tail-heavy)
Rudder Trim = 0.35 (35% Right)
Aileron Trim = 0.1    (10% Right)
The added line creates a new command "Trim Preset Elevator_Rudder_Aileron" which I've bound to a button on my VRP stick.

I created this one a long time ago. Hopefully it will still work:
{down = iCommandPlaneGearUp, up = iCommandPlaneGearDown, name = _('Landing Gear 2-Position UP/DOWN'), category = {_('Gear Systems'), _('Instrument Panel')}}, Edit: just tried. Still working.

And "Game Avionics Mode"? If that option is checked the keyboard commands for Radar commands don't work. I tried.

You can wait for ED, or add the command(s) yourself to the file "default.lua" in the folder "...\Mods\aircraft\A-10C_2\Input\A-10C_2\keyboard".
As a minimum, you need this line to switch the HMCS power ON:
{down = 3001, cockpit_device_id = 75, value_down = 1.0, name = _('HMCS Power ON'), category = _('HMCS Power')}, For the OFF command you need to add this line:
{down = 3001, cockpit_device_id = 75, value_down = 0.0, name = _('HMCS Power OFF'), category = _('HMCS Power')}, For a tutorial about editing these files go here: https://forums.eagle.ru/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/?tab=comments#elControls_4646929_menu