LeCuvier

I tested the solution presented by @scoobie and it works fine here. And there is no reason why it shouldn't work for someone else. I don't want to be patronizing but I suspect you did something wrong. I just inserted the 2 lines modified for "slow" after the original lines, but that difference shouldn't matter. It should be easy to find out what was wrong if you could provide a copy of your modified "default.lua" file.

I shot the Mossie's left wing off, but the left propeller stayed magically in place. Looks spectacular! Screenshot attached.

You should probably ask ED support for advice.

Yes of course, if you want to use the commands from the keyboard the 2 lines must be added to the "default.lua" under "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard"

These 2 lines work with a maintained 3-position switch ON1-OFF-ON2 (like the FLAPS switch on the Warthog throttle): {down = alt_commands.ELEC, up = alt_commands.ELEC, value_down = -1.0, value_up = 0.0, cockpit_device_id = devices.AAU34, name = _('Altimeter Mode Switch ELEC/OFF'), category = {_('Instrument Panel')}}, {down = alt_commands.PNEU, up = alt_commands.PNEU, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.AAU34, name = _('Altimeter Mode Switch PNEU/OFF'), category = {_('Instrument Panel')}}, If you are not familiar with editing the "default.lua" I recommend you look into the tutorial under this post: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu

There is a problem in your hardpoint switch line. I have not yet found what it is, but when I include your line in my "default.lua" then the commands under "Sensor power control panel" can no longer be bound to anything except the keyboard. Searching... Edit: Got it. You omitted the comma after the "value_up = 0.0". That invalidates your line, and in this case everything with that device ID. I entered this corrected line and it shows up under Options/Controls now. {down = sms_commands.LeftHDPT, up = sms_commands.LeftHDPT, cockpit_device_id = devices.SMS, value_down = 1.0, value_up = 0.0, name = _('LEFT HDPT Switch - ON/OFF NEW'), category = {_('Right Console'), _('SNSR PWR Control Panel')}}, You have to be paranoid with the formatting of your added lines. A missing or extra comma can invalidate your "default.lua" altogether. Re your second issue, not sure I understand. If you want to use the command with the keyboard you must include it in the "default.lua" under "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard".

As you see from the numbers, I have made them 10 times faster. If you find that too fast you can reduce the values, e.g. to 0.05.

I'm German, but I do not use the German version. Why? Because I have rarely seen a translation without errors. Regarding the EHSI commands for Heading and Course, you can make them faster. Heading commands are defined by these 2 lines: { pressed = ehsi_commands.LeftKnob, cockpit_device_id = devices.EHSI, value_pressed = -0.01, name = _('HDG Set Knob - CCW/Decrease'), category = {_('Instrument Panel')}}, { pressed = ehsi_commands.LeftKnob, cockpit_device_id = devices.EHSI, value_pressed = 0.01, name = _('HDG Set Knob - CW/Increase'), category = {_('Instrument Panel')}}, The number following "value_pressed" defines how fast the heading pointer rotates. You could just overwrite the 0.01 with a higher number, but I prefer to create a new "Fast" version of the command. I have added these two lines of code: {pressed = ehsi_commands.LeftKnob, cockpit_device_id = devices.EHSI, value_pressed = -0.1, name = _('HDG Set Knob - CCW/Decrease Fast'), category = {_('Instrument Panel')}}, {pressed = ehsi_commands.LeftKnob, cockpit_device_id = devices.EHSI, value_pressed = 0.1, name = _('HDG Set Knob - CW/Increase Fast'), category = {_('Instrument Panel')}}, These work well for me. I'm fairly sure you could do the same with the Course commands. Note: 1. The added commands' names must be different from those of the original commands. 2. The original commands contain a lot of spaces or tabs. They have no function. I always take them out when I make a new command. 3. If you want to know what you are doing, I recommend you download my tutorial from this post: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu

I felt challenged to produce commands that combine pull and Turn into single key binds, and it turned out to be easy. These 2 lines of code do it: {down = clock_commands.CLOCK_left_lev_up, pressed = clock_commands.CLOCK_left_lev_rotate, up = clock_commands.CLOCK_left_lev_up, cockpit_device_id = devices.CLOCK, value_down = 1.0, value_pressed = -0.01, value_up = 0.0, name = _('Clock Winding and Setting Knob - PULL & CCW'), category = {_('Right Auxiliary Console')}}, {down = clock_commands.CLOCK_left_lev_up, pressed = clock_commands.CLOCK_left_lev_rotate, up = clock_commands.CLOCK_left_lev_up, cockpit_device_id = devices.CLOCK, value_down = 1.0, value_pressed = 0.01, value_up = 0.0, name = _('Clock Winding and Setting Knob - PULL & CW'), category = {_('Right Auxiliary Console')}}, This creates 2 new key binds. The first one will pull the button and rotate it counter-clockwise as long as you keep pushing the bound key or button. The second one does the same but rotates the button clockwise. You mention using a rotary encoder. I tried this and in works, but extremely slowly. Not acceptable for me. But if your rotary encoder produces longer pulses that might be fine. Note: If you want to use the keyboard for these commands, you must edit the "default.lua" under "...\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard". If you don't want to edit your lua file, no problem for me. I enjoyed trying this.

Regarding your second item, there are key binds for Pull, CW and CCW. What are you missing? Edit: Having tried this, I concede that it's awkward to push and hold one button and at the same time keep pushing another button, especially if you are out of buttons and have to use a modifier which means, push a key on your keyboard plus push two buttons on your button box or whatever simultaneously. But it's no problem if you have a spare Maintained ON/OFF switch. Set it to ON and then turn the knob. Set it back to OFF when you are done turning.

I have a solution for the Ejection Seat: I added these 2 lines to the file "default.lua" under "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick": {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')}}, These lines provide separate key binds for ARM and LOCK. If you want to use a single maintained ON/OFF switch instead, use this line: {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')}}, I have not looked at the clock pull/turn thing yet. If you are willing to make additions to the "default.lua" I might try.

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.

If you're about to be shot down by your pursuer that danger is very relative. Plus, in a real plane you get feedback from your body that helps to manage the roll. In the sim we don't have that body feedback. Plus a pursuing AI pilot has magic abilities for staying just behind you and killing you. So I'm afraid this tactic won't work for us.

Erich Brunotte is talking about a (probably undocumented) life-saving feature of the Dora. When he was pursued in a turning fight, and the opponent was dangerously close to a firing solution, he would brutally pull the stick back. If this happened in a left turn, the Dora would suddenly roll right, and in a right turn the Dora would suddenly roll left. This caused the opponent to overshoot, and he could get himself into a position to shoot. I have tried to reproduce this, but it works only in a right turn. Is that a bug? (just kidding of course)

@Blackhawk NC: When I started flying the Dora I could have posted something like your story. Today, I find the Dora a great fighter. I can defeat all allied WWII fighters except the Spit. The difference between then and now is simply learning through practice. Your problem is almost certainly that you pull too hard in the turn and then your left (I believe) wing drops. But the Dora warns you before that happens. I'm by no means a great fighter pilot, but I defeat the Mustang AI regularly, even when the AI has skill level "Ace". The attached track is just an example. I have a track of an easier victory. In that case the Mustang's mission task was "CAS". It seems that that makes it more docile. Note: I'm 77 and my eyesight has suffered. I must therefore use labels. The Dora is a beast that wants to be tamed. Are you up to the challenge? Dora kill Mustang AI Ace 1.trk

The second part of the video is so blurry I don't know what I see. What I think you are trying to tell us is: You can bind the button to "AAP Steer point FLT PLAN", but the button has no effect in game. I have seen this kind of issue reported (rarely) on various modules but I have not experienced it myself. I suspect it's a problem in the "....diff.lua file" under "Saved Games" What I would try: Re-name the folder "C:\Users\XYZ\Saved Games\DCS.openbeta\Config\Input\A-10C II\joystick". When you re-start the game DCS will create a new blank version of the folder and its files. Re-create the bindings for your button box or whatever it is and test. If that's successful you can copy the other "...diff.lua" from the re-named folder back into the new folder.

I cannot reproduce your problem. I bound that switch position to a button on my VRP MongoosT-50 stick (which I don't normally use for the hog) and when I press that button the switch goes to the "PLAN" position. Maybe that button on your joystick is defective?

Removing and re-installing the BS module is probably not helpful. Have you tried this?: Under "C:\Users\YourName\Saved Games\DCS.openbeta\Config\Input\" delete the folder "ka-50". Or just re-name it so the software will ignore it. Then re-start the game. You should now be able to re-enter your bindings (and delete the unwanted default bindings).

Just a remark: there is no need to delete the original "...press 3 times" command. As long as the new command has a different name, original and added commands coexist without a problem.

My answer is a bit late as I had not seen this post (should have been under "Controller Questions and Bugs). I don't fly the F-5 much, but I gave it a try adding these 2 lines to the file "Throttle - HOTAS Warthog.lua" {down = asg31_commands.DgMode, up = asg31_commands.ResumeSearch, cockpit_device_id = devices.AN_ASG31, value_down = -1, value_up = 1, name = _('Dogfight/Resume Search Switch - FORWARD (DM)/CENTER (RESUME'), category = {_('Stick')}}, {down = asg31_commands.DgMode, up = asg31_commands.ResumeSearch, cockpit_device_id = devices.AN_ASG31, value_down = 1, value_up = 1, name = _('Dogfight/Resume Search Switch - AFT (DG)/CENTER (RESUME'), category = {_('Stick')}}, I bound the two new commands to the positions "PATH" and "ALT" of the Autopilot switch on the TM Warthog throttle, and it seems to work. But I'm not an F-5 expert, so why don't you give it a try? Edit: I've re-bound the new commands to the Boat Switch. That seems more handy.

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.

I have not bought the Mi-24 but I did a trial, and I still have some of the files. It seems that the 3rd line represents a true 2-position switch and that's why this line works. The 1st 2 lines represent pushbuttons which have a different structure in "clickabledata.lua". Even if I had the module I could probably not make these 2 lines work.

I have experienced a lot of game start issues since a few updates. Very often the game will show the progress messages of a normal load, but at the end the game window will not display. Clicking on the game icon in the taskbar won't help. But when I click on the MS-Outlook or any other Office icon in the taskbar the game window comes up and I can play. Sounds ridiculous I know. Biut it has become a bit of a routine and doesn't bother me any more.

The "default.lua" is not under "Saved Games". It's under "...Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick". If you want to master this coding I recommend you study the tutorial under this post: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu

I recommend you use Notepad++ This post contains a tutorial, and sample code for several aircraft modules: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu