Shows where JoyPro finds the control files of Prepar3D v5 on this PC, in
%APPDATA%\Lockheed Martin\Prepar3D v5\Controls\, the active one first. Detect in the import wizard's Expert
import section runs it.
engine p3d5 paths --text
Advanced
No options. Listed: your own config location of engine games config set first, then the active file (named in
Prepar3D.cfg under [CONTROLS] Controls_Current, else Standard.xml), then every other .xml file of the folder.
Read-only; also works when the sim is not installed or switched off.
Technical internals
Output: JSON (Game, DisplayName, ConfigPaths, Warnings), or with --textPrepar3D v5 Config Paths,
Paths: <n> and the files. Exit code 0; an unknown option fails with Unknown P3D5 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 Prepar3D v5 events JoyPro knows: the sim's event names with axis or button and category.
engine p3d5 catalog --text
Advanced
No options; read-only, also when the sim is not installed.
JoyPro's own FSX/Prepar3D event list plus the events found in the sim's files, in a list of its own. A fresh install
has no list yet; the first scan, import, export or engine p3d5 refresh-db builds it (until then: a warning and no
action).
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>. 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 binds of the active Prepar3D v5 control file, axes, buttons, hats and keyboard keys, without changing your
profile or the sim. Look first in the import wizard runs it.
engine p3d5 scan --text
Advanced
Reads the device maps and the keyboard map of the file engine p3d5 paths lists first, or of the file given
(positional or --path); devices are matched by the GUID in the map name, else by a unique name.
Keys are listed without --include-keyboard; sensitivity and null zone are read but not listed; an event that is
not in the list yet gets a warning naming engine p3d5 refresh-db.
--ignore-device <name> / --ignore-devices <a;b> leave the binds of those devices out.
Safety: reads only, also while the sim runs; a fresh install first builds and saves the command list. Refused when
the sim is not installed or switched off in Settings > Games.
Technical internals
Output: JSON (Game, Actionscan, ConfigPath, BindingsRead, Bindings, Steps, Warnings, Errors), or
a text report with --text.
Exit code 0; 1 on an error (No Prepar3D v5 config file found. Pass the path explicitly.). Unknown options fail
with Unknown P3D5 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 Prepar3D v5's files only; nothing changes in the game. A scan only shows what an import would bring and does not change the profile. Prepar3D v5 details · what each mode changes
Example
engine p3d5 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 active controls file of Prepar3D v5 into your JoyPro profile: axes, buttons and hats with each axis's
sensitivity and null zone. Nothing in the sim changes. The GUI runs it with Import on the Prepar3D v5 card.
It reads %APPDATA%\Lockheed Martin\Prepar3D v5\Controls\Standard.xml, or the file Prepar3D.cfg names under
[CONTROLS].
Default: adds to the open profile; --replace replaces every relation of the profile by what Prepar3D v5 has.
--include-keyboard also reads the keyboard map.
Safety: reads only, not refused while the sim runs; the profile is kept as "Before import from Prepar3D v5" 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 config file found).
Without a path it reads the first file of engine p3d5 paths; a fresh install builds the command list first.
With --profile the profile is saved afterwards. The imported inputs are recorded as JoyPro's in
<file>.joypro.json (so merge-overwrite can later replace them), 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 Prepar3D v5'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. Prepar3D v5 details · what each mode changes
It edits the device maps of %APPDATA%\Lockheed Martin\Prepar3D v5\Controls\Standard.xml (or the active file).
--mode
In the controls file
add
never removes or replaces a block; a bind on a taken input is listed, not written
merge
replaces the event on your input, keeps everything else
merge-overwrite (engine default)
also removes the other inputs of the events you bind
clean (GUI default)
the main maps of the devices you write keep only your binds
--nuke-untouched-devices empties the main maps of the other connected devices (not with add);
--include-keyboard also writes the keyboard map.
Never touched: devices that are not connected, --ignore-device(s), the --vjoy-tunnel device, slew and mouse
maps, per-SimObject maps.
Safety: refused while Prepar3D runs; backed up first (undo: engine backups list); the profile is kept as "Before
export to Prepar3D v5". --dry-run writes nothing.
Technical internals
Output: JSON of the export result or a text report with --text; exit code 1 on an error.
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 Prepar3D v5's control files while the game is closed (refused while it runs), after a backup. Civil and general flight simulators. JoyPro takes over the devices it writes (clean and nuke clear every other bind of those devices). Bind file: %APPDATA%\Lockheed Martin\Prepar3D v5\Controls\Standard.xml (XML). Prepar3D v5 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 events to JoyPro's Prepar3D v5 command list: JoyPro's own event list, then every event used in the sim's
control files and presets. Update on the Prepar3D v5 card of the Start page runs it.
engine p3d5 refresh-db --text
Advanced
Rows the list already has stay; nothing is removed. Read without a path: the files of engine p3d5 paths,
Standard.xml in the installation folder and the preset Controls\Standard.xmlx. A path: a folder reads every
*.xml* file in it, a file only that file.
--dry-run writes nothing; otherwise the list is written only when it changed.
Refused when the sim is not installed or switched off in Settings > Games; the sim may run.
Technical internals
Output: JSON of the refresh (DryRun, FilesWritten, Steps with the new events per file and Actions: <old> -> <new>, Warnings), or a text report with --text.
Exit code 0; 1 only for a refusal or an unknown option.