JoyPro2 Discord GitHub
Engine (CLI)

engine ac7 (ACE COMBAT 7: Skies Unknown)

Show:

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

#engine ac7 paths

written
engine ac7 paths
For beginners

Shows where JoyPro finds ACE COMBAT 7's binds on this PC: %LOCALAPPDATA%\BANDAI NAMCO Entertainment\ACE COMBAT 7\Config\Input.ini, which the game writes when it closes with your devices connected. Detect in the import wizard's Expert import section runs it.

engine ac7 paths --text
Advanced
  • No options. Listed: your own config location of engine games config set first, then Input.ini when it exists.
  • Read-only; also works when the game is not installed or switched off.
Technical internals
  • Output: JSON (Game, DisplayName, ConfigPaths, Warnings), or with --text ACE COMBAT 7: Skies Unknown Config Paths, Paths: <n> and the file. Exit code 0; an unknown option fails with Unknown AceCombat7 paths argument(s): ....
  • Related: engine ac7 scan, engine games paths; game page ace-combat.

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 ac7 paths --text

#engine ac7 catalog

written
engine ac7 catalog
For beginners

Lists the ACE COMBAT 7 flight actions JoyPro knows (the Flight_* keys of Input.ini), with axis or button and category.

engine ac7 catalog --text
Advanced
  • No options; read-only, also when the game is not installed.
  • Categories: Flight axes, Flight and Hat. Before a list was built from your Input.ini, JoyPro lists its own 20 flight actions; engine ac7 refresh-db, or the first scan, import or export, builds the list from the file.
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.
  • File: %LOCALAPPDATA%\JoyPro2\GameData\DB\AceCombat7\actions.tsv.
  • Related: engine ac7 refresh-db, engine ac8 catalog; game page ace-combat.

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 ac7 catalog --text

#engine ac7 scan

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

Shows the flight-stick binds ACE COMBAT 7 has in its Input.ini for your connected devices, without changing your profile or the game. Look first in the import wizard runs it.

engine ac7 scan --text
Advanced
  • Reads the [Joystick-<product GUID>] sections of the file engine ac7 paths lists, or of the file given (positional or --path): axes with invert (:R), buttons and hat directions.
  • A section of a model that is not connected is skipped with a warning; two devices of one model share a section and are read for the first. Combinations and half axes (:P, :N, :C) are not read (warning each).
  • --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; 1 on an error (No ACE COMBAT 7: Skies Unknown config file found. Pass the path explicitly.). Unknown options fail with Unknown AceCombat7 scan argument(s): ....
  • Related: engine ac7 import, engine ac7 catalog; game page ace-combat.

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

Example

engine ac7 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 ac7 import

written
engine ac7 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 the flight-stick binds of ACE COMBAT 7: Skies Unknown from its Input.ini into your JoyPro profile. Nothing in the game changes. Start the game once with every device connected first, so it writes a section per device. The GUI runs it with Import on the ACE COMBAT 7 card of the Start page.

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

It reads %LOCALAPPDATA%\BANDAI NAMCO Entertainment\ACE COMBAT 7\Config\Input.ini: one [Joystick-<product GUID>] section per device model with its Flight_* keys.

  • Default: adds to the open profile (--merge means the same); --replace replaces every relation of the profile by what the file has.
  • No keyboard or modifier binds; --include-keyboard changes nothing. Invert (:R) comes in, no curves.
  • Two sticks of the same model share one section.
  • Safety: reads only, not refused while the game runs; the profile is kept as "Before import from ACE COMBAT 7: Skies Unknown" 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 ACE COMBAT 7: Skies Unknown config file found. Pass the path explicitly.).
  • Without a path it reads the file engine ac7 paths lists first. Before the file exists JoyPro lists its own 20 flight actions; engine ac7 refresh-db builds the list from the file.
  • With --profile the profile is saved afterwards; a game JoyPro never exported to is watched from now on.
  • Related: engine ac7 scan, engine ac7 export, engine ac8 import; game page ace-combat.

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 ACE COMBAT 7: Skies Unknown'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. ACE COMBAT 7: Skies Unknown details · what each mode changes

Example

engine --profile 'C:\JoyPro\profiles\pilot_main.pr0file' ac7 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 ac7 export

written
engine ac7 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 ACE COMBAT 7's Input.ini, one section per device model. Close the game first. The GUI's Export now on the ACE COMBAT 7 card runs it.

engine ac7 export --mode merge-overwrite --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced

One input per action and device. ACE COMBAT 7 counts as a flight-only game.

--mode In Input.ini
add an action that already has a value on that device keeps it; a bind on an input the game uses for another action gets a mark "Not written to the game"
merge the profile's value is written; another action on the same input is released; the action's values on other devices stay
merge-overwrite (engine default) as merge, and every action the profile binds is cleared on the other connected devices
clean (GUI default) the sections JoyPro writes keep only your readable values; a written axis is still cleared on the other connected devices
  • --nuke-untouched-devices: the readable values of the other connected devices are cleared (not with add).
  • The game averages one axis action over all devices: merge reports such an axis; merge-overwrite clears it on the others.
  • A device without a section is skipped ("start the game once with this device connected").
  • Never touched: the keyboard, menu keys (UI_*), combinations JoyPro does not read, sections of devices that are not connected, --ignore-device(s), the --vjoy-tunnel device; comments, order, encoding and line ends.
  • Safety: refused while Ace7Game or Ace7Game-Win64-Shipping runs; backed up first (undo: engine backups list); the profile is kept as "Before export to ACE COMBAT 7: Skies Unknown". --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 ac7 paths lists first.
  • After a real run: Input.ini.joypro-meta.json, the watcher's fingerprint, the export marks (engine export-marks list).
  • Related: engine ac7 import; game page ace-combat.

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 ac7 export --mode clean
engine ac7 export --mode add
engine ac7 export --mode merge
engine ac7 export --mode merge-overwrite

In the game Writes into ACE COMBAT 7: Skies Unknown'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%\BANDAI NAMCO Entertainment\ACE COMBAT 7\Config\Input.ini (ini, one section per device model). ACE COMBAT 7: Skies Unknown details · what each mode changes

Example

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

#engine ac7 refresh-db

written
engine ac7 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 ACE COMBAT 7 command list from your Input.ini: every Flight_* key of the device sections. Start the game once with your devices connected first. Update on the ACE COMBAT 7 card of the Start page runs it.

engine ac7 refresh-db --text
Advanced
  • Reads the file engine ac7 paths lists; a path (positional or --path) may name another Input.ini, a folder means the default file.
  • The list is rebuilt from the file. --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 <file>. and Actions: <old> -> <new>, Warnings, Errors), or a text report with --text.
  • Exit code 0; 1 when nothing could be read: Input.ini not found (<path>): start ACE COMBAT 7 once with your devices connected. or <path> has no device section with Flight_ binds yet: ...; the list stays unchanged.
  • Writes %LOCALAPPDATA%\JoyPro2\GameData\DB\AceCombat7\actions.tsv.
  • Related: engine ac7 catalog, engine ac8 refresh-db; game page ace-combat.

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 ac7 refresh-db --text