Shows where JoyPro finds IL-2 Sturmovik: 1946's binds on this PC: the pilots' settings.ini files in the game's
Users folder, the current pilot first. Detect in the import wizard's Expert import section runs it.
engine il21946 paths --text
Advanced
No options. Listed: your own config location first, then <install>\Users\<pilot>\settings.ini of the pilot
Users\all.ini names as current, then the other pilots' files in name order.
The files are found through the installation: when the game is not detected the list is empty; set its folder with
engine games install set.
Read-only.
Technical internals
Output: JSON (Game, DisplayName, ConfigPaths, Warnings), or with --textIL-2 Sturmovik: 1946 Config Paths, Paths: <n> and the files. Exit code 0; an unknown option fails with Unknown IL21946 paths argument(s): ....
What it does Lists where JoyPro looks for this game's controls on this machine: files, folders or registry keys (your config location from games config set first). A file the game has not written yet can be listed (e.g. Arma Reforger's JoyPro.conf, Project Wingman's Input.ini).
Lists the IL-2 Sturmovik: 1946 commands JoyPro knows: the game's command names per section (move.aileron, ...),
with axis or button and category.
engine il21946 catalog --text
Advanced
No options; read-only, also when the game is not installed.
Categories follow the game's sections: Axes, Aircraft, Gunner, Misc, Views, Snap views, Pan views, Head movement,
Orders and Time. Only the move section holds axes.
A fresh install has no list yet; the first scan, import, export or engine il21946 refresh-db builds it. Until then
the command lists no action and warns IL-2 Sturmovik: 1946 action catalog not found: <path>.
Technical internals
Output: JSON (Game, Source, Actions with Id, Title, IsAxis, Category, Warnings), or with --text
one line per action <id> | axis|button | <category> | <title>; an id is <section>.<command>. Exit code 0.
What it does Lists every action of JoyPro's command list of this game with its kind and category: <data>\GameData\DB\<Game>\actions.tsv, else the program folder's DB\<Game>.
Shows the current pilot's binds of IL-2 Sturmovik: 1946, joystick and keyboard, without changing your profile or the
game. Look first in the import wizard runs it.
engine il21946 scan --text
Advanced
Reads the [HotKey <section>] lines of the file engine il21946 paths lists first (the current pilot), or of the
settings.ini given (positional or --path), for another pilot.
Devices are stored by Windows' order (JoystickDevice0 to 3): each is shown on the connected device at that
position. Axes come with invert; keys with their modifier are listed without --include-keyboard (the import takes
them only with it). The axis response of conf.ini is read but not listed.
--ignore-device <name> / --ignore-devices <a;b> leave the binds of those devices out.
Safety: reads only, also while the game runs; a fresh install first builds and saves the command list. Refused when
the game is not installed or switched off in Settings > Games.
Technical internals
Output: JSON (Game, Actionscan, ConfigPath, BindingsRead, Bindings with Reformers for modifiers,
Steps, Warnings, Errors), or a text report with --text.
Exit code 0; 1 on an error (No IL-2 Sturmovik: 1946 config file found. Pass the path explicitly.). Unknown
options fail with Unknown IL21946 scan argument(s): ....
What it does Reads the game's controls (its control file or folder, or registry values for Nuclear Option and Tiny Combat Arena; Ace Combat 8 stores none) and shows the joystick binds, without changing the profile. Without a command list yet (fresh install) it first builds the list from the game and saves it.
Option
Values
Meaning
--path
<config-path>
Optional explicit path override. Use when you prefer option form over positional path.
--ignore-device
<name>
Leave the binds of this device out (one per flag; a name without {GUID} means every device of that name). Example: --ignore-device 'vJoy Device'.
--ignore-devices
<csv>
Leave the binds of these devices out (separated by commas, | or ;). Example: --ignore-devices 'vJoy Device,Old Pedals'.
In the game Reads IL-2 Sturmovik: 1946's files only; nothing changes in the game. A scan only shows what an import would bring and does not change the profile. IL-2 Sturmovik: 1946 details · what each mode changes
Example
engine il21946 scan --text
How the options interact
--ignore-device / --ignore-devices leave the binds of those devices out of the scan or import (the result names how many).
--ignore-device(s): the binds of these devices are left out
For beginners
Reads the current pilot's binds of IL-2 Sturmovik: 1946 into your JoyPro profile, with the dead band and curve of each
axis. Nothing in the game changes. The GUI runs it with Import on the IL-2 Sturmovik: 1946 card of the Start page.
It reads the pilot's <install>\Users\<pilot>\settings.ini (the current pilot first, as Users\all.ini names it)
and the axis response lines of <install>\conf.ini. <install> is steamapps\common\IL 2 Sturmovik 1946 for Steam.
Default: adds to the open profile (--merge means the same); --replace replaces every relation of the profile by
what the pilot file has.
--include-keyboard also reads the keys (one modifier each).
Devices are stored by Windows' order (JoystickDevice0 to 3): JoyPro maps each to the connected device at that
position.
For another pilot, pass that pilot's settings.ini as the path.
Safety: reads only, not refused while the game runs; the profile is kept as "Before import from IL-2 Sturmovik:
1946" first.
--ignore-device <name> / --ignore-devices <a;b> leave the binds of those devices out (a name without
{GUID} means every device of that name); a step line says how many binds were left out.
Technical internals
Output: JSON of the import result or a text report with --text; exit code 1 on an error (No IL-2 Sturmovik: 1946 config file found. Pass the path explicitly.).
Without a path it reads the first file of engine il21946 paths (the current pilot); a fresh install builds the
command list first.
With --profile the profile is saved afterwards. The imported inputs are recorded as JoyPro's in
settings.ini.joypro.json, and a game JoyPro never exported to is watched from now on.
What it does Imports the game's joystick binds into the loaded profile (merged by default; --replace starts from an empty relation list). Without a command list yet it first builds the list from the game.
Option
Values
Meaning
--path
<config-path>
Optional explicit path override. Use when you prefer option form over positional path.
--replace
switch (no value)
For game import: start from an empty relation list instead of merging into the loaded profile.
--include-keyboard
switch (no value)
--ignore-device
<name>
Leave the binds of this device out (one per flag; a name without {GUID} means every device of that name). Example: --ignore-device 'vJoy Device'.
--ignore-devices
<csv>
Leave the binds of these devices out (separated by commas, | or ;). Example: --ignore-devices 'vJoy Device,Old Pedals'.
In the game Reads IL-2 Sturmovik: 1946's files only; nothing changes in the game. The binds come into the profile as relations; JoyPro's own data next to the game file brings back names, groups, modifiers and curves. IL-2 Sturmovik: 1946 details · what each mode changes
Flight only: clean takes over the devices it writes, nuke clears unused devices; --ignore-device(s) and --vjoy-tunnel devices are never cleared
For beginners
Writes your binds into the pilot's settings.ini of IL-2 Sturmovik: 1946 and the axis lines of conf.ini, so the
game's Controls page shows them. Close the game first. The GUI's Export now on the IL-2 Sturmovik: 1946 card runs
it.
It edits the lines of <install>\Users\<pilot>\settings.ini in place and the [rts_joystick] sections of
<install>\conf.ini.
--mode
In the game
add
nothing is removed; a bind on an input the game uses for another command is listed, not written
merge
your binds go in; a game bind on an input you give another command is removed, the rest stays
merge-overwrite (engine default)
as merge, and every command you bind loses its other inputs (keyboard only with --include-keyboard)
clean (GUI default)
the devices you write lose all their other lines in the managed sections
--nuke-untouched-devices: the other connected devices lose their lines (not with add).
--include-keyboard also writes keys; joystick binds with modifiers are skipped (warning), because the game ignores
a key held while a joystick button is pressed.
The game reads the first four game controllers: a device at position five or later is refused. Axis response:
dead band, ten curve points, filter and the one-sided flag; in merge a curve set in the game stays when JoyPro's is
the plain default.
Never touched: lines of devices that are not connected, lines the import cannot read, mouse lines, keyboard lines
without --include-keyboard, other pilots' files, every other line of conf.ini.
Safety: refused while il2fb runs; both files backed up first (undo: engine backups list); the profile is kept as
"Before export to IL-2 Sturmovik: 1946". --dry-run writes nothing.
Technical internals
Output: JSON of the export result or a text report with --text; exit code 1 on an error (the game runs, an
invalid --mode, no file found).
Without a path it writes the current pilot's file of engine il21946 paths; pass another settings.ini for another
pilot.
After a real run: settings.ini.joypro.json, JoyPro's .joypro-meta.json, the watcher's fingerprint, the export
marks (engine export-marks list).
What it does Writes the profile's binds for this game. Only the flight actions JoyPro manages are changed, the game must be closed, and the game's files are backed up first (engine backups). Without a command list yet it first builds the list from the game.
Option
Values
Meaning
--path
<config-path>
Optional explicit path override. Use when you prefer option form over positional path.
--mode
cleanaddmergemerge-overwrite
Export mode for DCS/IL2 export commands: clean, add, merge, merge-overwrite.
--dry-run
switch (no value)
Report what the export would write; the game's files are not changed.
In the game Writes into IL-2 Sturmovik: 1946's control files while the game is closed (refused while it runs), after a backup. Combat flight sims and combat flight games that read several joysticks. Bind file: <install>\Users\<pilot>\settings.ini ([HotKey ...]), responses in conf.ini. IL-2 Sturmovik: 1946 details · what each mode changes
Reads the installed game or <source-path> and adds its new actions to the catalog, the known ones stay; writes it only when it changes
For beginners
Adds new IL-2 Sturmovik: 1946 commands to JoyPro's command list: JoyPro's own list of the game's commands, then every
command it finds in the game's and your pilots' files. Update on the IL-2 Sturmovik: 1946 card of the Start page
runs it.
engine il21946 refresh-db --dry-run --text
Advanced
Rows the list already has stay; nothing is removed. Read without a path: the pilots' settings.ini files of
engine il21946 paths, <install>\Users\default.ini and <install>\conf.ini.
Path (positional or --path): a settings.ini (that file plus its installation's default.ini and conf.ini) or
the installation folder (those two plus every pilot's settings.ini).
Command names with blanks are skipped. --dry-run writes nothing; otherwise the list is written only when it
changed.
Refused when the game is not installed or switched off in Settings > Games; the game may run.
Technical internals
Output: JSON of the refresh (DryRun, FilesWritten, Steps such as JoyPro's own IL-2 Sturmovik: 1946 command list: <n> new command(s)., Read <file>: <n> new command(s). and Actions: <old> -> <new>, Warnings), or a text
report with --text. A file that cannot be read gives a warning.
Exit code 0; 1 only for a refusal or an unknown option.
Writes %LOCALAPPDATA%\JoyPro2\GameData\DB\IL21946\actions.tsv and records the game's Steam build for
engine db check-updates.