JoyPro2 Discord GitHub
Engine (CLI)

engine telemetry

Show:

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

#engine telemetry games

written
engine telemetry games

Telemetry recording, docs/telemetry-recording.md: the games, what JoyPro listens to, ACMI possible

For beginners

Lists the games whose telemetry JoyPro can record (like a flight recorder for each round, mission or flight), what JoyPro listens to for each one, whether a recording can become a Tacview file, and whether the game is recorded now.

engine telemetry games --text
Advanced
  • Ten games: DCS World, IL-2 Great Battles, IL-2 Series: Korea, War Thunder, X-Plane 12, X-Plane 11, Microsoft Flight Simulator 2024 and 2020, Falcon BMS and Elite Dangerous.
  • Per game: the way JoyPro reads it (for example UDP 41992 (JoyPro's DCS hook), HTTP 127.0.0.1:8111 (the game's local web server), SimConnect through your own SimConnect.dll, BMS's shared memory, Elite's Status.json and journal), the game's processes, ACMI yes or no (IL-2 and Elite send no position, so no Tacview export), and what has to be set up once (DCS: JoyPro's hook; IL-2: JoyPro's address in startup.cfg, both on the Force Feedback page, engine ffb telemetry setup).
  • "Recorded" is true when recording is switched on and the game is not switched off for it (engine telemetry config set).
  • Read-only; no option except the global --text (and --folder, which changes nothing here).
Technical internals
  • Output: JSON (Enabled, Games with Id, Title, Transport, ProcessNames, Acmi, Setup, Recorded), or with --text "Telemetry recording is on|off. Games with telemetry: " and two lines per game ([recorded] behind the recorded ones).
  • Exit code 0; 1 with Unknown telemetry games argument(s): ....
  • Settings read from %LOCALAPPDATA%\JoyPro2\Telemetry\telemetry-recording.json (with JOYPRO_DATA_DIR: <data>\Telemetry\); a file that cannot be read means the defaults (recording off).
  • Related: engine telemetry config show, engine telemetry record, engine ffb telemetry status; reference telemetry-recording.

What it does Telemetry recording, docs/telemetry-recording.md: the games, what JoyPro listens to, ACMI possible.

Example

engine telemetry games --text

#engine telemetry config show

written
engine telemetry config show
For beginners

Shows the telemetry recording settings: whether recording is on, where the sessions go, how much space they may take, how long they are kept, the values per second and the per-game switches. It is what Settings > Telemetry recording in the GUI edits.

engine telemetry config show --text
Advanced
  • The values, with their defaults: enabled false, folder "" (= <data>\Telemetry\Recordings), maxTotalMb 4096 (0 = no size cap), keepDays 0 (= keep), sampleHz 20 (0 = every frame the game sends), keepRaw true, sessionTimeoutSeconds 60, and games with enabled per game (a game without an entry is recorded when the global switch is on).
  • Values out of range are shown clamped (for example the session timeout to 5..3600 s), as the recorder uses them.
  • Read-only. engine telemetry config without show or set shows too.
Technical internals
  • Output: JSON (ConfigPath, Folder = the recordings folder in use, Config, Warnings), or with --text the settings as indented JSON.
  • Exit code 0; 1 with Unknown telemetry config argument(s): .... A settings file that cannot be read gives the warning The telemetry recording settings could not be read (...); the defaults apply.
  • File: %LOCALAPPDATA%\JoyPro2\Telemetry\telemetry-recording.json (<data> = JOYPRO_DATA_DIR when set).
  • Related: engine telemetry config set, engine telemetry games; reference telemetry-recording.

What it does Shows the telemetry recording settings (<data>\Telemetry\telemetry-recording.json) with every default filled in.

Example

engine telemetry config show --text

#engine telemetry config set

written
engine telemetry config set [--game <game>] --param enabled|folder|max-total-mb|keep-days|sample-hz|keep-raw|session-timeout=<value>...
For beginners

Changes the telemetry recording settings, for example switches recording on. Recording is off until you do this (or switch it on in Settings > Telemetry recording); while it is off nothing is recorded or polled.

engine telemetry config set --param enabled=true --param folder="D:\Recordings" --param keep-days=30 --text
Advanced
  • --param key=value, as often as needed (_ in a key counts as -):
Key Value
enabled true or false: the global switch
folder the recordings folder, any drive; empty (folder=) = the default <data>\Telemetry\Recordings
max-total-mb space for recordings in MB, 0 = no cap (at most 10000000)
keep-days delete sessions older than this, 0 = keep (at most 100000)
sample-hz frames per second written, 0 = every frame the game sends (at most 1000); events are always kept
keep-raw true or false: also keep what the game sent unprocessed
session-timeout seconds without telemetry that end a session (5..3600; a longer pause starts a new one)
  • --game <game> switches one game: then only --param enabled=true|false is allowed. The game is a recording game id or a short name (il2, korea, wt, xp12, xp11, msfs, bms, elite; see engine telemetry games).
  • Numbers are clamped to their range; the file is written once at the end, only when every parameter was valid.
  • Safety: only the settings file changes; no recording is deleted here (the new space and age limits apply at the next session start, or now with engine telemetry prune, engine telemetry recover). A running recorder of the GUI reads the file again when the GUI tells it to.
Technical internals
  • Output: JSON (ConfigPath, Changes, Warnings, Config), or with --text "Telemetry recording settings: " and one line per change.
  • Exit code 0; 1 (nothing written) with telemetry config set needs --param key=value (...), --param needs key=value: ..., <key> must be true or false., <key> must be a number >= 0., Unknown telemetry setting '<key>' (...), With --game only enabled=true|false can be set., JoyPro records no telemetry of '<game>'. See: engine telemetry games. or Unknown telemetry config argument(s): ....
  • File: %LOCALAPPDATA%\JoyPro2\Telemetry\telemetry-recording.json (<data> = JOYPRO_DATA_DIR when set), written through a temporary file.
  • Related: engine telemetry config show, engine telemetry sessions; reference telemetry-recording.

What it does Sets telemetry recording settings: enabled, folder, max-total-mb, keep-days, sample-hz, keep-raw, session-timeout; with --game the game's own enabled switch.

OptionValuesMeaning
--game<game>Game filter value. Example: DCS or IL2Game.
--paramenabled folder max-total-mb keep-days sample-hz keep-raw session-timeoutA response model parameter as name=value, repeatable. Example: --param sensitivity=22 --param offset=10.
Every value as a command line
engine telemetry config set --param enabled
engine telemetry config set --param folder
engine telemetry config set --param max-total-mb
engine telemetry config set --param keep-days
engine telemetry config set --param sample-hz
engine telemetry config set --param keep-raw
engine telemetry config set --param session-timeout

Example

engine telemetry config set --param enabled|folder|max-total-mb|keep-days|sample-hz|keep-raw|session-timeout=<value> --text

#engine telemetry sessions

written
engine telemetry sessions [--game <game>] [--folder <folder>]

Recorded sessions, newest first; alias: list

For beginners

Lists the recorded sessions, newest first: date, game, aircraft, duration and size. The number in front of each one can be used as <session> in the other telemetry commands.

engine telemetry sessions --game DCS --text
Advanced
  • --game <game> shows the sessions of one game (a recording game id or short name, see engine telemetry games).
  • --folder <folder> lists another folder than the one of the settings (for example recordings copied from another PC).
  • A session still being written is marked [recording], one cut off by a crash [unfinished] (engine telemetry recover finishes it).
  • Read-only. engine telemetry alone, and engine telemetry list, do the same.
Technical internals
  • Output: JSON (Folder, TotalBytes, Sessions with Path, FileName, Game, GameTitle, Created, CreatedLocal, DurationSeconds, Duration, SizeBytes, Size, Aircraft, Maps, Frames, Events, RawPackets, Channels, Complete, Recording, EndReason, Acmi; then Problems, Warnings), or with --text "Recorded sessions in : ()" and one numbered line per session.
  • Exit code 0 (a file that cannot be read is listed as a problem); 1 with Unknown telemetry sessions argument(s): .... A --game JoyPro does not record lists nothing.
  • Files: *.jptel in the folder, named like 2026-10-18_14-03-22_DCS.jptel (local start time and game).
  • Related: engine telemetry show, engine telemetry export, engine telemetry delete; reference telemetry-recording.

What it does Recorded sessions, newest first; alias: list.

OptionValuesMeaning
--game<game>Game filter value. Example: DCS or IL2Game.
--folder<folder>

Example

engine telemetry sessions --text

#engine telemetry show

written
engine telemetry show <session> [--folder <folder>]

<session> = path, file name, latest or a number of the list

For beginners

Shows one recorded session: game, aircraft, map, start, duration, size, what it holds (frames, events, raw data), why it ended, whether a Tacview export is possible, and its channels by category.

engine telemetry show latest --text
Advanced
  • <session>: a path to a .jptel file, a file name in the recordings folder (with or without .jptel), latest, or a number of engine telemetry sessions (1 = newest).
  • --folder <folder> looks in another folder than the one of the settings.
  • The whole file is read once to count the events by kind. Read-only.
Technical internals
  • Output: JSON (Session as in the sessions list, Header, Summary, Nav = where the game's position and attitude are, Channels with Key, Title, Unit, Category, Min, Max, and Events = count per kind), or with --text a few lines ("ACMI export: yes" or "no (no position in this game's telemetry)", the channels grouped by category with their units, the event kinds by count).
  • Exit code 0; 1 with Which session? A path, a file name, "latest" or a number from: engine telemetry sessions --text, No recorded session '<x>' in <folder>. or Unknown telemetry show argument(s): ....
  • Related: engine telemetry preview, engine telemetry export; reference telemetry-recording.

What it does <session> = path, file name, latest or a number of the list.

OptionValuesMeaning
--folder<folder>

Example

engine telemetry show <session> --text

#engine telemetry export

written
engine telemetry export <session> --format acmi|acmi-zip|csv [--to <file or folder>] [--max-hz <n>] [--no-per-channel]

Tacview ACMI 2.2 / CSV

For beginners

Turns a recorded session into a file for Tacview (ACMI 2.2) or into CSV tables for a spreadsheet. The GUI's Export for Tacview (ACMI) and Export CSV in Settings > Telemetry recording do the same.

engine telemetry export latest --format acmi-zip --to "C:\Users\Pilot\Documents\Tacview\last-flight.zip.acmi" --text
Advanced
  • <session>: path, file name, latest or a number of engine telemetry sessions; --folder <folder> looks in another folder.
  • --format (default acmi-zip):
    • acmi-zip: a .zip.acmi (a zip with one .txt.acmi); zip and zip.acmi mean the same.
    • acmi: a plain .txt.acmi; txt.acmi and text mean the same.
    • csv: a folder with <session>.csv (time and every channel, one row per frame), <session>-events.csv, <session>-channels.csv (key, title, unit, category, range) and, unless --no-per-channel, one file per channel in <session>-channels\ with time and value at every change.
  • --to <file or folder>: where it goes (a file for ACMI, a folder for CSV). Default: Exports\ beside the session, <session>.zip.acmi, <session>.txt.acmi or <session>-csv\. An existing file of that name is replaced.
  • --max-hz <n>: at most this many frames a second (ACMI default 20; CSV default every frame, and it thins only the main table, not the per-channel files). A value that is not a number means the default.
  • ACMI needs a position: sessions of IL-2 and Elite Dangerous (and any session without a frame with a position) can only go to CSV. War Thunder has no map coordinates, so it is placed on a flat world around 0/0.
  • Safety: the session itself is never changed; the ACMI file is written to a temporary file first.
Technical internals
  • Output: JSON (Session, Format, Output, Files, Frames, Rows, Objects, Warnings), or with --text "Exported as : ( rows, other objects)" and the warnings.
  • Exit code 0; 1 with --format acmi|acmi-zip|csv, This recording has no position (<game> does not send one): ACMI needs one. Export CSV instead., This recording has no frame with a position ..., a session that cannot be found (as for engine telemetry show) or Unknown telemetry export argument(s): ....
  • The global --out is the engine's output file as with every command; the export target is --to.
  • Related: engine telemetry show, engine telemetry preview; reference telemetry-recording.

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
--formatacmi acmi-zip csvFormat selector. Example values: dcs/il2 for binds unbind, rl/json for relations mass export.
--to<file or folder>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.
--max-hz<n>
--no-per-channelswitch (no value)
Every value as a command line
engine telemetry export --format acmi
engine telemetry export --format acmi-zip
engine telemetry export --format csv

Example

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

#engine telemetry preview

written
engine telemetry preview <session> [--channel <key>]... [--points <n>]
For beginners

Reads a few channels of a recorded session reduced to a short series each, for a small timeline. Without a choice it takes altitude, speed and G (or pitch, roll, throttle, angle of attack), as the timeline in Settings > Telemetry recording does.

engine telemetry preview latest --channel dcs.alt --channel dcs.ias --points 300 --text
Advanced
  • <session>: path, file name, latest or a number of engine telemetry sessions; --folder <folder> looks in another folder.
  • --channel <key> (repeatable): the channels to read, by the keys engine telemetry show lists. A key the session does not have is left out without a message. Without --channel: the first three channels with values among altitude, speed, G, pitch, roll, throttle and angle of attack, else the first channels of the session.
  • --points <n> (default 200, 4..5000; not a number = 200): about this many points per channel. Each time bucket keeps its minimum and maximum, so peaks stay visible.
  • Read-only.
Technical internals
  • Output: JSON (Session, Series with Key, Title, Unit, Min, Max, Times in seconds from the session start, Values), or with --text one line per channel: " (, <unit>): <n> points, <min> .. <max>".</li> <li>Exit code <code>0</code>; <code>1</code> for a session that cannot be found (as for <a href="../cli/telemetry.html#telemetry-show"><code>engine telemetry show</code></a>) or <code>Unknown telemetry preview argument(s): ...</code>.</li> <li>Related: <a href="../cli/telemetry.html#telemetry-show"><code>engine telemetry show</code></a>, <a href="../cli/telemetry.html#telemetry-export"><code>engine telemetry export</code></a>; reference <a href="../reference/telemetry-recording.html">telemetry-recording</a>.</li> </ul> </section> </div><p><span class="lbl">What it does</span> A few channels of a recorded session reduced to --points values each, for a timeline.</p><div class="table-wrap"><table class="opts"><thead><tr><th>Option</th><th>Values</th><th>Meaning</th></tr></thead><tbody><tr><td><code>--channel</code></td><td><code><key></code></td><td></td></tr><tr><td><code>--points</code></td><td><code><n></code></td><td>Number of preview samples from -1 to 1. Example: --points 21.</td></tr></tbody></table></div><p class="lbl">Example</p><pre><code>engine telemetry preview <session> --text</code></pre></article><article class="entry cli level-full" id="telemetry-delete"><header><h3 class="eh"><a class="anchor" href="#telemetry-delete">#</a><code>engine telemetry delete</code></h3><span class="badge full">written</span></header><pre class="sig"><code>engine telemetry delete <session>...</code></pre><p>Alias: remove</p><div class="hand"><section class="layer layer-beginner" data-layer="beginner"><div class="layer-badge">For beginners</div> <p>Deletes recorded sessions. The GUI's <strong>Delete</strong> in Settings > Telemetry recording does the same after asking; the command does not ask.</p> <pre><code class="language-powershell">engine telemetry delete 3 4 --text </code></pre> </section> <section class="layer layer-advanced" data-layer="advanced"><div class="layer-badge">Advanced</div> <ul> <li>One or more <code><session></code> values: path, file name, <code>latest</code> or a number of <a href="../cli/telemetry.html#telemetry-sessions"><code>engine telemetry sessions</code></a> (the numbers refer to the list before anything is deleted). <code>--folder <folder></code> looks in another folder. <code>remove</code> is the same command.</li> <li>Every session is looked up first: when one cannot be found nothing is deleted.</li> <li>Safety: a session being recorded right now is never deleted (it is listed as not deleted). Deleted files are gone, not in the recycle bin.</li> </ul> </section> <section class="layer layer-technical" data-layer="technical"><div class="layer-badge">Technical internals</div> <ul> <li>Output: JSON (<code>Deleted</code>, <code>Problems</code>), or with <code class="opt">--text</code> "Deleted <n> session(s)." with the files and a "not deleted:" line per problem (for example <code><file> is being recorded right now.</code>).</li> <li>Exit code <code>0</code>; <code>1</code> when a session could not be deleted (the problems also go to the error output), without a session (<code>telemetry delete <session>... (a path, a file name, "latest" or a number)</code>), or when a session cannot be found (<code>No recorded session '<x>' in <folder>.</code>).</li> <li>Related: <a href="../cli/telemetry.html#telemetry-sessions"><code>engine telemetry sessions</code></a>, <a href="../cli/telemetry.html#telemetry-recover"><code>engine telemetry recover</code></a> (<code>prune</code> deletes by the retention settings).</li> </ul> </section> </div><p><span class="lbl">What it does</span> Deletes recorded sessions (alias: remove).</p><p class="lbl">Example</p><pre><code>engine telemetry delete <session> --text</code></pre></article><article class="entry cli level-full" id="telemetry-recover"><header><h3 class="eh"><a class="anchor" href="#telemetry-recover">#</a><code>engine telemetry recover</code></h3><span class="badge full">written</span></header><pre class="sig"><code>engine telemetry recover | prune</code></pre><p>Finish sessions cut off by a crash | apply the retention settings; exit code 1 when a session could not be read, finished or deleted</p><div class="hand"><section class="layer layer-beginner" data-layer="beginner"><div class="layer-badge">For beginners</div> <p>Finishes sessions that were cut off by a crash or a killed process, so they can be shown and exported again (<code>engine telemetry recover</code>). <code>engine telemetry prune</code> applies the retention settings now: it deletes the sessions that are too old or do not fit into the space for recordings.</p> <pre><code class="language-powershell">engine telemetry recover --text </code></pre> </section> <section class="layer layer-advanced" data-layer="advanced"><div class="layer-badge">Advanced</div> <ul> <li><code>recover</code>: every <code>.jptel</code> in the folder without a summary that is not being written: the damaged tail is cut and the summary is written from the data. Complete sessions are left alone. The recorder does the same itself when it starts.</li> <li><code>prune</code>: first the sessions older than <code>keep-days</code> (0 = no age limit), then the oldest until the folder is at most <code>max-total-mb</code> (0 = no size limit). The recorder does the same before and after every session.</li> <li><code>--folder <folder></code> works on another folder than the one of the settings (<code>prune</code> still uses the limits of the settings).</li> <li>Safety: the session being recorded is never touched by either. <code>prune</code> deletes files for good; set the limits with <a href="../cli/telemetry.html#telemetry-config-set"><code>engine telemetry config set</code></a> and look at <a href="../cli/telemetry.html#telemetry-sessions"><code>engine telemetry sessions</code></a> first.</li> </ul> </section> <section class="layer layer-technical" data-layer="technical"><div class="layer-badge">Technical internals</div> <ul> <li>Output of <code>recover</code>: JSON (<code>Folder</code>, <code>Recovered</code>, <code>Problems</code>), or with <code class="opt">--text</code> "Finished <n> session(s) that were cut off." with the files and "problem:" lines.</li> <li>Output of <code>prune</code>: JSON (<code>Folder</code>, <code>Deleted</code>, <code>Problems</code>), or with <code class="opt">--text</code> "Deleted <n> session(s) (size cap <size or none>, keep days <n or no limit>)." with the files and "problem:" lines.</li> <li>Exit code <code>0</code>; <code>1</code> when a session could not be read, finished or deleted (the others are done; the problems are listed), or with <code>Unknown telemetry recover argument(s): ...</code> or <code>Unknown telemetry prune argument(s): ...</code>.</li> <li>Related: <a href="../cli/telemetry.html#telemetry-delete"><code>engine telemetry delete</code></a>, <a href="../cli/telemetry.html#telemetry-config-show"><code>engine telemetry config show</code></a>; reference <a href="../reference/telemetry-recording.html">telemetry-recording</a>.</li> </ul> </section> </div><p><span class="lbl">What it does</span> Finishes sessions cut off by a crash (telemetry recover) or applies the retention settings now (telemetry prune); exit code 1 when a session could not be read, finished or deleted.</p><p class="lbl">Example</p><pre><code>engine telemetry recover --text engine telemetry prune --text</code></pre></article><article class="entry cli level-full" id="telemetry-record"><header><h3 class="eh"><a class="anchor" href="#telemetry-record">#</a><code>engine telemetry record</code></h3><span class="badge full">written</span></header><pre class="sig"><code>engine telemetry record --game <game> [--seconds <n>] [--folder <folder>] [--sample-hz <n>] [--no-raw] [--no-game-check]</code></pre><p>Records now; it ends after --seconds, with Ctrl+C or when the game exits; --no-game-check: the game process is not watched</p><div class="hand"><section class="layer layer-beginner" data-layer="beginner"><div class="layer-badge">For beginners</div> <p>Records the telemetry of one game now, in this window, also when recording is switched off in the settings. Start the game (or start this first and then the game); Ctrl+C ends the recording, and it also ends when the game exits.</p> <pre><code class="language-powershell">engine telemetry record --game DCS --seconds 600 --text </code></pre> </section> <section class="layer layer-advanced" data-layer="advanced"><div class="layer-badge">Advanced</div> <ul> <li><code>--game <game></code> (required): a recording game id or short name (<a href="../cli/telemetry.html#telemetry-games"><code>engine telemetry games</code></a>). DCS and IL-2 need their one-time setup first (<a href="../cli/ffb.html#ffb-telemetry-setup"><code>engine ffb telemetry setup</code></a>).</li> <li><code>--seconds <n></code>: stops after that time; without it, it runs until Ctrl+C.</li> <li><code>--folder <folder></code>: writes the session there instead of the folder of the settings.</li> <li><code>--sample-hz <n></code>: frames per second written (0 = every frame the game sends), instead of the setting.</li> <li><code class="opt">--no-raw</code>: does not keep what the game sent unprocessed.</li> <li><code class="opt">--no-game-check</code>: listens without the game's process. Without it, it waits for the game ("waiting for DCS.exe / DCS_mt.exe") and stops when the game exits.</li> <li>It runs JoyPro's force feedback process (<code>JoyPro.Ffb.exe record --force</code>), which also does the GUI's automatic recordings. Only one process can listen on a game's telemetry port: do not run it while the GUI records or runs force feedback for the same game.</li> <li>Safety: only listens locally and writes the session file; nothing is sent anywhere and the game is not changed.</li> </ul> </section> <section class="layer layer-technical" data-layer="technical"><div class="layer-badge">Technical internals</div> <ul> <li>Output: a status line "Recording <game> telemetry (Ctrl+C ends it): JoyPro.Ffb record ..." and then the recorder's state lines (waiting, listening, recording with the session file and its frames, and the reason it ended); the exit code is the recorder's.</li> <li>Exit code <code>1</code> without a known <code class="opt">--game</code> (the usage line lists the ids), with <code>Unknown telemetry record argument(s): ...</code>, or with <code>JoyPro.Ffb.exe not found (<path>); it reads the games' telemetry. Set JOYPRO_FFB_EXE to its path.</code> (it is looked for in <code>ffb\</code> beside the engine's folder, or at <code>JOYPRO_FFB_EXE</code>).</li> <li>The session goes to <code><folder>\<date>_<time>_<game>.jptel</code>; afterwards <a href="../cli/telemetry.html#telemetry-sessions"><code>engine telemetry sessions</code></a> lists it.</li> <li>Related: <a href="../cli/telemetry.html#telemetry-show"><code>engine telemetry show</code></a>, <a href="../cli/telemetry.html#telemetry-export"><code>engine telemetry export</code></a>, <a href="../cli/ffb.html#ffb-telemetry-status"><code>engine ffb telemetry status</code></a>; reference <a href="../reference/telemetry-recording.html">telemetry-recording</a>.</li> </ul> </section> </div><p><span class="lbl">What it does</span> Records now; it ends after --seconds, with Ctrl+C or when the game exits; --no-game-check: the game process is not watched.</p><div class="table-wrap"><table class="opts"><thead><tr><th>Option</th><th>Values</th><th>Meaning</th></tr></thead><tbody><tr><td><code>--game</code></td><td><code><game></code></td><td>Game filter value. Example: DCS or IL2Game.</td></tr><tr><td><code>--seconds</code></td><td><code><n></code></td><td></td></tr><tr><td><code>--folder</code></td><td><code><folder></code></td><td></td></tr><tr><td><code>--sample-hz</code></td><td><code><n></code></td><td></td></tr><tr><td><code>--no-raw</code></td><td><span class="muted">switch (no value)</span></td><td></td></tr><tr><td><code>--no-game-check</code></td><td><span class="muted">switch (no value)</span></td><td></td></tr></tbody></table></div><p class="lbl">Example</p><pre><code>engine telemetry record --game <game> --text</code></pre></article> </div> <footer class="foot">JoyPro is free software: <a href="https://github.com/Holdi601/JoystickProfiler2/blob/main/LICENSE">GPL-3.0</a> · <a href="https://discord.gg/yK4gQA9xgk">Discord</a> · <a href="https://github.com/Holdi601/JoystickProfiler2">Source</a> · <a href="../project/wiki-status.html">Wiki status</a></footer> </main> </div> <script src="../assets/i18n.js"></script> <script src="../assets/site.js"></script> </body> </html>