JoyPro2 Discord GitHub
Engine (CLI)

engine pw (Project Wingman)

Show:

6 commands of engine pw. Each with every option and every value it takes, what it does, which GUI buttons use it, and an example.

#engine pw paths

written
engine pw paths
For beginners

Shows where JoyPro finds Project Wingman's binds on this PC: %LOCALAPPDATA%\ProjectWingman\Saved\Config\WindowsNoEditor\Input.ini. Detect in the import wizard's Expert import section runs it.

engine pw paths --text
Advanced
  • No options. Listed: your own config location of engine games config set first, then Input.ini. The file is listed once %LOCALAPPDATA%\ProjectWingman exists, also before the game wrote it (the game writes it at the first change in its controls menu); an export then starts from the game's defaults.
  • The curves and dead zones are read from ...\Saved\SaveGames\savegame.sav; that file is not listed.
  • Read-only; also works when the game is not installed or switched off.
Technical internals
  • Output: JSON (Game, DisplayName, ConfigPaths, Warnings), or with --text Project Wingman Config Paths, Paths: <n> and the file. Exit code 0; an unknown option fails with Unknown ProjectWingman paths argument(s): ....
  • Related: engine pw scan, engine games paths; game page project-wingman.

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).

Example

engine pw paths --text

#engine pw catalog

written
engine pw catalog
For beginners

Lists the Project Wingman actions JoyPro knows: the game's flight, weapon and view actions, with axis or button.

engine pw catalog --text
Advanced
  • No options; read-only, also when the game is not installed.
  • Categories: Flight axes, Weapons, View and Misc; menu rows and the mouse axes are not in the list.
  • A fresh install has no list yet; the first scan, import, export or engine pw refresh-db builds it. Until then the command lists no action and warns Project Wingman 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>. The ids are the game's action names (Gun Fire, Pitch Axis ...). Exit code 0.
  • File: %LOCALAPPDATA%\JoyPro2\GameData\DB\ProjectWingman\actions.tsv.
  • Related: engine pw refresh-db; game page project-wingman.

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>.

Example

engine pw catalog --text

#engine pw scan

written
engine pw scan [<config-path>] [--path <config-path>] [--ignore-device <name>] [--ignore-devices <csv>]
For beginners

Shows the joystick binds Project Wingman has for your connected devices, with invert, without changing your profile or the game. Look first in the import wizard runs it.

engine pw scan --text
Advanced
  • Reads the ActionMappings and AxisMappings lines with a Joystick_... key of the file engine pw paths lists, or of the file given (positional or --path).
  • The game numbers a device by its place in its device list: JoyPro maps the number to the devices connected now and warns when a device's number moved. Keyboard, mouse and pad mappings are not shown.
  • The curve and dead zone of each axis action are read from savegame.sav; the scan output does not list them.
  • --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, Action scan, ConfigPath, BindingsRead, Bindings, Steps, Warnings, Errors), or a text report with --text.
  • Exit code 0, also when Input.ini does not exist yet (warning Input.ini does not exist yet (<path>): the game has its default binds, none on a joystick.); 1 on an error (no config location, an unreadable file). Unknown options fail with Unknown ProjectWingman scan argument(s): ....
  • Related: engine pw import, engine pw catalog; game page project-wingman.

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.

OptionValuesMeaning
--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 Project Wingman's files only; nothing changes in the game. A scan only shows what an import would bring and does not change the profile. Project Wingman details · what each mode changes

Example

engine pw 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).

#engine pw import

written
engine pw import [<config-path>] [--path <config-path>] [--replace] [--include-keyboard] [--ignore-device <name>] [--ignore-devices <csv>]

--ignore-device(s): the binds of these devices are left out

For beginners

Reads Project Wingman's joystick binds of the flight actions into your JoyPro profile, with invert, curve and dead zone. Nothing in the game changes. The GUI runs it with Import on the Project Wingman card of the Start page.

engine pw import --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced

It reads %LOCALAPPDATA%\ProjectWingman\Saved\Config\WindowsNoEditor\Input.ini (ActionMappings, AxisMappings) and the curves and dead zones per axis action from ...\Saved\SaveGames\savegame.sav.

  • Default: adds to the open profile (--merge means the same); --replace replaces every relation of the profile by what the game has.
  • No keyboard or modifier binds; --include-keyboard changes nothing.
  • The game numbers a device by its place in its device list: JoyPro maps it with the devices connected now and warns when a device's number moved.
  • Safety: reads only, not refused while the game runs; the profile is kept as "Before import from Project Wingman" 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 Project Wingman config file found. Pass the path explicitly.).
  • Without a path it reads the file engine pw paths lists first; a fresh install builds the command list from the game's pakchunk0-WindowsNoEditor.pak first.
  • With --profile the profile is saved afterwards; a game JoyPro never exported to is watched from now on.
  • Related: engine pw scan, engine pw export; game page project-wingman.

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.

OptionValuesMeaning
--path<config-path>Optional explicit path override. Use when you prefer option form over positional path.
--replaceswitch (no value)For game import: start from an empty relation list instead of merging into the loaded profile.
--include-keyboardswitch (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 Project Wingman'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. Project Wingman details · what each mode changes

Example

engine --profile 'C:\JoyPro\profiles\pilot_main.pr0file' pw import --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).

#engine pw export

written
engine pw export [<config-path>] [--path <config-path>] [--mode clean|add|merge|merge-overwrite] [--dry-run] [--include-keyboard] [--nuke-untouched-devices] [--ignore-device <name>] [--ignore-devices <csv>]

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 Project Wingman's Input.ini and the curves and dead zones into its save game. Close the game first, and export again after you add or remove a controller. The GUI's Export now on the Project Wingman card runs it.

engine pw export --mode clean --nuke-untouched-devices --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file"
Advanced

Only joystick mappings of cataloged flight actions are removed. Project Wingman counts as a flight-only game.

--mode In Input.ini
add a bind on an input the game uses for another flight action gets a mark "Not written to the game"
merge also removes the game's mapping on an input the profile gives another action; the action's other mappings stay
merge-overwrite (engine default) also removes the other joystick mappings of every action the profile binds
clean (GUI default) the exported devices lose their other joystick mappings
  • --nuke-untouched-devices: the same on the other connected devices (not with add).
  • A written list replaces the game's defaults, so JoyPro writes the defaults of a missing list first. Curve (0.00 to 2.00) and dead zone (0 to 100 %) per axis action go into savegame.sav, for all devices together.
  • A hat bind is refused: the game binds no hats (set Hat Function in its controls).
  • Never touched: keyboard, mouse and pad mappings, menu rows, devices that are not connected, --ignore-device(s), the --vjoy-tunnel device, every other line of Input.ini and byte of savegame.sav.
  • Safety: refused while ProjectWingman-Win64-Shipping or ProjectWingman runs; backed up first (undo: engine backups list); the profile is kept as "Before export to Project Wingman". --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 file engine pw paths lists first. Device numbers come from the devices connected at the export.
  • After a real run: Input.ini.joypro-meta.json, the watcher's fingerprint, the export marks (engine export-marks list).
  • Related: engine pw import; game page project-wingman.

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.

OptionValuesMeaning
--path<config-path>Optional explicit path override. Use when you prefer option form over positional path.
--modeclean add merge merge-overwriteExport mode for DCS/IL2 export commands: clean, add, merge, merge-overwrite.
--dry-runswitch (no value)Report what the export would write; the game's files are not changed.
--include-keyboardswitch (no value)
--nuke-untouched-devicesswitch (no value)DCS export only: delete untouched device .diff.lua/.jp files under Config\\Input (true/false).
--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.
Every value as a command line
engine pw export --mode clean
engine pw export --mode add
engine pw export --mode merge
engine pw export --mode merge-overwrite

In the game Writes into Project Wingman's control files while the game is closed (refused while it runs), after a backup. Arcade flight games and shooters that read one joystick, only Xbox pads, or a fixed layout (docs: one-device-games.md). Bind file: %LOCALAPPDATA%\ProjectWingman\Saved\Config\WindowsNoEditor\Input.ini (Unreal ini, per device name and place) + curves and dead zones in savegame.sav. Project Wingman details · what each mode changes

Example

engine --profile 'C:\JoyPro\profiles\pilot_main.pr0file' pw export --dry-run --text engine --profile 'C:\JoyPro\profiles\pilot_main.pr0file' pw export --mode merge-overwrite --text

#engine pw refresh-db

written
engine pw refresh-db [<source-path>] [--path <source-path>] [--dry-run]

Rebuilds the catalog from the installed game or <source-path>: actions the game no longer has are dropped; writes it only when it changes

For beginners

Builds JoyPro's Project Wingman command list from the game's default controls and your Input.ini. Update on the Project Wingman card of the Start page runs it.

engine pw refresh-db --text
Advanced
  • Reads the default input file inside ProjectWingman\Content\Paks\pakchunk0-WindowsNoEditor.pak of the detected installation, then the actions of your Input.ini. A path (positional or --path) may be the game folder, the .pak file or another Input.ini.
  • Menu rows and the mouse axes are left out. The list is rebuilt from these sources.
  • --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 Read <n> flight action(s) from <pak> and <ini>. and Actions: <old> -> <new>, Warnings, Errors), or a text report with --text.
  • Exit code 0; 1 when nothing could be read (Neither the game's pak nor an Input.ini was found: install Project Wingman (or pass its folder) and start it once.); the list stays unchanged.
  • Writes %LOCALAPPDATA%\JoyPro2\GameData\DB\ProjectWingman\actions.tsv.
  • Related: engine pw catalog, engine pw export; game page project-wingman.

What it does Rebuilds the catalog from the installed game or <source-path>: actions the game no longer has are dropped; writes it only when it changes.

OptionValuesMeaning
--path<source-path>Same as <source-path>: the game's installation or a file of the game to read the actions from.
--dry-runswitch (no value)Report what the command would do; nothing is written or changed.

Example

engine pw refresh-db --text