LeCuvier

I agree. And I did not find a satisfactory mod. The only way it works well is with the mouse in the cockpit.

Cannot confirm. I can set the switch to all 3 positions. Right mouse button moves the switch up from OFF to Anti-Skid, then to Parking Brake. Left mouse button makes it switch down from Parking Brake to Anti-Skid, then to OFF.

I do not have all of the bindings in your list, but the ones we have in common are still working. I have reviewed all bindings for the F-15E and I haven't lost any. Note: the AN/APG-70 Radar: OFF/STBY/ON/EMERG has never worked for me, just like the other rotary switches on the "Sensor" panel. As a work-around I have bound the positions "STBY" and "ON" to a 2-position switch and that works fine. Have the CW/CCW commands ever worked for you?

Even if I used Visual Studio to implement the parsing and visualization of logbook data, I would use a database structure with tables and relationships to store the structured data. Now MS Access includes VBA (Visual Basic for Applications) and that is practically the same as the VB I would use within Visual Studio. Plus, MS Access provides an object set of forms and data handling objects that make it very easy to create a data-based application.

logbook.lua is hard to read though. Took me a while to import it into a database (MS Access), parse the data structure and present campaign data in an understandable format.

Yes, that was a potential benefit. In practice though I flew in Open Beta only because I always had at least one bird in early access and wanted to see the progress. I have never seen bugs so distastrous that I would have gone back to "Stable". I actually stopped maintaining mods in stable. But now, as NineLine stated Thursday, "this is the unified version, no matter what version you are on now it will update to the same version. " Thus, no point keeping a second version.

Correct statement. I would therefore vote against adding "Prop Governor to Automatic" to the auto-start macro. The beginner will tend to forget activating the engine governor after takeoff, and that will kill the engine rather quickly. After one or two killed engines you will remember. Note: It's also recommended to set the engine governor to "manual" and propeller pitch control to 12:00 when you prepare for landing.

Since both are the same now, I find it useless to update and maintain both. I used to fly in Open Beta only. So the "Saved Games" data for Open Beta were most relevant. Going forward, there will be no Open Beta I presume. I do not want to wait for some miraculos logic from ED to clean up for the different user situations. Therefore after the updating, I ... 1. Renamed the folder "DCS" under "Saved Games" to "DCS Old Stable". Will be deleted after a short grace period. 2. Renamed the folder "DCS Open Beta" under "Saved Games" to "DCS"- 3. Deleted the folder "K:\Eagle Dynamics\DCS World Open Beta" ("K:" is my games drive). This freed up about 400 GB on my Games drives 4. Deleted the desktop shortcuts to Open Beta and Open Beta MT. When I start the game from the shortcut "DCS World" it starts the MT version.

If I get this right then there is no need to maintain two versions (Open Beta and Stable) going forward. So far I have kept both updated. Is there any reason why I should not delete the Open Beta version? That move would free up about 400 GB on my "Games" disk. Please confirm!

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.

Don't you have a backup of the folders under "C:\Users\USERNAME\Saved Games\DCS.openbeta\Config\InputSaved Games"? You should be able to restore the files for aircraft other than F/A-18 from there.

Didn't you make a backup of the folders under "C:\Users\USERNAME\Saved Games\DCS.openbeta\Config\Input" from the old computer? If you did, just restore your "Saved Games" backup and all the bindings should be there, plus your presonal missions if you backed up "C:\Users\USERNAME\Saved Games\DCS.openbeta\Missions" as well. If you don't have the backup, there might be a solution I've never tried: Under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick" there are files that have the format of binding files and I suspect these are default bindings. For the TM Warthog HOTAS it's the "Joystick - HOTAS Warthog.diff.lua" and the "Throttle - HOTAS Warthog.diff.lua". Copy these files to "C:\Users\USERNAME\Saved Games\DCS.openbeta\Config\Input\F-16C_50\joystick". If my theory is correct, you should now see the default bindings on the screen Options/Controls. As I said, I've never tried this but I cannot think of any other purpose for having these .diff.lua files under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick".

I don't know of a connected devices limit. Normal logic would say that if there was such an issue you would see instability on a cockpit device that's bound to one of the game controllers. You can easily exclude this possibility by disconnecting some of your game controllers.

I agree. By the way, you might even have a Mouse button bound to it. Steps: 1. document all existing bindings you want to use 2. re-name the folder "C:\Users\USER\Saved Games\DCS.openbeta\Config\Input\FA-18C_hornet" or "C:\Users\USER\Saved Games\DCS\Config\Input\FA-18C_hornet" This voids all existing bindings for the Hornet so you are sure there is no garbage hidden somwhere. 3. start the game and re-enter your bindings

This combination of commands is not not included in the stock file, but it can be created with a little LUA edit in the file "defaut.lua". I just tried, and it works for me. However, that file is restored to its original content when you do an update or repair, so you need to back up your modified file. I do not have this problem because I use the "command injector" created by @Quaggles.

I have Voice Attack installed and use it with WWII wingmen, and I would use it if I did air refueling. I see no way to achieve what you want without using 3rd party software. There is no way to get there with LUA editing.

I looked at that site, and I saw no specifics. So it's not clear to me whether the controls labelled "Key..." are analog devices or rotary encoders. A rotary encoder is like a pair of pushbuttons that produce a short pulse at every click.

That solution might be an improvement, but it does not address the fact that button pairs are often too "fast" or too "slow", plus there are individual users' preferences. The Tuning option I propose could satisfy a larger part of the user community (so I believe).

We have this kind of problem for many bindings of that kind; not just trimming, and for a significant number of aircraft. In many cases that can be fixed by changing the GAIN in "clickabledata.lua" or the VALUE_DOWN in "default.lua". But these changes are not a "one size fits all", because the best values are vastly different depending on whether you want to use a pair of pushbuttons or a rotary encoder. The best solution from a user point of view would be to provide a "Tune" option for all bindings of this kind in Options/Controls. I do realize that this might require a lot of rework in the software.

I looked at the Serpents Tail A-10CII and it seems that the wingman has no weapons in its loadout. Easy to fix of course, but should be included before disribution.

I added these lines to the "axisCommands" section of the "default.lua" to create axis bindings for the two knobs: -- HWF Addition {action = device_commands.Button_4, cockpit_device_id = devices.AAP, name = _('AAP Page Select Knob Axis')}, {action = device_commands.Button_1, cockpit_device_id = devices.AAP, name = _('AAP Use Steerpoint Knob Axis')}, -- End Addition

I have created and published a lot of new bindings and I know how to use info from "clickabledata.lua". But I have never seen anybody create CW/CCW commands from a multi-position switch. We cannot change the software logic by lua editing.

I get it; you are referring to the multi-position switches on the Auxiliary Avionics Panel. This is a multi-position switch that has no "hooks" for creating incremental commands. However, I was able to create axis commands for both. The Page Select axis for example will set the knob to distinct positions with values from 0.0 to 0.3 as shown below: Value Position 0.0 Other 0.1 Position 0.2 Steer 0.3 Waypt Maybe the WinWing MIP could be programmed to provide analog values per above?

They are available under category "UFC". There are bindings for all the rocker switches. e.g. "UFC STEER DOWN/UP" for steerpoints and "UFC DATA DOWN/UP" for pages.

Wow!