Binds an 'Only add' export did not write because the game uses their button for another function, with the game's function and the date; they clear at the next export that writes the bind or finds the button free
For beginners
Lists the binds an "Only add" export did not write because the game uses their button for another function. The Check
shows them as "Not written to the game".
engine export-marks list --game DCS --profile "C:\Users\Pilot\Documents\JoyPro\My Sticks.pr0file" --text
Advanced
Each mark names the bind, the game's function on that button (or that there was no free place) and the date. Marks
clear at the next export that writes the bind or finds the button free. --game <id> shows one game's marks.
engine export-marks dismiss --game <id> --relation <name> [--aircraft <a>] is the Check's "Keep as is": no card for
these marks any more.
Technical internals
Output: JSON or text with --text; another argument fails with Unknown export-marks argument(s).
The marks are stored in the profile; an export replaces the marks of its game and aircraft and saves the profile
quietly.
What it does Binds an 'Only add' export did not write because the game uses their button for another function, with the game's function and the date; they clear at the next export that writes the bind or finds the button free.
'Keep as is': the Check shows no card for these marks; --game takes the game id or an alias (il2, wt); --aircraft: only the marks of that aircraft; a warning when no open mark matches
For beginners
The Check's Keep as is for a bind that an "Only add" export did not write: the marks of that relation get no card
any more. The game keeps its own bind on that button, and JoyPro stops asking about it.
--game <id> and --relation <name> are required; --aircraft <a> dismisses only the marks of that aircraft,
without it every mark of the relation in that game. Names are compared without case; the game is a game id
(DCS, IL2Game, StarCitizen, MSFS2024, ...) or an alias (il2, wt, ...), see engine export-marks list.
A dismissed mark stays in the list with [kept as is]. A later export that skips the same bind on the same button
keeps it dismissed; when the bind is written or the conflict changes, the mark goes or comes back as a new one.
Changes only the profile (saved with --profile, one undo step). Nothing in the game changes.
Technical internals
Output: the marks after the change as for engine export-marks list (JSON Marks, Changed, or text with
--text, ending Changed: <n>). Exit code 0, also when nothing matched: then the profile is not changed and the
warning No open mark of '<relation>' in <game> to dismiss; ... says so (Warnings in the JSON, Warning: in the
text).
Exit code 1 with export-marks dismiss needs --game <id> and --relation <name>., Unknown game: ... or Unknown export-marks argument(s): ....
What it does 'Keep as is' for the marks of an 'Only add' export: the Check shows no card for them. --game takes the game id or an alias (il2, wt); --aircraft limits it to that aircraft's marks. When no open mark matches, the output says so.
Option
Values
Meaning
--game
<id>
The game of the marks: its id or an alias (IL2Game or il2, WarThunder or wt). Example: --game DCS.
--relation
<name>
The relation whose marks are kept as they are. Example: --relation 'Gear Toggle'.
--aircraft
<a>
Only the marks of this aircraft (default: all of the relation's marks in the game). Example: --aircraft F-16C_50.