LeCuvier

He changes the "Name" field in the .LUA line by adding "Pilot" as a prefix.

Interesting, I learned something!

Oops, I'm not familiar with the Apache although I have the module, and I wrongly assumed that the aft cockpit is for the CPG. The command for the CPG is defined in this line in the "default.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Input\AH-64D_CPG\joystick": {down = tedac_commands.RHG_SIGHT_SLAVE_BTN, up = tedac_commands.RHG_SIGHT_SLAVE_BTN, cockpit_device_id = devices.TEDAC_INPUT, value_down = 1.0, value_up = 0.0, name = _('RHG Sight Slave Button'), category = {_('TEDAC'), _('Right Handgrip')}}, You can add this line into the "default.lua" under "C:\Users\USER\Saved Games\DCS.openbeta\InputCommands\AH-64D\Input\AH-64D_PLT\joystick". But I'm not sure that the software will let the pilot use this command. Also, I wouldn't know how to test it as the pilot doesn't see this button.

The command "RHG Sight Slave Button" is already available for the CPG. What are you trying to add?

I like this cockpit mod and will use it going forward. But I also like the REVI mod I've been using for 4 years now. I think Pato created it. Unfortunately he is no longer available and I just hope his REVI16 will not be killed by an update any time soon. It might not be realistic, but what the hell, I want to enjoy this game.

Radio 1 also has at least one issue: For communication within the flight I use the default 243,000 MHz/Chnl 1. When I activate the channel selection field by hitting the [GREC C/M], I cannot communicate with my wingmen. I can hear them when they call out a bandit for example, but they do not hear my commands. When I switch to the frequeny field. communication works both ways. It seems to me that the radios require a lot of rework.

Thanks! I was desperately trying to figure out why I could not communicate with the ATC on radio 2 while communication with AWACS was ok.

This process doesn't sound familiar at all, I don't know of a 2-step authentication in DCS World. I'm wondering, are you logging in via Steam? In that case you should log your issue in a Steam forum or support site.

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!

Even if you bind it to the Bodnar board or any other game controller, you still have to hit the button thrice. I have added the following line to the "default.lua" for ^"UiLayer" under Saved Games. So I only need to hit the button once, and the hack is available for all aircraft modules. {down = iCommandPlaneEject, pressed = iCommandPlaneEject, up = iCommandPlaneEject, name = _('Eject (press once)'), category = _('Systems')}, Regarding DCS-Bios, I hope someone else can help you. My knowledge is = 0.

In my experience, user-edited "default.lua" cause no problem with MP integrity check. Note: Nowadys I have all my edits in separate "default.lua" under "Saved Games", using the solution developed by @Quaggles. You can find this here: https://forum.dcs.world/topic/270487-quaggles-dcs-input-command-injector-mod-v1010-store-custom-input-commands-safely-in-saved-games-instead-of-merging-them-with-developer-changes-each-update/#elControls_4651461_menu This solution uses a modified "Data.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Scripts\Input". I have tried this in MP and it passes integrity check, even if the server specifies "pure script".

The two VOIP commands are not greyed out for any of my game controllers. And I cannot imagine what would cause them to be greyed out for you.

I have the TM Warthog throttle (not the latest version) and the TDC Slew control is not very good. My settings are: Deadzone = 20 Saturation X = 100 Saturation Y = 20 Curvature = 20

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?

I guess my question could be misunderstood. I mean the functionality of @Quaggles Command Injector. This allows users to add command bindings in a "default.lua" under \Saved Games. These don't get lost in the process of updating. Quaggles has achieved that by editing the file "Data.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Scripts\Input". The obvious issue is that this customization can be (and has been) broken when the stock file "Data.lua" is modified in an update. So far Quaggles is maintaining the customization but he won't be doing that forever. The functionality makes sense to a lot of people, and I believe it would make sense for ED to integrate it in the product.

Yes I have a TM Warthog, but I've uninstalled TARGET years ago. I would rather use Voice Attack.

I continue to use my LUA edit (posted a year ago in this thread), a simple line of LUA code. And I have bound the command to the Right Windows button. I have never ejected by mistake. And I'm now using it with the "Command Injector" developed by Quaggles. That works very well. It was broken by the udate to 2.9, but Quaggles fixed that in a couple of days. Only worry is, when one day Quaggles will no longer support this, the solution is dead. I have looked at the file and I cannot figure out how it works. @BIGNEWY: is there any chance that ED would integrate that functionality? I think the potential benefits are obvious!

A macro in ED?

Real pilots don't look at a PC monitor. This issue is about rendering objects in a way that simmers have a chance to see them. This community has a wide variety of hardware, and "real pilots" cannot tell the developers how to achieve results satisfactory for all or at least the vast majority of users. In my opininion, users need the ability to set this up the way that suits their need. There are some new options that seem related, but I have no idea what they do. And the user manual was last updated about a year ago...

I don't have any Winwing controls, so cannot speak from experience. Unlike the F/A-18C, the hog doesn't have any special settings related to the afterburner detent. One guess I could make is that in your axis tuning settings you have Saturation Y set to less than 100%, but that seems unlikely. My best guess is that you are looking at the engine power (Fan) gauges, and these never go beyond about 82%. That's because the engines of the A-10C are limited to about 82%. That's not a bug, it's like the real hog. It's meant to loiter for a long time; not to engage with fighters. When you go to Options/Controls, Axis page, right-click on a throttle axis binding and select "Tune". When you move the throttle through its range, do you see it going through its full range? And when you look at the throttle levers in the cockpit, do they move all the way to Max?

No. If you don't want to hold the button down till it's closed, use this line: {down = 3006, cockpit_device_id = devices.CPT_MECH, value_down = 0.0, name = _('Canopy CLOSE without Hold'), category = _('Systems')}, That's not "realistic" though.

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

That's probably because this command is also defined in the file "Throttle - HOTAS Warthog.lua". If my guess is right you will not be able to bind this command on any device except the TM Warthog throttle. That file is structurally the same as "default.lua", but its bindings can only be bound to switches/axes on that device.

For the APU it's all there. For the 3 others I can provide additions for the "default.lua" file. Do you want to use a pair of pushbuttons for each of these, or one maintained ON/OFF switch each? Edit: if you want to discuss this privately auf deutsch PM me!

This works: {down = 3009, up = 3009, cockpit_device_id = devices.AHCP , value_down = 1.0, value_up = 0.0, name = _('JTRS switch 2-Pos ON/OFF'), category = _('Armament HUD Control Panel')}, It works also if you use "...value_up = -1.0...". Your tentative line uses the same name as ED's original command. That would never work. The names must be unique.