Shows what engine il2 import would bring from IL-2 Great Battles with the same options, without changing the profile
or the game. On the Start page Look first in the import wizard and Scan in the expert import run it.
engine il2 scan "D:\Games\IL-2 Sturmovik Battle of Stalingrad" --text
Advanced
The path is the IL-2 folder (positional or --path); without one the installation is detected (Auto-detected IL2 root path: ... on stderr).
--device / --devices, --ignore-device / --ignore-devices, --import-inverted, --import-curvature,
--import-deadzone and --confirm work as in engine il2 import.
Reads only. Refused when IL-2 is not installed.
Technical internals
Output: JSON of the scan, or a text report with --text. Exit code 0; 1 with il2 scan failed: ... (for
example Missing global.actions: <file>) or without a path (il2 scan requires an IL2 root path. Try: engine games paths --game IL2 --text).
Save options (--save-profile, --save-last) and --mode are refused here.
What it does Parses IL2 input files and previews import results.
Option
Values
Meaning
--path
<il2-root-path>
Optional explicit path override. Use when you prefer option form over positional path.
--device
<name>
Include one device per flag. Example: --device LEFT VPC Throttle.
--devices
<csv>
Include devices as CSV. Example: --devices VKB Gladiator NXT,LEFT VPC Throttle.
--ignore-device
<name>
Exclude one device per flag. Example: --ignore-device Keyboard.
--ignore-devices
<csv>
Exclude devices, separated by commas, | or ;. Example: --ignore-devices Keyboard,Mouse.
--import-inverted
switch (no value)
Include axis inversion settings.
--import-curvature
switch (no value)
Include axis curvature settings.
--import-deadzone
switch (no value)
Include axis deadzone settings.
--confirm
truefalse
Controls suggestion confirmation (true) vs auto-accept (false).
Reads the binds you made in IL-2 Great Battles into your JoyPro profile, one relation per action and input. Nothing in
IL-2 changes. Import now in the Start page's import wizard and Import in the expert import run it.
Reads data\input of the IL-2 folder: global.actions (required), devices.txt, current.responses (axis responses)
and JoyPro's own jp.actions (relation names and groups of an earlier export).
--merge adds to the open profile (an action that fits an existing relation joins it); without it the import
replaces the profile's relations and binds.
New relations get the group IL2 unless jp.actions names groups.
--device / --devices limit the import to these devices; --ignore-device / --ignore-devices leave devices
out (the --vjoy-tunnel device is always left out). A name that does not match exactly is resolved to the closest
device; --confirm false takes it without asking.
--import-inverted, --import-curvature, --import-deadzone bring that axis setting into the profile.
Safety: reads only; refused when IL-2 is not installed; the profile is kept as the version "Before import from IL-2"
first.
Technical internals
Output: JSON of the import (relations and binds imported, merged into existing, skipped, warnings), or text with
--text. Exit code 0; 1 with il2 import failed: ....
--save-profile <file> saves the result to that file, --save-last to the last-profile file; with --profile the
profile is saved after the import. A successful import marks IL-2 as imported for engine profile game-state.
In the game Reads IL-2 Sturmovik: Great Battles'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: Great Battles details · what each mode changes
--ignore-device(s) and --vjoy-tunnel devices are never cleared; add never removes and skips a bind whose input the game uses for another action; merge also removes the game's bind on an input the profile gives another action; merge-overwrite also takes the profile's actions off their other inputs; clean releases the other binds of the written devices, nuke the connected joysticks the profile does not use; mouse lines, lines JoyPro cannot read and devices that are not connected stay
For beginners
Writes your profile's binds into IL-2 Great Battles. Use it after you changed binds in JoyPro; close IL-2 first. The
Export page's Export now on the IL-2 card runs it.
Writes the profile into IL-2's data\input files (global.actions keeps its order, new lines at the end; the axis
responses) and JoyPro's jp.actions.
--mode: add never removes and skips a bind whose input the game uses for another action; merge also removes the
game's bind on an input the profile gives another action; merge-overwrite also takes the profile's actions off
their other inputs; clean releases the other binds of the written devices.
--nuke-untouched-devices true also clears the connected joysticks the profile does not use.
Never touched: mouse lines, lines JoyPro cannot read, devices that are not connected, devices passed with
--ignore-device(s) and the --vjoy-tunnel device.
Safety: refused while IL-2 runs; every file is backed up first (undo: engine backups restore);
the profile is kept as the version "Before export to IL-2".
Technical internals
Output: JSON of the export result, or text with --text; exit code 0, 1 on an error or while the game runs.
jp.actions holds JoyPro's names, groups and tuning for a later engine il2 import.
In the game Writes into IL-2 Sturmovik: Great Battles'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>\data\input\*.actions, current.responses, global.pitch, current.devices; jp.actions sidecar. IL-2 Sturmovik: Great Battles details · what each mode changes