JoyPro2 Discord GitHub
Engine (CLI)

engine binds

Show:

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

#engine binds list

written
engine binds list [filter]
For beginners

Lists the binds of the profile: for each relation its device, input, modifiers and axis settings. An optional text filters the list. The Binds page runs it to build its cards (Refresh binds under More, and after every change).

engine binds list "Warthog" --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • The filter (all words after list, joined) matches, case-insensitive and as a part of the text: the relation name, the device, the button or axis, the device alias, device::input and the modifiers.
  • Sorted by relation name. Relations without a bind are not listed (engine binds show tells you more).
  • Read-only.
Technical internals
  • Output: the binds document as JSON (FormatVersion, GeneratedUtc, Binds), or a text list with --text; exit code 0.
  • binds list without an action is the same as binds.
  • Related: engine binds show, engine binds export (the same document into a file), engine binds edit.

What it does Lists bind entries (hardware mapping layer).

Used by the GUI Profile bar: Reload · Profile bar: Merge · Start: Import now · Start: Import · Start: Import · Start: Import · Start: Import · Relations: Duplicate · Relations: Duplicate without bind · Relations: Run Mass Operation · Relations: Merge Profile · Relations: Apply selected

Example

engine binds list 'Throttle' --text

#engine binds show

written
engine binds show <bind-or-relation>
For beginners

Shows one bind in full: device, input, modifiers, axis settings and the relation with its actions. Show selected in output under More on the Binds page runs it and prints the answer into the Output panel.

engine binds show "Gear Up/Down" --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • The selector is a relation name, a bound input (JOY_BTN22) or device::input; a part of a relation name works when only one bound relation contains it.
  • Read-only.
Technical internals
  • Output: Bind and Relation as JSON, or text; exit code 0.
  • Failures (exit 1): binds show requires a bind name or relation name., No bind matched query: ..., Ambiguous bind query '...'. Matches: ..., Bind not found for relation: ... (the relation has no bind).
  • Related: engine binds list, engine binds set.

What it does Shows one bind in detail.

Used by the GUI Binds: Show selected in output · Binds: Clear Input · Binds: Clear Modifiers · Binds: Make main · Binds: Attach Selected To Bind · Binds: Detach Selected From Bind · Binds: Create Modifier · Modifiers: Create Modifier

Example

engine binds show 'Gear Toggle' --text

#engine binds set

written
engine binds set <bind-or-relation> [--device <name>] [--input <value>] [--format dcs|il2] [--modifier <name>] [--clear-modifiers] [--clear-input] [--inverted true|false] [--slider true|false] [--curvature <csv>] [--deadzone <value>] [--saturation-x <value>] [--saturation-y <value>] [--double-tap true|false]
For beginners

Puts a relation on a button or axis, or changes its modifiers and axis settings. It creates the bind when the relation has none. The Binds page runs it for Record input and Set Bind, the Layout page for Bind to this input, and the virtual function editor for Bind relation.

engine binds set "Gear Up/Down" --device "Throttle - HOTAS Warthog" --input JOY_BTN22 --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file"
Advanced
Option Effect on the bind
--device <name> the device the input belongs to
--input <token> the input; an axis relation stores it as its axis, a button relation as its button (the other field is emptied)
--format dcs|il2 how --input is written: dcs (default, JOY_BTN1) or il2 (joy0_b0, converted to the DCS form); needs --input
--modifier <name> (also --mod, --reformer; repeatable) replaces the bind's whole modifier list
--clear-modifiers empties the modifier list (ignored when --modifier is given)
--clear-input empties the input, the bind and its settings stay
--inverted, --slider true|false axis invert and one-sided axis
--curvature <csv>, --deadzone, --saturation-x, --saturation-y <n> the bind's own (base) axis curve
--double-tap true|false the double-tap flag (kept in the profile)
  • The axis options are refused on a button relation. At least one option is needed.
  • Only the profile changes; the game gets the bind at the next export.
Technical internals
  • Output: the bind after the change, as engine binds show prints it; exit code 0.
  • Failures (exit 1): binds set requires at least one change option (e.g. --device, --input, --curvature, --inverted)., --format requires --input., Invalid --deadzone value '...', Axis tuning options (...) can only be set on axis relations., No relation/bind matched query: ..., Unknown binds set argument(s): ....
  • With --profile the profile is saved afterwards as a new history version (one undo step).
  • Per-game and per-aircraft curves: engine binds tuning set. Related: engine binds clear, engine binds modifier add.

What it does Creates or updates one relation bind (device/input/modifiers and optional tuning values).

OptionValuesMeaning
--device<name>Include one device per flag. Example: --device LEFT VPC Throttle.
--input<value>Input token. Example: --input JOY_BTN1 or --input joy0_b0.
--formatdcs il2Format selector. Example values: dcs/il2 for binds unbind, rl/json for relations mass export.
--modifier<name>Modifier key token. Example: --modifier LShift.
--clear-modifiersswitch (no value)Clears all modifiers from the selected bind.
--clear-inputswitch (no value)Clears bind input token(s) (button/axis) while keeping the bind object.
--invertedtrue falseSet axis inversion flag on selected bind (true/false).
--slidertrue falseSet axis slider flag on selected bind (true/false).
--curvature<csv>Set curvature list. Example: --curvature 0.1,0.2,0.3.
--deadzone<value>Set deadzone numeric value. Example: --deadzone 0.15.
--saturation-x<value>Set saturation X numeric value. Example: --saturation-x 0.9.
--saturation-y<value>Set saturation Y numeric value. Example: --saturation-y 0.8.
--double-taptrue falseSet double-tap behavior flag (true/false).
Every value as a command line
engine binds set --format dcs
engine binds set --format il2
engine binds set --inverted true
engine binds set --inverted false
engine binds set --slider true
engine binds set --slider false
engine binds set --double-tap true
engine binds set --double-tap false

Used by the GUI Binds: Bind here · Binds: Free · Binds: Record input · Binds: Set Bind · Layout: Bind to this input · Layout: Free

Example

engine binds set 'Gear Toggle' --device 'VKB Gladiator NXT' --input JOY_BTN1 --text
engine binds set 'Pitch Axis' --input JOY_Y --inverted true --curvature 0.1,0.2 --deadzone 0.05 --saturation-x 0.9 --saturation-y 0.9 --text
How the options interact
  • If relation has no bind yet, this command creates one.
  • Axis tuning options apply only to axis relations.
  • --format is only meaningful when --input is provided.

#engine binds clear

written
engine binds clear <bind-or-relation> [--input-only]
For beginners

Takes the bind off a relation: by default the whole bind (input, modifiers, axis settings), with --input-only just the input. The relation and its actions stay. Clear Bind on the Binds page runs the full clear, Clear Input the --input-only form; the Layout page's free-marker button also uses it.

engine binds clear "Gear Up/Down" --input-only --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • Default: the bind is removed from the relation. --input-only: the button and axis are emptied, modifiers and the curve stay on the relation for the next input.
  • A relation without a bind is no error; the result says HadBind: false.
  • After the next export the relation is on no button in the game.
Technical internals
  • Output: Relation, InputOnly, HadBind, ClearedInput, RemovedBind as JSON or text; exit code 0.
  • Failures (exit 1): binds clear requires: <bind-or-relation> [--input-only]., Unknown binds clear argument(s): ..., Relation not found: ....
  • One undo step with --profile. Related: engine binds unbind (free an input in every relation), engine binds set.

What it does Unbinds one relation (remove bind entirely or clear only input token).

OptionValuesMeaning
--input-onlyswitch (no value)For binds clear, clear only input tokens instead of removing whole bind.

Used by the GUI Binds: Bind here · Binds: Free · Binds: Clear Input · Binds: Clear Bind · Layout: Bind to this input · Layout: Free

Example

engine binds clear 'Gear Toggle' --text
engine binds clear 'Gear Toggle' --input-only --text
How the options interact
  • Default behavior removes the entire bind from that relation.
  • Use --input-only to keep bind metadata and clear only button/axis input.

#engine binds extra list

written
engine binds extra list <relation>

Changes not with --multi-bind off: the relation's inputs numbered as the pages show them, 1 = the main bind, 2.. = the other inputs, each with its own device, input, modifiers and axis tuning

For beginners

Shows every input of a relation, numbered as the Binds page's More inputs panel shows them: 1 is the main bind, 2 and up are the other inputs. Each line names the device, the input and the modifiers; an axis also shows its tuning. It works with --multi-bind off too.

engine binds extra list "Weapon Release" --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced

What it does Changes not with --multi-bind off: the relation's inputs numbered as the pages show them, 1 = the main bind, 2.. = the other inputs, each with its own device, input, modifiers and axis tuning.

Example

engine binds extra list <relation> --text

#engine binds extra add

written
engine binds extra add <relation> --device <name> --input <value> [--format dcs|il2] [--modifier <name>]... [--copy-tuning true|false] [--inverted true|false] [--slider true|false] [--deadzone <v>] [--saturation-x <v>] [--saturation-y <v>] [--curvature <v>]

Another input that does the same; an axis starts with the main bind's tuning unless --copy-tuning false; a relation without a bind gets it as its bind

For beginners

One more input for a relation, with its own device, modifiers and axis curve. The Binds page's More inputs panel runs it.

engine binds extra add "Weapon Release" --device "MOZA AB9 Base {...}" --input JOY_BTN2 --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • Inputs are numbered as the pages show them: 1 = the main bind, 2.. = the others; engine binds extra list, binds extra set <relation> <n>, binds extra remove <relation> <n>|--all, binds extra move <relation> <n> --to <m> (--to 1 makes it the main bind) or --to-relation <name>.
  • An axis starts with the main bind's tuning (--copy-tuning false: neutral); binds tuning set <relation> --bind <n> tunes one input per game or aircraft.
  • On by default since 2.7.0 (experimental before, behind --multi-bind on). With the global option --multi-bind off (or JOYPRO_MULTI_BIND=0) changes are refused for that call; list and remove always work. Exports and the table per game: docs/multi-bind.md.

What it does Another input that does the same; an axis starts with the main bind's tuning unless --copy-tuning false; a relation without a bind gets it as its bind.

OptionValuesMeaning
--device<name>Include one device per flag. Example: --device LEFT VPC Throttle.
--input<value>Input token. Example: --input JOY_BTN1 or --input joy0_b0.
--formatdcs il2Format selector. Example values: dcs/il2 for binds unbind, rl/json for relations mass export.
--modifier<name>Modifier key token. Example: --modifier LShift.
--copy-tuningtrue false
--invertedtrue falseSet axis inversion flag on selected bind (true/false).
--slidertrue falseSet axis slider flag on selected bind (true/false).
--deadzone<v>Set deadzone numeric value. Example: --deadzone 0.15.
--saturation-x<v>Set saturation X numeric value. Example: --saturation-x 0.9.
--saturation-y<v>Set saturation Y numeric value. Example: --saturation-y 0.8.
--curvature<v>Set curvature list. Example: --curvature 0.1,0.2,0.3.
Every value as a command line
engine binds extra add --format dcs
engine binds extra add --format il2
engine binds extra add --copy-tuning true
engine binds extra add --copy-tuning false
engine binds extra add --inverted true
engine binds extra add --inverted false
engine binds extra add --slider true
engine binds extra add --slider false

Used by the GUI Binds: Record another input · Binds: Add the input picked by hand

Example

engine binds extra add <relation> --device <name> --input <value> --text

#engine binds extra set

written
engine binds extra set <relation> <n> [--device <name>] [--input <value>] [--format dcs|il2] [--modifier <name>]... [--clear-modifiers] [--inverted true|false] [--slider true|false] [--deadzone <v>] [--saturation-x <v>] [--saturation-y <v>] [--curvature <v>]

Changes input n (2 or more); scoped axis tuning of it: binds tuning set <relation> --bind <n>

For beginners

Changes input <n> (2 or more) of a relation: its device, input, modifiers or axis tuning. The main bind (1) is changed with engine binds set.

engine binds extra set "Weapon Release" 2 --input JOY_BTN3 --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • --modifier can be given several times; --clear-modifiers takes them all off first.
  • Tuning for one game or aircraft only: binds tuning set <relation> --bind <n> --scope ....
  • A warning says when another relation uses the same input; the change is made anyway.

What it does Changes input n (2 or more); scoped axis tuning of it: binds tuning set <relation> --bind <n>.

OptionValuesMeaning
--device<name>Include one device per flag. Example: --device LEFT VPC Throttle.
--input<value>Input token. Example: --input JOY_BTN1 or --input joy0_b0.
--formatdcs il2Format selector. Example values: dcs/il2 for binds unbind, rl/json for relations mass export.
--modifier<name>Modifier key token. Example: --modifier LShift.
--clear-modifiersswitch (no value)Clears all modifiers from the selected bind.
--invertedtrue falseSet axis inversion flag on selected bind (true/false).
--slidertrue falseSet axis slider flag on selected bind (true/false).
--deadzone<v>Set deadzone numeric value. Example: --deadzone 0.15.
--saturation-x<v>Set saturation X numeric value. Example: --saturation-x 0.9.
--saturation-y<v>Set saturation Y numeric value. Example: --saturation-y 0.8.
--curvature<v>Set curvature list. Example: --curvature 0.1,0.2,0.3.
Every value as a command line
engine binds extra set --format dcs
engine binds extra set --format il2
engine binds extra set --inverted true
engine binds extra set --inverted false
engine binds extra set --slider true
engine binds extra set --slider false

Example

engine binds extra set <relation> <n> --text

#engine binds extra remove

written
engine binds extra remove <relation> <n>|--all

Works also with --multi-bind off

For beginners

Takes input <n> (2 or more) out of a relation, or all its other inputs with --all; the main bind stays. Remove in the Binds page's More inputs panel does the same. It works with --multi-bind off too.

engine binds extra remove "Weapon Release" --all --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text

What it does Works also with --multi-bind off.

OptionValuesMeaning
--allswitch (no value)Apply operation to all matches (or select all relations/devices where supported).

Used by the GUI Binds: Remove

Example

engine binds extra remove <relation> <n>|--all --text

#engine binds extra move

written
engine binds extra move <relation> <n> --to <m> | --to-relation <name>

--to 1 makes it the main bind and the main bind takes its place; --to-relation moves the input to another relation of the same kind

For beginners

--to <m> changes the order of a relation's inputs; --to 1 makes input <n> the main bind, and the old main bind takes its number (Make main on the Binds page). --to-relation <name> moves the input to another relation.

engine binds extra move "Weapon Release" 2 --to 1 --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • --to-relation needs a relation of the same kind (button to button, axis to axis). A relation without a bind gets the input as its main bind, otherwise as its next input.

What it does --to 1 makes it the main bind and the main bind takes its place; --to-relation moves the input to another relation of the same kind.

OptionValuesMeaning
--to<m>The target: the new position (relations item move), the file or folder to write (telemetry export), the folder to unpack into (support unpack). Example: C:\Cases\case1.
--to-relation<name>

Used by the GUI Binds: Make main

Example

engine binds extra move <relation> <n> --to <m> --text

#engine binds modifier list

written
engine binds modifier list [bind-or-relation]
For beginners

Lists modifiers (shift buttons held together with a bind's button): without a selector every modifier name with the relations that use it, with a selector those of one bind. The Binds and Modifiers pages run it when they refresh their modifier lists.

engine binds modifier list --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • Global: Modifiers (names, sorted) and Entries (name, relations, BindCount).
  • One bind: Modifiers (names) and Reformers (the stored form with the modifier's device and input).
  • Read-only.
Technical internals

What it does Lists modifiers on one bind, or all modifiers across all binds.

Used by the GUI Profile bar: Reload · Profile bar: Merge · Start: Import now · Start: Import · Start: Import · Start: Import · Start: Import · Relations: Merge Profile · Binds: Merge Profile · Binds: Apply · Binds: Clear Input · Binds: Clear Modifiers

Example

engine binds modifier list --text
engine binds modifier list 'Gear Toggle' --text
How the options interact
  • Without a bind/relation selector, lists all modifier names and usage counts.

#engine binds modifier add

written
engine binds modifier add <bind-or-relation> <mod1> [mod2] [...]
For beginners

Adds one or more modifiers to a bind, so its button only does the relation while they are held. Attach Selected To Bind on the Binds page and Create Modifier (with a relation picked) run it.

engine binds modifier add "Gear Up/Down" LShift --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • Modifiers the bind already has (any case) are not added twice.
  • The relation needs a bind (engine binds set first).
  • The game gets the modifier combination at the next export (DCS shows it in its modifier list).
Technical internals

What it does Adds one or more modifiers to a bind.

Used by the GUI Binds: Attach Selected To Bind · Binds: Create Modifier · Modifiers: Create Modifier

Example

engine binds modifier add 'Gear Toggle' LShift RCtrl --text

#engine binds modifier remove

written
engine binds modifier remove <bind-or-relation> <mod1> [mod2] [...] [--all]
For beginners

Takes modifiers off a bind, or all of them with --all; the bind and its input stay. Detach Selected From Bind and Clear Modifiers (--all) on the Binds page run it, and Delete Selected on the Modifiers page runs it per relation.

engine binds modifier remove "Gear Up/Down" --all --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • A name removes every stored form of that modifier on the bind (any device and input).
  • After the next export the button works without holding the shift button; binds that only differed by the modifier now share one button (the Check shows it).
Technical internals
  • Output: the bind after the change; exit code 0.
  • Failures (exit 1): binds modifier remove requires at least one modifier or --all., Bind not found for relation: ....
  • One undo step with --profile. Related: engine binds modifier add.

What it does Removes one or more modifiers (or all) from a bind.

OptionValuesMeaning
--allswitch (no value)Apply operation to all matches (or select all relations/devices where supported).

Used by the GUI Binds: Clear Modifiers · Binds: Detach Selected From Bind · Binds: Delete Selected (Profile-Wide) · Modifiers: Delete Selected (Profile-Wide)

Example

engine binds modifier remove 'Gear Toggle' LShift --text
engine binds modifier remove 'Gear Toggle' --all --text
How the options interact
  • Use --all to clear all values instead of specifying individual names.

#engine binds modifier rename

written
engine binds modifier rename <old-modifier> <new-modifier> [bind-or-relation]
For beginners

Gives a modifier a new name in every bind that uses it, or only in one bind when you name it. Rename (From / To) on the Modifiers page runs it.

engine binds modifier rename LAlt "Pinky Shift" --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • Only the name changes; the modifier's device and input stay. A bind that ends up with the same modifier twice keeps one. A relation's other inputs (engine binds extra list) are renamed with it.
  • The new name shows in the game after the next export (DCS's modifier list).
Technical internals
  • Output: Scope, Relation, OldName, NewName, UpdatedRelations, UpdatedCount; exit code 0.
  • Failures (exit 1): binds modifier rename requires different old/new names., Modifier not found: ..., Bind not found for relation: ....
  • One undo step with --profile. Related: engine binds modifier list.

What it does Renames a modifier across all binds, or only one selected bind.

Used by the GUI Modifiers: Rename

Example

engine binds modifier rename 'LAlt' 'LAlt_Hold' --text
engine binds modifier rename 'LAlt' 'LAlt_Hold' 'Gear Toggle' --text
How the options interact
  • If you omit bind/relation selector, rename is applied across all binds.

#engine binds tuning models

written
engine binds tuning models

The axis response models: DCS, IL-2 Great Battles, IL-2 Korea, the per-game models (Arma, Elite, BMS, FSX, IL-2 1946, Cliffs of Dover, MSFS, Project Wingman, Star Citizen, VTOL VR, WARDOGS, War Thunder, X-Plane) and the generic one, with their parameters

For beginners

Lists the axis response models JoyPro knows (how a game turns your stick position into what it uses) with their parameters. The parameter keys are what binds tuning set --param takes.

engine binds tuning models --text
Advanced
  • dcs: dead zone, saturation X/Y, curvature (exponential) or an 11-point user curve, slider, invert. Also il2, il2korea, and generic for games without a model of their own (invert, dead zone, saturation).
  • The games' own models: Arma 2 / Arma 2 OA, Arma 3, Arma Reforger, Elite Dangerous, Falcon BMS, FSX / Prepar3D, IL-2 1946, IL-2 Cliffs of Dover (also Blitz), MSFS 2020 / 2024, Project Wingman, Star Citizen, VTOL VR, Wardogs, War Thunder, X-Plane 11 / 12.
  • Per parameter: key, label, kind (number or switch) and the range of a number. A model whose game takes a curve with free stops also shows the --curve-points line.
  • Read-only; no profile needed. With binds tuning alone it lists the models too.
Technical internals

What it does Lists the axis response models and their parameters: DCS, IL-2 Great Battles, IL-2 Korea, the per-game models (Arma 2 / 3 / Reforger, Elite, BMS, FSX, IL-2 1946, Cliffs of Dover, MSFS, Project Wingman, Star Citizen, VTOL VR, WARDOGS, War Thunder, X-Plane) and the generic one.

Example

engine binds tuning models --text

#engine binds tuning show

written
engine binds tuning show <bind-or-relation> [--bind <n>] [--game <game>] [--plane <plane>]

Every scope; per game and DCS aircraft of the relation the scope its curve comes from

For beginners

Shows an axis relation's curves: the base curve every game gets and each scope with its own curve (an aircraft, a game, a game family), and for every game and DCS aircraft of the relation which of them its curve comes from. With --game (and --plane) it also gives the curve that game uses. The axis response panel on the Binds page runs it to fill its Applies to list ("own curve", "same as ...", "uses DCS") and to load the curve shown (Reload).

engine binds tuning show "Pitch" --game DCS --plane F-16C_50 --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • The resolved curve: the most specific stored scope (aircraft, game, family), else the base; for a game whose curve differs from DCS's it is fitted to the base curve; in detent mode the detent curve.
  • Values are written as inv=0;sl=0;dz=0.05;sx=1;sy=1;cv=0.2 plus the game's own parameters.
  • Per game / DCS aircraft (Uses, text: "Curve per game and aircraft"): the scope its curve comes from before detent mode, whether it is fitted to the base, and whether detent mode bends it. Only DCS is listed per aircraft: it is the game whose curves are written per aircraft.
  • Read-only. Axis relations only.
Technical internals

What it does Shows the axis tuning of a bind per scope (base, game, plane, family) and, with --game, what that game (and plane) uses.

OptionValuesMeaning
--bind<n>
--game<game>Game filter value. Example: DCS or IL2Game.
--plane<plane>Include one plane/module per flag. Example: --plane A-10C_2.

Used by the GUI Binds: Reload · Binds: SaveAxisTuningCommand · Binds: ClearAxisTuningCommand · Binds: Save calibration · Binds: Set · Binds: Game data

Example

engine binds tuning show 'Pitch Axis' --game IL2Korea --text

#engine binds tuning set

written
engine binds tuning set <bind-or-relation> [--bind <n>] --scope base|game:<game>|plane:<game>:<plane>|family:<family> [--scope <another>]... [--clear-scope <scope>]... [--param <name>=<value>]... [--inverted true|false] [--slider true|false] [--deadzone <value>] [--saturation-x <value>] [--saturation-y <value>] [--curvature <csv>] [--curve-points <x:y,...>|none]
For beginners

Stores an axis curve for one scope or several at once: the base (every game), a game, an aircraft of a game or a game family. Several scopes (--scope repeated) get the same values in one run, so one undo takes them all back. Save in the axis response panel on the Binds page runs it for the ticked rows.

engine binds tuning set "Pitch" --scope plane:DCS:F-16C_50 --deadzone 0.03 --curvature 0.2 --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file"
engine binds tuning set "Collective" --scope plane:DCS:AH-64D_BLK_II_CPG --scope plane:DCS:AH-64D_BLK_II_PLT --scope plane:DCS:Ka-50_3 --deadzone 0.12 --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file"
engine binds tuning set "Collective" --scope game:DCS --clear-scope plane:DCS:Ka-50_3 --deadzone 0.07 --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file"
Advanced
Option Values
--scope (required, repeatable) base, game:<game>, plane:<game>:<plane>, family:<family>; each gets the values
--clear-scope (repeatable) a scope whose own curve is removed in the same run (not base, not one of the --scopes)
--inverted, --slider true / false
--deadzone, --saturation-x, --saturation-y 0..1
--curvature one value -1..1, or 11 user-curve points 0..1
--param <name>=<value> a parameter of the game's own curve model, checked against its range (engine binds tuning models)
--curve-points x:y,... | none a curve with free stops in 0..1, x increasing, at least two points
  • A scope without values of its own starts from what it uses now (game and aircraft scopes) or from the base; with several scopes each starts from its own and gets the options given (all values given: all the same).
  • Nothing is stored unless the options are valid for every scope.
  • Curve points stay until dead zone, saturation or curvature change without new points.
  • The base scope writes the bind's own values: invert, slider, dead zone, saturation and curvature. --param and --curve-points are not stored there: the result shows only the stored values and a line "Not set: ... do not apply to the base scope"; put them on a game, aircraft or family scope.
  • Games that keep some values once per device axis (MSFS) get a warning when another relation on the same axis has other values.
  • The next export writes the curve into the game's axis settings for that aircraft, game or family.
Technical internals
  • Output: Relation and Message (Set <scope>: <values> per scope, Cleared <scope>, ... for --clear-scope, for the base scope a Not set: ... line when --param or --curve-points were given, plus warnings); exit code 0.
  • Failures (exit 1): binds tuning set requires --scope (...), Invalid scope '...', Invalid --clear-scope '...', '...' is both set (--scope) and cleared (--clear-scope)., Relation '...' has no bind; bind an axis first., --deadzone must be 0..1., Unknown model parameter '...'. See: engine binds tuning models., --curve-points: x must increase from point to point.
  • Stored per bind in TuningOverrides (scope -> values). One undo step with --profile, however many scopes.
  • Related: engine binds tuning show, engine binds tuning clear, engine binds set (base values only).

What it does Sets axis tuning for one scope: base (all games), game:<game>, plane:<game>:<plane> or family:<family>. A game without its own tuning gets the base curve fitted to its model.

OptionValuesMeaning
--bind<n>
--scopebase gameAxis tuning scope: base, game:<game>, plane:<game>:<plane> or family:<family>. Example: --scope game:IL2Korea.
--clear-scope<scope>
--param<name>A model parameter as name=value, repeatable; game, plane and family scopes only (the base scope does not keep it). Example: --param sensitivity=22.
--invertedtrue falseSet axis inversion flag on selected bind (true/false).
--slidertrue falseSet axis slider flag on selected bind (true/false).
--deadzone<value>Set deadzone numeric value. Example: --deadzone 0.15.
--saturation-x<value>Set saturation X numeric value. Example: --saturation-x 0.9.
--saturation-y<value>Set saturation Y numeric value. Example: --saturation-y 0.8.
--curvature<csv>Set curvature list. Example: --curvature 0.1,0.2,0.3.
--curve-points<x:y,...>Free curve points x:y in 0..1 (or none); game, plane and family scopes only. Example: --curve-points 0:0,0.4:0.3,1:1.
Every value as a command line
engine binds tuning set --scope base
engine binds tuning set --scope game
engine binds tuning set --inverted true
engine binds tuning set --inverted false
engine binds tuning set --slider true
engine binds tuning set --slider false

Used by the GUI Binds: SaveAxisTuningCommand · Binds: Copy

Example

engine binds tuning set 'Pitch Axis' --scope game:IL2Korea --param sensitivity=22 --param deadZone0=3 --text
engine binds tuning set 'Pitch Axis' --scope plane:DCS:F-16C_50 --curvature 0.2 --deadzone 0.02 --text
How the options interact
  • --scope base keeps invert, slider, dead zone, saturation and curvature; --param and --curve-points are not stored there (the result says so): set them on a game, plane or family scope.

#engine binds tuning clear

written
engine binds tuning clear <bind-or-relation> [--bind <n>] --scope game:<game>|plane:<game>:<plane>|family:<family> [--scope <another>]...

Several scopes: one change, one undo step

For beginners

Removes the own curve of one scope or several (--scope repeated, one undo step), so that game, aircraft or family uses the next wider curve again (in the end the base). Use the game's curve again in the axis response panel runs it for the ticked rows.

engine binds tuning clear "Pitch" --scope plane:DCS:F-16C_50 --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
engine binds tuning clear "Collective" --scope plane:DCS:AH-64D_BLK_II_CPG --scope plane:DCS:AH-64D_BLK_II_PLT --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • Scopes: game:<game>, plane:<game>:<plane>, family:<family>. The base cannot be cleared; set its values with engine binds tuning set.
  • A scope without own values is no error (No tuning for <scope>.).
  • The next export writes the inherited curve into the game.
Technical internals
  • Output: Relation and Message (Cleared <scope>, .... and No tuning for <scope>, ....); exit code 0.
  • Failures (exit 1): The base tuning cannot be cleared; set its values instead. (also among several), Invalid scope '...', --clear-scope is an option of binds tuning set; binds tuning clear takes --scope., Relation '...' has no bind; bind an axis first.
  • One undo step with --profile. Related: engine binds tuning show.

What it does Removes the tuning of one scope; the scope inherits again.

OptionValuesMeaning
--bind<n>
--scopeswitch (no value)Axis tuning scope: base, game:<game>, plane:<game>:<plane> or family:<family>. Example: --scope game:IL2Korea.

Used by the GUI Binds: ClearAxisTuningCommand

Example

engine binds tuning clear 'Pitch Axis' --scope game:IL2Korea --text

#engine binds tuning preview

written
engine binds tuning preview <bind-or-relation> --game <game> [--plane <plane>] [--points <n>]
For beginners

Prints the response curve a game (and an aircraft) applies to an axis relation: each stick position from -1 to 1 and what the game makes of it. Use it to compare scopes before an export.

engine binds tuning preview "Pitch" --game DCS --plane F-16C_50 --points 11 --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • --game (required) and --plane: the curve engine binds tuning show resolves for them (the aircraft, game or family scope, else the base; fitted to the base curve for a game with another model; the detent curve in detent mode).
  • --points <n>: 2..1001 samples spread evenly from -1 to 1 (default 21).
  • Read-only. Axis relations only.
Technical internals
  • Output: JSON Relation, Game, Plane, Model, Source, Fitted, Tuning, Points ([x, y] pairs), or text (Model: ..., Tuning: ..., then lines like +0.500 -> +0.353553); exit code 0.
  • Failures (exit 1): binds tuning preview requires --game., --points must be 2..1001., Axis tuning is only for axis relations; '...' is a button relation., binds tuning preview requires a relation or bind name.
  • Reference: axis-curves. Related: engine binds tuning models.

What it does Prints the response curve a game (and plane) applies to the bind: stick position -> what the game uses.

OptionValuesMeaning
--game<game>Game filter value. Example: DCS or IL2Game.
--plane<plane>Include one plane/module per flag. Example: --plane A-10C_2.
--points<n>Number of preview samples from -1 to 1. Example: --points 21.

Example

engine binds tuning preview 'Pitch Axis' --game DCS --plane F-16C_50 --points 11 --text

#engine binds detent show

written
engine binds detent show <bind-or-relation>

Detent mode: settings, the device axis calibration, the aircraft grouped by afterburner start, per game the curve it gets and how exactly

For beginners

Shows a throttle relation's detent mode: on or off, the device axis calibration, the aircraft grouped by where their afterburner starts, and per game the curve it gets. Reload in the Detent mode panel on the Binds page runs it.

engine binds detent show "Throttle" --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • Settings: on/off, aircraft without afterburner (full power at the detent or linear), unknown aircraft, margin.
  • Per aircraft: the afterburner start and where it comes from (JoyPro's gate data, your own value), its confidence; per game: the fit method, its error and the curve.
  • Warnings: no device axis bound, the axis not calibrated, the relation not a one-sided axis.
  • Read-only. Axis relations only.
Technical internals

What it does Detent mode of a throttle relation: its settings, the calibration of the bound device axis, the aircraft grouped by where their afterburner starts (game data or the relation's own value) and per game the curve it gets and how exactly the game expresses it.

Used by the GUI Binds: Reload · Binds: Merge · Binds: Undo merge · Binds: Set · Binds: Game data

Example

engine binds detent show 'Throttle' --text

#engine binds detent set

written
engine binds detent set <bind-or-relation> [--on|--off] [--no-ab full|linear] [--unknown full|linear] [--margin <0..0.1>] [--target <game>:<plane>=ab:<0..1>|full|linear|default]...
For beginners

Switches detent mode on or off for a throttle relation and sets its options. In detent mode one throttle relation serves every aircraft: the curve is bent per aircraft so your device's detent is where that aircraft's afterburner starts. The Detent mode on tick, the second tick (aircraft without afterburner) and a group's Set / Game data run it.

engine binds detent set "Throttle" --on --no-ab full --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • --on / --off (not both).
  • --no-ab full|linear: aircraft without afterburner get full power at the detent, or the relation's curve.
  • --unknown full|linear: the same for aircraft without gate data.
  • --margin <0..0.1>: share of the game's throttle.
  • --target <game>:<plane>=ab:<0..1>[/idle:<0..1>]|full|linear|default (repeatable): your own afterburner start for an aircraft; default goes back to the gate data.
  • It needs a bound device axis. Without a calibration it says so: it takes effect after engine binds detent calibrate.
Technical internals
  • Output: the detent view of engine binds detent show with a Message; exit code 0.
  • Failures (exit 1): Relation '...' has no device axis bound; bind the throttle axis first., Use --on or --off, not both., --margin must be 0..0.1 (share of the game's throttle)., --target takes <game>:<plane>=...
  • Stored on the bind. One undo step with --profile.

What it does Switches detent mode on or off, sets what aircraft without afterburner get (full power at the detent or the relation's curve), the margin below the afterburner, and an aircraft's own afterburner start (--target <game>:<plane>=ab:0.78|full|linear|default).

OptionValuesMeaning
--onswitch (no value)
--offswitch (no value)
--no-abfull linear
--unknownfull linear
--margin<0..0.1>
--target<game>
Every value as a command line
engine binds detent set --no-ab full
engine binds detent set --no-ab linear
engine binds detent set --unknown full
engine binds detent set --unknown linear

Used by the GUI Binds: Set · Binds: Game data

Example

engine binds detent set 'Throttle' --on --no-ab full --text
engine binds detent set 'Throttle' --target DCS:F-16C_50=ab:0.775 --target DCS:A-10C=full --text

#engine binds detent calibrate

written
engine binds detent calibrate <bind-or-relation> --idle <0..1> --detent <0..1> [--full <0..1>|none] [--cutoff <0..1>|none] [--source wizard|manual]

Raw axis positions of the bound device axis

For beginners

Stores where your throttle axis is at idle and at the afterburner detent (and optionally at full and behind idle), as raw axis positions. Save calibration at the end of the Calibrate detent... wizard runs it.

engine binds detent calibrate "Throttle" --idle 0.02 --detent 0.78 --full 0.99 --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • --idle, --detent (required), --full, --cutoff (0..1 or none): raw positions of the bound device axis.
  • --source (default manual; the GUI passes wizard) and the date are stored with it.
  • Checks: the detent at least 2 % of the travel away from idle, full beyond the detent, the cut-off behind idle.
  • Stored per device axis, so every throttle relation on that axis uses it.
Technical internals
  • Output: the detent view with Calibrated <device axis>: idle at ..., detent at ... of the travel.; exit code 0.
  • Failures (exit 1): --idle must be the raw axis position 0..1 at idle., --detent must be ..., The detent must be at least 2 % of the travel away from idle., Full must be beyond the detent., The cut-off must be behind idle.
  • One undo step with --profile. Related: engine binds detent uncalibrate, engine binds detent set.

What it does Stores where the bound device axis has its idle, afterburner detent, full and cut-off positions (raw axis 0..1; the GUI's wizard reads them live). Every throttle relation on that axis uses it.

OptionValuesMeaning
--idle<0..1>
--detent<0..1>
--full<0..1>
--cutoff<0..1>
--sourcewizard manual
Every value as a command line
engine binds detent calibrate --source wizard
engine binds detent calibrate --source manual

Used by the GUI Binds: Save calibration

Example

engine binds detent calibrate 'Throttle' --idle 0.02 --detent 0.79 --full none --cutoff none --source manual --text

#engine binds detent uncalibrate

written
engine binds detent uncalibrate <bind-or-relation>
For beginners

Removes the stored detent calibration of the throttle axis a relation is bound to. Detent mode then has nothing to bend the curve to until you calibrate the axis again.

engine binds detent uncalibrate "Throttle" --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • The calibration belongs to the device axis, not to the relation: every throttle relation on that axis loses it.
  • Detent mode itself, its options and your per-aircraft targets stay.
  • An axis without a calibration is no error (No calibration stored.).
  • It needs a bound device axis. Axis relations only.
Technical internals
  • Output: the detent view of engine binds detent show with Calibration of <device axis> removed.; exit code 0.
  • Failures (exit 1): Relation '...' has no device axis bound; bind the throttle axis first., Detent mode is only for axis relations; '...' is a button relation., Unknown binds detent uncalibrate argument(s): ...
  • One undo step with --profile. Related: engine binds detent calibrate.

What it does Removes the detent calibration of the bound device axis.

Example

engine binds detent uncalibrate 'Throttle' --text

#engine binds detent gates

written
engine binds detent gates [--game <game>] [--plane <plane>]

The shipped throttle gate data: afterburner start per aircraft, source, confidence

For beginners

Lists JoyPro's throttle gate data: per aircraft where its afterburner starts (and where idle is) on the game's throttle axis, with source and confidence. Detent mode uses it for every aircraft you did not set yourself.

engine binds detent gates --game DCS --text
Advanced
  • --game <id>: only that game (its id, e.g. DCS). --plane <name>: only that aircraft (its id or one of its aliases). Without them: every aircraft of the data.
  • Per aircraft: no afterburner, afterburner start unknown or afterburner at <n> %, the idle gate when known, the confidence and the source.
  • Read-only; no profile needed. Alias: binds detent data.
Technical internals
  • Output: JSON File, Aircraft (Game, Plane, Title, NoAfterburner, Afterburner, IdleGate, Confidence, Source, Notes, GameOption), or text Throttle gates (<file>): <n> with a line per aircraft; exit code 0.
  • Failures (exit 1): Unknown binds detent gates argument(s): ...
  • The data: DB\Detents\throttle-gates.json. Related: engine binds detent set (--target overrides an aircraft), engine binds detent show.

What it does Lists the shipped throttle gate data (DB\Detents\throttle-gates.json): per aircraft where its afterburner and idle cut-off are on the game's throttle axis, with source and confidence.

OptionValuesMeaning
--game<game>Game filter value. Example: DCS or IL2Game.
--plane<plane>Include one plane/module per flag. Example: --plane A-10C_2.

Example

engine binds detent gates --game DCS --text
engine binds detent gates --game DCS --plane F-14 --text

#engine binds detent merge

written
engine binds detent merge [--relations <csv>] [--into <relation>] [--ab-source profile|game] [--apply]

Per-aircraft throttle relations of one device axis into one relation in detent mode; without --apply only the plan

For beginners

Joins your old per-aircraft throttle relations (one per afterburner position) into one relation in detent mode. Without --apply it only shows the plan. Merge my throttle relations... shows the plan, Merge applies it.

engine binds detent merge --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • Without --relations: every device axis with two or more bound throttle relations (by name, or DCS thrust axes).
  • --relations a,b,... (at least two, one device axis) and --into <relation> (one of them) choose by hand; else the relation with most aircraft that does not give full power at the detent stays.
  • The device's detent: the calibration, else read from a relation that gives full power there, else from the gate data. Each aircraft's afterburner start comes from its old curve (--ab-source profile, default) or from the gate data where it has a value (--ab-source game).
  • --apply: the kept relation gets the other relations' aircraft and groups, detent mode on, each aircraft's own afterburner point; the others are removed.
Technical internals
  • Output: Applied, AbSource, Proposals (device, sources, calibration, targets, notes, problems); exit code 0.
  • Failures (exit 1): Nothing to merge: no device axis has two or more throttle relations., Cannot merge: ... (a problem of a plan), --into needs --relations., binds detent merge needs at least two relations.
  • --apply saves one history version named "Detent mode: merged ..."; undo with engine profile history.

What it does Merges per-aircraft throttle relations of one device axis into one relation in detent mode: the device's detent and each aircraft's afterburner start are read from the old curves. Without --apply only the plan; profile history undo takes a merge back.

OptionValuesMeaning
--relations<csv>Select relations as CSV for mass operations. Example: --relations 'Trim Pitch,Trim Roll'.
--into<relation>
--ab-sourceprofile game
--applyswitch (no value)
Every value as a command line
engine binds detent merge --ab-source profile
engine binds detent merge --ab-source game

Used by the GUI Binds: Merge my throttle relations... · Binds: Merge

Example

engine binds detent merge --text
engine binds detent merge --relations 'ThrottleLeft,ThrottleLeft29,ThrottleLeftNonAB' --into ThrottleLeft --apply --text

#engine binds unbind

written
engine binds unbind <device::input|input> [--device <name>] [--input <value>] [--format dcs|il2] [--game <game id>] [--all]

--game: only relations with an action of that game, any game id (DCS, IL2Game, StarCitizen, MSFS2024, ...); --format: how the input is written, DCS (default) or IL-2 tokens

For beginners

Frees one physical input in the whole profile: every relation bound to it loses that input. Use it to answer "nothing may be on this button". Unbind under "Unbind an input everywhere (advanced)" on the Binds page runs it; Unbind selected input in the header does it for the selected bind's input.

engine binds unbind "Throttle - HOTAS Warthog::JOY_BTN22" --all --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
  • The input: positional device::input or input, or --input (with --device). --format il2 converts an IL-2 token (joy0_b0).
  • --device <name> limits it to binds on that device (exact name, any case); without it the input matches on any device.
  • --game <id> limits it to relations with an action of that game: any game id (DCS, IL2Game, StarCitizen, MSFS2024, ...), any case; a node without a game counts as DCS.
  • Without --all it refuses when more than one relation matches; with --all every match is freed (the GUI's In all relations tick; Unbind selected input always uses --all with the bind's device).
  • Only the input goes: the binds keep their device, modifiers and curve.
  • A relation's other input (engine binds extra add) on that input is taken out of the relation (its main bind stays); the ambiguity count includes these (" (input 2)").
Technical internals
  • Output: Input, NormalizedInput, Format, DeviceFilter, GameFilter, UpdatedRelations; exit code 0.
  • Failures (exit 1): binds unbind requires --input <value> or positional <device::input|input>., No bind matched input '...'., Ambiguous bind match for input '...'. Matches: .... Use --all or narrow with --device/--game.
  • One undo step with --profile. Related: engine binds clear.

What it does Removes bind links by input token (DCS or IL2 format).

OptionValuesMeaning
--device<name>Include one device per flag. Example: --device LEFT VPC Throttle.
--input<value>Input token. Example: --input JOY_BTN1 or --input joy0_b0.
--formatdcs il2How the input is written: dcs (default, JOY_BTN1) or il2 (joy0_b0).
--game<game id>Only relations with an action of this game; any game id (DCS, IL2Game, StarCitizen, MSFS2024, ...).
--allswitch (no value)Apply operation to all matches (or select all relations/devices where supported).
Every value as a command line
engine binds unbind --format dcs
engine binds unbind --format il2

Used by the GUI Binds: Unbind selected input · Binds: Unbind

Example

engine binds unbind 'VKB Gladiator NXT::JOY_BTN1' --format dcs --text
engine binds unbind --input joy0_b0 --format il2 --all --text
How the options interact
  • Positional value supports device::input shorthand.
  • If matches are ambiguous, use --all or narrow with --device / --game.

#engine binds export

written
engine binds export <path.json> [filter]

Every bind as JSON, a missing folder is created; a filter word writes only the matching binds; with --text the file is the readable view, which binds import cannot read

For beginners

Writes the profile's binds to a JSON file: per relation the device, the input, modifiers and the axis settings. Use it to keep a copy or to edit binds by hand. Export Binds JSON... in the menu of the binds list runs it.

engine binds export "C:\Users\Pilot\Documents\JoyPro\binds.json" --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file"
Advanced
  • The path is the first word; without it the global --out is used. A missing folder is created.
  • Words after the path filter the binds: only those whose relation name, device, input, device alias or modifiers contain them. Such a partial file needs --replace on engine binds import, which then unbinds every relation the file has no bind for.
  • With --text the file gets the readable text form instead of JSON; engine binds import reads only the JSON and refuses the text form ("for reading only").
  • The file is overwritten; the profile and the games are not touched.
Technical internals
  • Output: the file, JSON FormatVersion, GeneratedUtc, Binds (RelationName, IsAxis, Joystick, JAxis, JButton, Inverted, Slider, Deadzone, Curvature, SaturationX, SaturationY, AllReformers, AliasJoystick, DoubleTap, TuningOverrides, ...); exit code 0.
  • Failures (exit 1): binds export requires a target file path.
  • Related: engine binds import, engine relations export (relations with their binds).

What it does Writes every bind to a JSON file (a missing folder is created); a filter word writes only the matching binds. With --text the file is the readable view, which binds import cannot read.

Example

engine --profile 'C:\JoyPro\profiles\pilot_main.pr0file' binds export 'C:\JoyPro\exports\binds.json'
How the options interact
  • A filter word makes a partial file: importing it with --replace removes everything the file does not have.

#engine binds import

written
engine binds import <path.json> [--replace]

The file's binds replace all binds of the profile; a file without the binds of some relations (a filtered export) is refused unless --replace, which unbinds them; profile history undo brings them back

For beginners

Reads a binds file of engine binds export into the profile. The file's binds replace all binds of the profile. Import Binds JSON... in the menu of the binds list runs it after asking first ("Replace all binds?").

engine binds import "C:\Users\Pilot\Documents\JoyPro\binds.json" --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file"
Advanced
  • Each bind goes to the relation of its RelationName. A name the profile does not have becomes a new relation without game actions, holding that bind.
  • Every bind that is not in the file is removed; those relations stay, unbound. A file that lacks the binds of some relations (a filtered export) is refused and the refusal names them; --replace imports it anyway and lists them (Unbound (not in the file): ...). The GUI asks first and then passes --replace. The modifier list is rebuilt from the imported binds.
  • Only binds change: the relations' actions, groups and aircraft stay as they are.
  • Safety: with --profile the import is one history version; undo with engine profile history. The games get the binds at the next export.
Technical internals
  • Output: always text, Imported binds from: <path> and the profile summary; exit code 0.
  • Failures (exit 1): binds import requires a source file path., File not found: ..., <file> is not a JSON file. A binds export with --text is for reading only; ..., <file> is not a binds file of engine binds export ..., the refusal of a partial file, Unknown binds import argument(s): ...; the profile stays as it was.
  • Related: engine binds export, engine relations import.

What it does Reads a binds JSON file (from binds export): its binds replace all binds of the profile. A file without the binds of some relations (a filtered export) is refused unless --replace, which unbinds them; profile history undo brings them back. A file that is not a binds document ends with a clear error.

OptionValuesMeaning
--replaceswitch (no value)Import also when the file lacks the binds of some relations: those relations lose their bind (the file's binds replace all of the profile's). Without it such a file is refused.

Example

engine --profile 'C:\JoyPro\profiles\pilot_main.pr0file' binds import 'C:\JoyPro\exports\binds.json'
engine --profile 'C:\JoyPro\profiles\pilot_main.pr0file' binds import 'C:\JoyPro\exports\throttle-binds.json' --replace
How the options interact
  • The import replaces everything of its kind in the profile; a partial file (a filtered export, relations mass export) needs --replace. profile merge adds relations instead.
  • The GUI asks before it imports and then passes --replace.

#engine binds edit

written
engine binds edit

No args; exports temp binds JSON, opens editor, re-imports on close; uses --editor or notepad

For beginners

Opens every bind of the profile as one JSON file in a text editor and reads it back when you close the editor. For many changes at once. Binds Edit on the Advanced page runs it.

engine binds edit --editor "code --wait {file}" --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file"
Advanced
  • The file is the binds document of engine binds export, written to %TEMP%\joypro-engine-binds-<time>.json.
  • The editor: the global --editor command ({file} stands for the file, else the path is appended; it runs through cmd.exe /c), else Notepad. The engine waits until the editor process ends, so use an editor's wait flag.
  • On close the file is applied like engine binds import: binds to the relations of the same name.
Technical internals

What it does Opens binds JSON in an external editor for round-trip editing.

Used by the GUI Advanced: Binds Edit

Example

engine --editor 'code --wait {file}' binds edit