Lists where JoyPro finds the controls file of War Thunder on this PC. The first one is what engine warthunder scan,
engine warthunder import and engine warthunder export use when you give no path. Detect in the Other Games
panel (Start page, Expert import) runs it and puts the first one into File / Folder.
engine warthunder paths --text
Advanced
Every %USERPROFILE%\Documents\My Games\WarThunder\Saves\<folder>\production\machine.blk: the account
Saves\lastlogin.blk names first, then the newest (Saves\last is the copy from before a login).
No options. Reads only; it also works while the game runs or when it is not installed.
Technical internals
Output: JSON (Game, DisplayName, ConfigPaths, Warnings), or text with --text ("War Thunder Config Paths",
"Paths: " and one line per location). Exit code 0, also when nothing was found (empty list).
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 War Thunder actions JoyPro manages (its command list): id, axis or button, category and title. An export
writes only these actions, and the relation editor and the search list them.
engine warthunder catalog --text
Advanced
The list is %LOCALAPPDATA%\JoyPro2\GameData\DB\WarThunder\actions.tsv (when that folder does not exist, the
DB\WarThunder folder next to the engine).
catalog only shows the list; it never builds it. Titles that look like ids are shown readable.
No options. Reads only; works without the game installed.
Technical internals
Output: JSON (Game, Source, Actions with Id, Title, IsAxis, Category, Warnings), or text with
--text ("War Thunder Action Catalog", "Source:", "Actions: ", then ` | axis|button | |` per action).
Without a list: the warning War Thunder action catalog not found: <path> and an empty list, 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 joystick binds War Thunder has now, without changing your profile or the game. Use it to look before an
import. Look first on the game's card of the Start page and Scan in the Other Games panel run it.
engine warthunder scan --text
Advanced
It reads the aircraft and helicopter controls of machine.blk: the last button of a shortcut is the input, the
others in the block are modifiers; devices are matched through the game's deviceMapping{} (VID:PID).
Path (positional or --path): another machine.blk or an exported controls preset.
--ignore-device <name> / --ignore-devices <a;b> (separated by | or ;, --ignore-devices also by commas) leave the binds of those devices out
(a name without {GUID} means every device of that name); a step line names them and counts the binds.
Keyboard binds JoyPro reads in this game are listed too; engine warthunder import takes them only with
--include-keyboard.
Safety: reads only and is not refused while the game runs. It is refused when the game is not installed (set its
folder: engine games install set) or switched off in Settings > Games.
A fresh install has no command list yet: the first scan builds it from the installed game and saves it (a step line
says so).
Technical internals
Output: JSON (ConfigPath, BindingsRead, Bindings with ActionId, Device, Input, IsAxis, Reformers,
Inverted, then Steps, Warnings, Errors), or text with --text ("War Thunder Scan", "Config:", "Bindings
Read:" and the list).
Exit code 0; 1 when the result has errors, for example No War Thunder config file found. Pass the path explicitly.
Unknown options fail with Unknown WarThunder scan argument(s): ...; MSFS options (--game-profile,
--include-disconnected, --include-sim-defaults) are refused.
Binds of the vJoy device JoyPro forwards into (--vjoy-tunnel) are left out.
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'.
--no-game-archives
switch (no value)
Do not read War Thunder's packed archives (gui.vromfs.bin) for the command list: JoyPro's own list of the actions it knows is used (GUI: Settings > Games). scan, import and export build the list only when there is none yet.
In the game Reads War Thunder's files only; nothing changes in the game. A scan only shows what an import would bring and does not change the profile. War Thunder details · what each mode changes
Example
engine warthunder 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 aircraft and helicopter controls of War Thunder into your JoyPro profile, with every value of the game's Axis
setup dialog and the game-wide control options. Nothing in the game changes. The GUI runs it with Import on the
War Thunder card of the Start page.
It reads %USERPROFILE%\Documents\My Games\WarThunder\Saves\<uid>\production\machine.blk (<uid> is your account;
Saves\last before a login). An exported controls preset can be given as the path too.
Default: adds to the open profile (--merge means the same); --replace replaces every relation of the profile by
what the file has.
--include-keyboard also reads the flight keys. The last button of a shortcut is the input, the others in the block
become modifiers.
Game options (sensitivities, inverts, WEP, autotrim, force feedback) become the profile's War Thunder settings (step
line "Game settings imported: ..."; from machine.blk only).
Devices are matched through the game's deviceMapping{} (VID:PID), which is only read.
Safety: reads only, not refused while the game runs; the profile is kept as "Before import from War Thunder" 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 War Thunder config file found. Pass the path explicitly.).
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'.
--no-game-archives
switch (no value)
Do not read War Thunder's packed archives (gui.vromfs.bin) for the command list: JoyPro's own list of the actions it knows is used (GUI: Settings > Games). scan, import and export build the list only when there is none yet.
In the game Reads War Thunder'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. War Thunder details · what each mode changes
Only aircraft/helicopter actions: clean and nuke release those on the written / unused devices; --ignore-device(s) and --vjoy-tunnel devices are never cleared
For beginners
Writes your aircraft and helicopter binds and axis values into War Thunder's machine.blk in place. Tanks, ships,
infantry and the menus are never touched. Close the game first. The GUI's Export now on the War Thunder card runs
it.
Only cataloged aircraft and helicopter controls count; a conflict is another of those on the same input.
--mode
In machine.blk
add
a shortcut is written only when no other flight control uses that input; no block is removed, no bound axis replaced
merge
your shortcuts go in beside the control's others; only conflicts are removed (an axis of another control on yours gets axisId -1)
merge-overwrite (engine default)
as merge, and a control you bind loses its other shortcuts on connected devices the game lists (keyboard only with --include-keyboard)
clean (GUI default)
as merge-overwrite, and the other flight shortcuts and axes of the written devices are released
--nuke-untouched-devices: the same for connected devices without binds in your profile (not with add).
Axis values in the game's units (dead zone, nonlinearity, multiplier, correction, invert, relative control); a
relation without War Thunder values gets its JoyPro curve fitted. The game options you stored are written, also by a
profile without War Thunder binds.
The file's version:i=N line is kept, so the new content is uploaded at login.
Never touched: tank, ship, submarine, infantry and menu controls, deviceMapping{}, config{}, other settings
lines, mouse binds, devices that are not connected or not listed by the game, --ignore-device(s), the
--vjoy-tunnel device, the keyboard without --include-keyboard.
Safety: refused while aces runs; backed up first (.jpbak and the backup store, undo: engine backups list; a
restore raises the file's version); the profile is kept as "Before export to War Thunder". --dry-run writes
nothing.
Technical internals
Output: JSON of the export result or a text report with --text; exit code 1 on an error (War Thunder is running (aces). Close the game first; it overwrites its config on exit., an invalid --mode, no file found).
Without a path it writes the file engine warthunder paths lists first. Hat diagonals, mouse buttons and axis
modifiers are not written.
After a real run: machine.blk.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.
Exclude one device per flag. Example: --ignore-device Keyboard.
--ignore-devices
<csv>
Exclude devices, separated by commas, | or ;. Example: --ignore-devices Keyboard,Mouse.
--no-game-archives
switch (no value)
Do not read War Thunder's packed archives (gui.vromfs.bin) for the command list: JoyPro's own list of the actions it knows is used (GUI: Settings > Games). scan, import and export build the list only when there is none yet.
In the game Writes into War Thunder'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: Documents\My Games\WarThunder\Saves\<uid>\production\machine.blk (BLK text, a diff against the preset). War Thunder details · what each mode changes
Reads the full list from the game's gui.vromfs.bin and rebuilds the catalog: actions the game no longer has are dropped; with --no-game-archives (or --read-game-archives false) only JoyPro's own list, added to the catalog; writes it only when it changes
For beginners
Builds JoyPro's War Thunder command list from the installed game's files, or adds the actions that are new. Run it
after a game update, or when JoyPro says the list is missing. Refresh DB in the Other Games panel (its DB
Source box is the path) and the Start page's notice "Command lists to build or update" run it.
engine warthunder refresh-db --dry-run --text
Advanced
Without a path (or with the game folder) it reads the two control scripts shortcutsgroupaircraft.nut and
shortcutsgrouphelicopter.nut from gui.vromfs.bin and the titles of controls.csv from lang.vromfs.bin, in a
temporary folder that is deleted afterwards.
Path: the game folder, or a folder that holds the two scripts (also with the older sl_ prefix) and optionally
controls.csv.
The list is rebuilt from the scripts: every axis and shortcut (not the USEROPT_ options), category Aircraft or
Helicopter; titles from controls.csv, else the known title, else the id. An action the scripts no longer have
leaves the list.
--dry-run reads everything and writes nothing (step "Dry run: nothing was written."). Without it the list is
written only when it changed.
--no-game-archives (or --read-game-archives false; GUI: Settings > Games, "War Thunder: read the full command
list from the game's archives") leaves the game's archives alone: the list is the current one plus JoyPro's own
War Thunder function list (a step line says so). A folder with the scripts given as the path is read either way.
Safety: only JoyPro's list changes, never a game file; it is refused when the game is not installed or switched off
in Settings > Games. The GUI can cancel it while the game's files are read; nothing is written then.
Technical internals
Output: JSON of the refresh (DryRun, FilesWritten, Steps with Actions: <old> -> <new>, Warnings,
Errors), or text with --text.
Exit code 0; 1 when nothing could be read: War Thunder was not found. Pass --path with the game folder (gui.vromfs.bin) or a folder that holds the control scripts ..., <script> was not found or not readable under <path>. or Could not read War Thunder's archives in <folder>: ...; the list stays unchanged.
Writes %LOCALAPPDATA%\JoyPro2\GameData\DB\WarThunder\actions.tsv (with a header line that has the date). After a
real run the game's build is recorded for engine db check-updates.
What it does Reads the full list from the game's gui.vromfs.bin and rebuilds the catalog: actions the game no longer has are dropped; with --no-game-archives (or --read-game-archives false) only JoyPro's own list, added to the catalog; writes it only when it changes.
Option
Values
Meaning
--path
<source-path>
Same as <source-path>: the game's installation or a file of the game to read the actions from.
--dry-run
switch (no value)
Report what the command would do; nothing is written or changed.
--no-game-archives
switch (no value)
Do not read War Thunder's packed archives (gui.vromfs.bin) for the command list: JoyPro's own list of the actions it knows is used (GUI: Settings > Games). scan, import and export build the list only when there is none yet.
--read-game-archives
truefalse
true (default) reads the game's archives for the full command list, false is the same as --no-game-archives.