LeCuvier

The Mosquito in my experience does a lot of wiggling too, but is manageable. I find the Jug easiest to kill.

The problem seems to originate in the German versions of the "default.lua" files under "DRIVE:\Eagle Dynamics\DCS World\Mods\aircraft\F-16C\Input\F-16C\joystick" and "DRIVE:\Eagle Dynamics\DCS World\Mods\aircraft\F-16C\Input\F-16C\keyboard" respectively. It seems that the line with the name "ANTI-SKID Schalter - "Parkbremse" has different definitions between the two files. This ought to be corrected by the person who is responsible for the localization. It's a relatively simple task. I do not have the German files so I cannot look into them. I use the English version of the game (although I'm German), and the bindings for this switch work ok here.

The above is the beginning of the description of the Intercom Panel. My assessment is that the ARC-210, like the AN/ARC-164, does not have a volume control. The AN/ARC-186 does have a Volume control, but the manual describes it as "initial volume". I guess that's the volume at pre-amplifier stage output. The Volume control of the Intercom Panel is the one you will use for all radios (and everything that beeps). Edit: I wanted to bind the Volume knob on the Intercom Panel to a rotary encoder. So I selected the category "Intercom Control panel and happily found the bindings "INT volume decrease" and "INT volume increase". But when I went to the cockpit and used the rotary encoder, it rotated the button labelled "INT". I didn't try if the rotation has any effect. So I went back to Controls/Options and found the bindings "Volume volume decrease" and "Volume volume increase". These actually rotate the "Volume" knob on the panel. The naming of this control binding is (IMO) ridiculous. It should be named "Master Volume Control". The knobs "FM", "VHF" and "UHF" also have bindings for "volume increase" and "volume decrease", but the manual states "Rotary Selector position will not matter". So why do we have those bindings? Seems to be that a bit of clean-up would be appropriate.

Nice mod, but it doesn't help much with the AI P-51 now flying even wilder stunts. I doubt that an AIM-9 could hit them as they fly now.

HMD OFF/BRT Knob - CCW/Decrease and HMD OFF/BRT Knob - CW/Increase

It gives me the creeps when I remember the nights when, as a kid, I heard them flying low over our place (I lived a bit east of the Nörvenich air base) in landing approach for hours, during exercises. I'll never forget the mournfull low-pitched howling of their engines. Near the Nörvenich air base there was the ruin of a sugar factory where one of them had punched a big gaping hole through the last wall standing. What a widow maker that F-104G was! Once a whole flight of them dived straight into the lignite strip mine nearby. We had a saying like "how do you get a Starfighter? Buy a little piece of land and wait!". Yet it seems the pilots loved them, so maybe I'll buy it...

Yes.

What exactly are you looking for? There are about 10 .lua files under "DRIVE:\Eagle Dynamics\DCS World\Mods\aircraft\F-15E\Cockpit\Radar"

Actually I found a solution in the collection created by @Munkwolf at his GitHub site:https://github.com/Munkwolf/dcs-community-keybinds You could add these lines directly into the "default.lua" under "DRIVE:\Eagle Dynamics\DCS World\Mods\aircraft\FA-18C\Input\FA-18C\joystick" -- Standby Pressure Altimeter AAU-52/A {cockpit_device_id = devices.AAU52, pressed = aau52_commands.AAU52_ClkCmd_ZeroSetting, value_pressed = -0.01, name = _('AAU-52 Altimeter Pressure Setting Knob - CCW/Decrease (Slow)'), category = {_('Instrument Panel'), _('Custom')}}, {cockpit_device_id = devices.AAU52, pressed = aau52_commands.AAU52_ClkCmd_ZeroSetting, value_pressed = 0.01, name = _('AAU-52 Altimeter Pressure Setting Knob - CW/Increase (Slow)'), category = {_('Instrument Panel'), _('Custom')}}, But that file will be restored to its original content by any update or repair. Using the Command Injector created by @Quaggles you would have these lines in a "default.lua" under "Saved Games" and that will survive updates and repaires. See here: https://forum.dcs.world/topic/270487-quaggles-dcs-input-command-injector-mod-v109-store-custom-input-commands-safely-in-saved-games-instead-of-merging-them-with-developer-changes-each-update/#comment-4651461 PS: I found these a bit slow, therefore changed the "value_pressed" parameters to -0.2/0.2

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.