JoyPro2 Discord GitHub
Game reference

DCS World

Show:
TitleSupportEngine commandBind fileIn-game test
DCS Worldnativeengine dcsSaved Games\DCS\Config\Input\<aircraft>\joystick\<device>.diff.lua (Lua diff), keyboard and modifiers.lua; .jp sidecar56/56

The game page in plain words: DCS World. Full matrix: Game support. What an export does in this kind of game: Export flow, in the game.

From docs/games/dcs.md in the repository (generated, always the current text).

CLI: engine dcs scan | import | export, engine dcs refresh id | clean (DB and clean profiles), engine dcs verify-clean, engine dcs strip-defaults, engine dcs device-luas. Code: engine\EngineDcsImport.cs, engine\EngineDcsExport.cs, engine\EngineDcsRefresh.cs, engine\DcsDeviceNames.cs, engine\DcsCommandNames.cs, engine\EngineDcsRefresh.Verify.cs, engine\EngineDcsDefaultsStrip.cs.

#Files

  • Saved Games\DCS\Config\Input\<profile>\joystick\<device>.diff.lua: the user's changes against the defaults (keyDiffs/axisDiffs with added/removed, ffDiffs for force feedback). <profile> is the input profile name a module declares in its entry.lua (InputProfiles), evaluated with DCS's own Lua (see refresh). Keyboard files are in keyboard\Keyboard.diff.lua, modifiers in <profile>\modifiers.lua.
  • <device>.jp: JoyPro's copy of the written file, with relation names and groups (re-import metadata).
  • Files are written without a BOM: DCS's Lua 5.1 cannot load one.

#Device names

DCS names a joystick <DirectInput instance name> {<instance GUID>}, with the instance name exactly as DirectInput reports it, spaces included. Example: VKB reports " VKB-Sim Gunfighter Modern Combat Pro Twist ", so DCS reads " VKB-Sim Gunfighter Modern Combat Pro Twist {1A2B3C4D-0A3F-11f0-8011-444553540000}.diff.lua". The GUID is upper case except its third group.

JoyPro's device names trim the instance name (VKB-Sim Gunfighter Modern Combat Pro Twist {...}). DcsDeviceNames converts between both:

  • Export: the file is named after the connected device's raw DirectInput name; for a device that is not connected, after an existing file of that device in the folder; else the JoyPro name. Files an older JoyPro wrote under the trimmed name (DCS ignores them) are read when no DCS-named file exists yet and removed after the write (backed up).
  • Import: a file name is turned into the JoyPro name (spaces at the ends of the instance name trimmed).

The device type (DCS: Input.Utils.getDeviceTemplateName) is the name without {GUID}. It selects the device's default file (below).

#Command names

DCS shows every command with a name and a category (Options > Controls). Most modules write English text (name = _('Gear up')), some a localization key: _('Input.SpitfireLFMkIX.pitch_minus') (Spitfire, Bf-109, FW-190, I-16, Mosquito, P-47, Yak-52, CH-47F) or _('29Fulcrum:Inp:AB Lock Latch ...') / _('29Fulcrum:Cat:Right Wall') (MiG-29 Fulcrum). DCS loads the input files with _ = InputUtils.localizeInputString = i_18n.dtranslate('input', s) (Scripts/Input/Data.lua), and the English text is in <DCS>\l10n\en\LC_MESSAGES\input.mo ("Engine RPM DECREASE").

Root cause of raw titles (fixed 2026-10-24): the headless refresh runs DCS's luae.exe, which has no locale, so dtranslate returned the key and the DB stored it (3682 titles and 512 categories in 11 lists, e.g. "Input. SpitfireLFMkIX.pitch_slider" for "Engine RPM (analog)": a search for "engine rpm" found nothing readable). The ID refresh now reads input.mo itself (AppendEnglishNamesShim) and answers dtranslate('input', key) for keys (Input.*, <module>:Inp: / :Cat:) with the English text, whatever language DCS or Windows uses; the step list says "English DCS command names: n". Names that already are English keep DCS's source text: the catalog rewords about 1000 of them ("Throttle Up" -> "Throttle Levers - UP"), which would make lists built before and after disagree. Checked on DCS 2.9.30 (read only, refresh into a temp data folder): 0 raw titles / categories after (3682 / 512 before), ids and combos identical, only the key rows changed. The shipped list (EngineOnly_Runtime\DB\DCS) is rebuilt.

A list built before (the user's, until the next DB refresh) is translated when it is read (DcsCommandNames, used by InternalDataManagement.ParseDcsHtmlInputs and the GUI's title lookups) from the installed DCS's input.mo; without a DCS install the sibling list's title (_easy, CW) or a readable form of the key ("Pitch minus") is shown.

#Commands from mods

Mods add commands to DCS's controls list without a new DCS version. JoyPro's list must have them too, else a relation says "the id is not in its list" for a command DCS shows (for example the F-16C's "C & I Knob - UFC else BACKUP (2-way Switch)", d3001pnilu3001cd35vd1vpnilvu0, and about 140 more "X else Y (2-way Switch)" commands in "Special For Joystick").

  • Quaggles' DCS Input Command Injector (github.com/Quaggles/dcs-input-command-injector), mostly with a community pack such as munkwolf's dcs-community-keybinds. Version 1.1.0 (2026-08) is a hook, <DCS>\Scripts\Hooks\QuagglesInputCommandInjector.lua; older versions replaced <DCS>\Scripts\Input\Data.lua. Both wrap DCS's loader of the input files (Input.Data loadDeviceProfileFromFile): after DCS runs an input file under ./Mods/aircraft/<x> (its folder there too) or (./)Config/Input/<x>, the file <Saved Games>\<variant>\InputCommands\<x> runs in the same environment (the module's devices, command tables and _), and its keyCommands and axisCommands (no axes for the keyboard) are joined to the module's. Examples: InputCommands\F-16C\Input\F-16C\joystick\default.lua, InputCommands\AJS37\Input\joystick\default.lua (a module without a profile folder), InputCommands\Aircrafts\common_joystick_binding.lua (included by many modules through external_profile("Config/Input/Aircrafts/common_joystick_binding.lua")). Files of Saved Games modules get nothing (the injector only matches DCS's relative paths). DCS then gives the joined commands their ids itself.
  • Modules in <Saved Games>\<variant>\Mods\aircraft: DCS loads them like installed modules; the refresh lists them.

Why a list could lack them (an OpenBeta install with its binds in Saved Games\DCS.openbeta): the headless refresh runs DCS's own Lua in luae.exe, where no hook of Scripts\Hooks runs, so the 1.1.0 injector never merged anything; and the refresh read Saved Games\DCS (the old GUI default), not DCS.openbeta where the pack is.

The refresh (dcs refresh id / clean, EngineDcsRefresh.ResolveModInputs, DcsModInputs):

  • reads the Saved Games folder of the install's variant: dcs_variant.txt "openbeta" (or an install folder named OpenBeta) means Saved Games\DCS.openbeta, also when --path names Saved Games\DCS beside it (not when that folder is the user's config location in Settings > Games); the step list says so;
  • merges InputCommands the way the injector does (AppendInputCommandsInjection: the same loader wrapper and the same mapping of paths, with JoyPro's own copy of the merge, so it works whether DCS's Data.lua is patched or not; a patched Data.lua's own merge is turned off in the sandbox so nothing is joined twice). --input-commands auto (the GUI) merges when the injector is installed in this DCS (a Scripts\Hooks\*.lua with "InputCommandInjector", or a patched Data.lua), as DCS does; on always, off never. The injector's settings.lua and state.lua are not command files. Every merged file is listed ("InputCommands Files Merged"), a broken one is a warning (DCS shows an error for it and leaves it out).

Checked with DCS 2.9.30 (read only, a temporary Saved Games folder with a community pack of 248 files, temporary data folder): 134 files merged (the others are device files of devices not connected, modules not installed, or the old Flaming Cliffs layout DCS does not load), 15425 more commands in 44 lists, none lost, e.g. F-16C_50 1125 -> 1494, FA-18C_hornet 1082 -> 1415, AJS37 994 -> 998, AH-64D_BLK_II_PLT 741 -> 1064; both C & I ids as in the pack's .diff.lua (...vd1vpnilvu0, ...vd0vpnilvu1). Of the 4495 command ids in a matching set of bind files, 59 were missing from the list without the pack and 13 with it (F-14, F-4E, TF-51D, Mosquito: commands of DCS 2.9.31 or old binds).

Outdated list (db check-updates): the recorded state (DB\DCS\source-version.txt) has mod-inputs = a fingerprint (names, sizes, dates; no file is read) of the InputCommands files and of the Saved Games modules' input files and entry.lua, plus how the injector is installed, in the Saved Games folder of the installed DCS (Settings > Games, else the variant's folder). Only when there are any: a DCS without mods never counts as changed. A list recorded without it while mod files exist (every list built before 2.6.1), a changed, added or removed file, or an injector installed later make the DCS list "game-updated" with Reason "mods": "Your DCS mods changed the controls list; rebuild the command list." The Start page shows it with Refresh DB; the refresh records the new state.

Safety net: commands in your bind files (DcsFoundCommands): an import or scan that reads a command in DCS's own .diff.lua (a .jp copy only when the .diff.lua beside it has the id) whose aircraft has a list without that id records it with the file's exact id and DCS's name in <data>\GameData\DcsCommandsFromYourFiles.tsv (outside DB\DCS, so the load correction's fingerprint does not change). Every DCS list read adds them (category "Found in your DCS files"), so JoyPro knows them instead of "not in its list"; the Relations page marks them "from your DCS files". New ones make db check-updates say "Your DCS bind files use commands the command list does not have; rebuild the command list." (Reason "binds"). A refresh drops the ones the new list has and keeps the others as "kept" (known, no more hints); Keep DB keeps them all. Nothing is guessed: aircraft without a list record nothing.

Tests: engine\tests\smoke\dcsmodcommands.ps1 (variant folder, auto/on/off, the outdated states, the safety net and, with the DCS install on the PC, the real refresh of F-16C_50 and AJS37 with JoyPro's own small pack in tests\fixtures\dcsmodcommands).

#Default binds and clean profiles

For each aircraft DCS loads the device's defaults from the profile's joystick folder: <device type>.lua when it exists, else default.lua; then the module-independent Config\Input\Aircrafts\Default\joystick\ files. A template diff <device type>.diff.lua in the install applies while the user has no diff of that device. default.lua itself asks defaultDeviceAssignmentFor("pitch" | "rudder" | "left_wheel_brake" | ...), which answers per device type from Scripts\Input\DefaultAssignments.lua (MFG Crosswind V2: rudder JOY_RZ, wheel brakes JOY_X/JOY_Y inverted; panels such as WINWING F18 TAKEOFF PANEL or F16 MFD: no axes) and from the user's Config\Input\wizard.lua. So the same aircraft has different defaults per device type (A-10C II: generic stick 17 default binds, Warthog stick 33, Warthog throttle 38, WINWING F18 takeoff panel 12).

JoyPro takes over whole devices (see README, rule 5), so it removes the defaults of every device it writes. The removals come from clean profiles in the game-data folder, built on the user's PC from the user's DCS:

  • CleanProfile\DCS\<profile>.cf: the generic stick (default.lua).
  • CleanProfile\DCS\<profile>\<device type>.cf: a device type whose defaults differ from the generic ones in that aircraft, or that has a default file in the aircraft's folder.
  • CleanProfile\DCS\device-types.txt: the device types the clean profiles were built for. A listed type without a .cf of its own has exactly the generic stick's defaults there.
  • KeyboardCleanProfile\DCS\<profile>.cf: the keyboard. Refreshed 2026-10-10 by the headless Lua refresh (118 profiles; the March 2025 set differed in 70: common keys such as F9/\ missing, MiG-21 Num+/Num- with the old signs, MiG-29/Su-25 commands moved to other device ids, 4 new profiles). Check: a clean export with --keep-keyboard-defaults false --clear-keyboard-defaults true into a temporary Saved Games for all 118 profiles, every written file loads in DCS's luae.exe.

The export picks <profile>\<device type>.cf for the device (also for a device that is not connected, whose JoyPro name has no spaces at the ends), else <profile>.cf. It warns when a written device's type has defaults of its own (DefaultAssignments.lua) that the clean profiles were not built for (lists from before 2026-10-17: update the DCS list once).

#Refresh (engine dcs refresh clean --headless-lua true)

Runs DCS's own input code in bin\luae.exe (no game window): Input.Data loads every input profile, registers a generic fake stick and one fake stick per device type (Input.addFakeJoystick("<type>"), which DCS names "<type> {FAKE-JOYSTICK-nnnn}"), calls InputData.clearProfile for every profile and saveChanges. The diffs DCS writes are the clean profiles above. The device types:

  • every type with a default file of its own in some aircraft (install and Saved Games mods);
  • every type Scripts\Input\DefaultAssignments.lua names (evaluated by Lua in the same run);
  • every joystick connected now (luae.exe sees the PC's DirectInput devices) and every device the user's Config\Input\*\joystick\*.diff.lua names (the user's devices that are not connected; read only). Everything is written into a temporary Saved Games folder; the user's Config\Input is never changed. --plane/--planes limit the aircraft. A file the strip option (below) patched is read from its .nocombo.bak, so the clean profiles always hold DCS's real defaults (checked: FA-18C and F-15C from a stripped copy of the install are byte-identical to those from the untouched install). Before the refresh JoyPro re-applies the switched-on install options. It writes 5071 clean profiles for a large install (85 profiles, 136 device types; 9 MB; before: 1145).

#Speed of the headless refreshes (dcs refresh id and clean)

Both run DCS's Lua in several luae.exe at once (EngineDcsRefresh.Parallel.cs): every run lists all input profiles (so DCS merges and aliases profiles of the same name the same way in every run) and works on its share: DCS's default profiles (General, UiLayer, ...) in a run of their own, the aircraft one per run (clean) or a few per run (ID). The aircraft that took longest in the last refresh start first (<data>\Cache\dcs-refresh-times.tsv; the clean refresh uses the ID refresh's times until it has its own). An aircraft slower than a worker's share of the whole is cleared by several runs, each with every n-th fake stick (a device's diff does not depend on the other devices); the connected joysticks themselves are left out of the clean runs (only their fake sticks are cleared). Runs at once: one per CPU but one, at most 16, and only as many as the free memory allows (clean ~0.9 GB, ID ~0.7 GB per run; one run measured at most 0.55 GB), at below normal priority. luae.exe crashes now and then while DCS saves the diffs (exit code 0xC000041D, about 1 of 90 runs with 16 at once; the refresh retried a failed run before too): such a run is repeated at once, up to three runs per aircraft; an aircraft that still fails is skipped with a warning and keeps its previous clean profiles (as before). The folders DCS saves an aircraft's diffs into are made before its run (DCS's lfs.mkdir in luae.exe starts cmd.exe, once per device); a folder DCS saved nothing into is ignored. JOYPRO_DCS_LUA_WORKERS=<n> limits the runs at once (1 = one after the other), JOYPRO_DCS_LUA_CHUNK=<n> sets n aircraft per run. Two DCS functions are made cheaper in the runs: InputData.clearProfile validated a command again after every device (one A-10C with ~100 fake sticks: 10 s), now once after its last device; makeHtml sorted the profile's commands again for every device page, now once per profile. DCS's own code is called otherwise unchanged and both fall back to DCS's functions when DCS changes them. The ID refresh writes DCS's InputLayoutsTxt into a temporary folder (before: <Saved Games>\InputLayoutsTxt, which was deleted); it still reads the user's Config\Input.

Measured on a PC with 16 cores ( DCS 2.9.30, 85 aircraft, 13 connected devices; old vs new engine on copies, the written DB, clean and keyboard profiles byte-identical): dcs refresh id 277 s -> 12-14 s, dcs refresh clean 1408 s -> 46-57 s (61-67 s on a first clean refresh with only the ID refresh's times or none; the F-4E alone took 75 s before its fake sticks were split over runs). A cancel (JOYPRO_CANCEL_FILE) stops every luae.exe and writes nothing.

#Root cause of "DCS defaults stay on my device" (fixed 2026-10-17)

Checked with engine dcs verify-clean on a copy of the user's Saved Games after a GUI-default export (merge), with the clean profiles of 2026-10-13:

  1. The written devices kept every DCS default in the aircraft the profile does not bind (C-130J, CH-47F, F-100D, ...) and in exported aircraft where that device has no bind (a device bound only in some aircraft): only clean mode touched other aircraft, and never the exported ones. Now every mode removes the DCS defaults of the written devices in every aircraft (--clean-all-aircraft, default true; outside clean mode the files keep their binds). (2.5.0 changed this again: clean + nuke is the default and works only in the exported aircraft, the import brings the active defaults into the profile, merge and add keep DCS's defaults; see Export modes.)
  2. The refresh built device-type clean profiles only for types with a default file of their own. Types that DefaultAssignments.lua gives other axes (MFG Crosswind V2, the WINWING / F16 MFD panels, ...) got the generic stick's removals: F-15C "Wheel Brake Left" stayed on the MFG's JOY_X, and the panels got removals of axes they never had. Now these types and all of the user's own devices get their own clean profiles. Result on the same copy: 0 DCS defaults left on the written devices (also the disconnected ones, checked with fake sticks), in every aircraft; left only in the input layers JoyPro does not touch ("General" = Config\Input\Aircrafts
    Default, Combined Arms = ground_unit) and on the devices JoyPro does not write (devices outside the profile, e.g. the extra HID interfaces of a Wooting keyboard), which nuke or the strip option below cover. Old-vs-new export diff (same profile, same DB): 1616 files identical, 313 new (other aircraft), 91 MFG / WINWING files with the exact removals of their type instead of the generic ones; no added bind or force feedback setting changed; all 932 written files load in DCS's luae.exe, none has a BOM. Not covered: a device the user ran DCS's axis wizard for (wizard.lua, per device instance) keeps the wizard's assignment as its default.

#Checking (engine dcs verify-clean)

engine dcs verify-clean [--path <Saved Games\DCS>] [--planes ...] [--devices ...] [--include-disconnected true]: DCS's own Lua loads every input profile with a temporary copy of the folder's Config\Input (diffs, modifiers, wizard.lua, disabled.lua) and lists every bind still active on a joystick that its .diff.lua does not add itself: DCS defaults that stay. Connected joysticks are checked as DCS names them; with --include-disconnected the devices that only have files get a fake stick of their type with a copy of their files. "Defaults Left On JoyPro Devices" counts those on files JoyPro wrote (a .jp next to them). About 90 s for all aircraft.

#Default binds in the DCS install (Settings > DCS: default binds)

Two optional changes to the DCS installation itself, for all devices (also those JoyPro does not write), both off by default: JoyPro's export already removes the defaults of the devices it writes (above), and patched files fail the integrity check of multiplayer servers that enforce it. The GUI shows that warning and asks before each change.

  • Strip (engine dcs strip-defaults [apply|restore|status|auto] [--dry-run] [--restore] [--skip-ui-layer]): every *.lua in a folder named joystick under <DCS>\Mods, <DCS>\Config and Saved Games\DCS*\Mods (not *.diff.lua; only files with keyCommands, axisCommands or external_profile) is wrapped in a function, and the table it returns gets combos = nil on every keyCommands/axisCommands entry. The first line is the marker -- [[DCS_STRIP_JOYSTICK_DEFAULTS v1]], the original stays as <file>.nocombo.bak (the community script's names: either one can undo the other's work; JoyPro's restore covers files that script patched). Original bytes, line ends and a UTF-8 BOM stay. After patching, DCS's own loader (Input.Data.loadDeviceProfileFromFile in luae.exe) reads every patched file and its original: same commands, no combos left; a file that fails is put back at once. On a copy of a full install: 218 files, all compared, 2525 default binds switched off; restore byte-identical (8231 files). --skip-ui-layer keeps Config\Input\UiLayer. The user's Saved Games\DCS\Config\Input is never touched, and nothing below a folder named keyboard (the keyboard's defaults) is ever patched or moved, also by the device files switch below.
  • Device files (engine dcs device-luas [list|remove|restore]): the device-specific default files of the joystick folders (<device type>.lua and template diffs <device type>.diff.lua, not default.lua) move into <data>\DcsDefaults\DeviceLuas (with manifest.json), so DCS uses default.lua for every device (JoyPro 1's way). Files another Lua file of the module names stay, and so does the UI layer (its VR controller files make the menus usable in VR). On a full install: 554 files. After a move or restore the clean profiles no longer match what DCS loads; the GUI rebuilds them and the export warns until then. engine dcs defaults restore still puts back what an older JoyPro moved into Saved Games\DCS\BACKUP_JOYSTICK_DEFAULTS.
  • The switches are kept in <data>\DcsDefaults\state.json. A DCS update or repair brings original files back; with a switch on, JoyPro does it again at its start (strip-defaults auto), before every DCS list refresh and on "Apply now". status reports what is patched, what DCS brought back (Needs Reapply) and the DCS version. All commands refuse while DCS or its updater runs; without write access to the DCS folder they say so.

#Export modes

Since 2.5.0 (engine/EngineDcsExport.Modes.cs) every mode works on the binds a device file has active in DCS: the device's defaults (its clean profile) minus the file's removed, plus its added and changed (what DCS's Scripts\Input\Data.lua applies). The mode decides which binds shall be active, and the .diff.lua then holds only real differences from the defaults:

  • an added bind that is no default, a removed default, and a default whose axis tuning (curvature, dead zone, saturation, invert, slider) differs, written as DCS's changed;
  • a bind equal to a default is not written: no default is removed and added again (Binds Equal To A DCS Default (Not Written) in the report). The .jp lists it with JoyPro's relation name for a re-import, but never a default the game has by itself;
  • a removal of the file that the clean profile does not know (an older list) stays unless the bind shall be active.

The modes, per device file of an exported aircraft (an input is device, key and modifiers):

  • add ("Only add") never deletes anything. A profile bind already active stays as the game has it; one whose input the game uses for another function (also a DCS default) is not written and lands in SkippedTakenInputs and the profile's marks (export).
  • merge ("Update, keep the game's binds") keeps the game's binds and DCS's defaults, except a bind of another function on an input the profile uses (Game Binds On Taken Buttons Removed). The profile's tuning wins on its own binds. A moved action keeps its old input.
  • merge-overwrite ("Update, my profile wins", the engine's default when --mode is left out) does what merge does, and every action the profile binds in the aircraft keeps only the profile's inputs: on the written devices and in the aircraft's device files of the other connected devices (Other Buttons Of Profile Actions Removed). Not touched: the files of other devices that are not connected (2.6.0; up to 2.5.0 they lost the profile's actions too), connected devices without a file (they keep DCS's defaults; nuke clears those), the import's ignored devices and the vJoy tunnel; the keyboard only when it is exported.
  • clean ("Replace on my devices", the GUI's default with nuke since 2.5.0): the written devices get exactly the profile's binds in the exported aircraft. Only with --clean-all-aircraft true (default false since 2.5.0, GUI "DCS: my devices lose the DCS default binds in every other aircraft too", off) they also lose their binds and DCS defaults in every other installed aircraft (input layers such as UiLayer, Camera and Default are not touched). Up to 2.4.3 every mode removed the written devices' defaults in every aircraft.
  • --nuke-untouched-devices true: in the exported aircraft, the connected devices the profile does not use there lose all binds and their DCS defaults. A device that is not connected keeps its files (an import with "only connected devices" did not read it), and so do --ignore-device(s) and the --vjoy-tunnel device (the GUI passes the import's ignore list and its vJoy setting).
  • A device whose binds are all DCS defaults and that has no file gets none. An export changes no file of an aircraft it does not export (also not the keyboard repair below).
  • Force feedback settings (ffDiffs) of a file that is emptied stay.

#Import of the default binds ("Include defaults", on by default in the GUI since 2.5.0)

The import takes every default bind DCS has active for an imported device, so that import followed by a clean + nuke export leaves the game with the same binds (smoke\dcsexportmodes.ps1; real check below):

  • imported devices: the joysticks whose files the import reads (after device filters, only-connected, the same-name merge) and the connected joysticks that pass the same filters; per imported aircraft each gets its model's defaults, else DCS's generic defaults (default.lua, up to 2.4.3 left out), also where it has no file yet;
  • left out: defaults the file removes; a default of an action the user bound on that device (keyboard: on any device); a default on an input the user uses for another action on that device ("your own binds win"); the second action of an input DCS gives two actions on one device; a keyboard default of an action a joystick default has (the keyboard's defaults stay in the game anyway);
  • the modifiers stay; the same default function and input of several aircraft is one relation.

Real check (2026-10-31, a temporary copy of the user's Saved Games snapshot of 2026-10-26, 2561 files; DCS's own luae.exe via engine dcs verify-clean --include-disconnected true --dump-active <file> before and after):

  • F/A-18C, F-16C, A-10C II imported with defaults, clean + nuke export: no file outside those aircraft changed, 75 files written, all load in luae.exe, no default re-added (25 kept unwritten). Active binds 1077 before, 1037 after: the 40 that went are the F16 MFD 1/2 model defaults in the A-10C II on buttons the user's own binds use for other actions (both fired before; the rule "your own binds win" keeps the user's). No bind was gained.
  • F/A-18C, UH-1H, M-2000C (F16 MFDs without a file there, generic defaults imported): 931 active before and after.
  • Only connected, with three devices unplugged (fake device list): their files stay byte for byte; and without only connected the same devices are imported and keep their binds; only the 20 / 40 rule cases above differ.
  • Undo export after clean + nuke: all 2561 files byte for byte as before.
  • Relations and Check on that copy, 2.4.3 -> 2.5.0: F/A-18C, F-16C, A-10C II 640 -> 640 relations, Check 33 -> 33 warnings, 0 errors, 35 -> 35 actions in several relations (the user's files removed DCS's generic defaults already); F/A-18C, UH-1H, M-2000C 812 -> 835 relations, 25 -> 38 warnings, 0 errors, 27 -> 40 actions in several relations (the generic defaults of the F16 MFDs, active in the game, now come in).

#Keyboard

The keyboard is never taken over like a stick, in any mode; clean, nuke and "every other aircraft" never touch it.

  • --keep-keyboard-defaults true (the default, GUI "DCS: keep keyboard defaults"): the profile's keyboard binds are not exported; no keyboard file is written.
  • --keep-keyboard-defaults false: the profile's keyboard binds are written into keyboard\Keyboard.diff.lua of their aircraft. A DCS default key the profile binds to another action loses that default use (one removed entry); every other DCS default key of the aircraft stays. An aircraft without keyboard binds in the profile gets no keyboard file.
  • --clear-keyboard-defaults true (with keep false, command line only): also every other DCS default key of the written aircraft is removed (KeyboardCleanProfile).
  • Up to 2.4.0, keep false removed every DCS default key of each aircraft the profile had a keyboard bind for, so DCS showed (almost) no keyboard binds there. A keyboard file JoyPro wrote (a Keyboard.jp next to it) that still removes every default key gets them back at the next DCS export, also with keep on; a file that removes only some defaults is the user's own and stays. The export reports Keyboard Default Keys Removed / Restored.
  • Checked by engine\tests\smoke\dcskeyboard.ps1 (every mode, repair, undo, strip/device files, DCS's luae.exe) and on the real F/A-18C keyboard profile: one rebound key removes 1 default instead of all 292.

#Verification

  • Engine smoke (engine\tests\engine_smoke_test.ps1): default removals, kept removals, nuke, clean of the other aircraft and --clean-all-aircraft false, device type clean profiles, DCS device names with spaces (export into the DCS-named file, legacy trimmed files removed, import back to the JoyPro name), no BOM. smoke\dcsdefaults.ps1: strip / restore / status / auto / --skip-ui-layer / dry run / a file the community script patched / device files on a synthetic DCS folder, each back byte for byte.
  • Headless check 2026-10-10 (luae.exe, temporary Saved Games): the fake stick of a device type gives the same diff as the real connected device (WINWING F18 TAKEOFF PANEL); the generic clean profiles of A-10C II and FA-18C are identical to the previous ones. 2026-10-17: the new refresh keeps all 1145 earlier clean profiles byte for byte.
  • In game: tools\e2e\games\DCS.ps1 and DCSCurves.ps1 (binds and axis tuning in the controls menu).