Telemetry Control

Manage iRacing’s telemetry logging and recording features. Toggle logging, mark events of interest for later review, start / stop / restart recording sessions, save a snapshot of the live telemetry, the session info and iRaceDeck’s own state to disk for diagnostics, and capture a CPU profile of iRaceDeck itself when it is using a lot of CPU.

Modes

Select the mode from the Mode dropdown in the Property Inspector.

Toggle Logging

Toggle iRacing’s telemetry log file on or off.

Details

Method: Key binding
Dial: No rotation support
Default binding: Alt+L
Telemetry-aware icon: No

Settings

No additional settings

Mark Event

Mark the current moment in the telemetry log for later review.

Details

Method: Key binding
Dial: No rotation support
Default binding: M
Telemetry-aware icon: No

Settings

No additional settings

Start Recording

Start a telemetry recording session via the iRacing SDK.

Details

Method: iRacing API
Dial: No rotation support
Default binding: No keyboard binding
Telemetry-aware icon: No

Settings

No additional settings

Stop Recording

Stop the current telemetry recording session via the iRacing SDK.

Details

Method: iRacing API
Dial: No rotation support
Default binding: No keyboard binding
Telemetry-aware icon: No

Settings

No additional settings

Restart Recording

Stop and immediately restart telemetry recording via the iRacing SDK.

Details

Method: iRacing API
Dial: No rotation support
Default binding: No keyboard binding
Telemetry-aware icon: No

Settings

No additional settings

Take Snapshot

Save everything iRaceDeck currently sees from iRacing — the full live telemetry and the session info — to disk, together with what iRaceDeck itself had worked out at that moment. Each press writes two timestamped files to the Output Folder: a .json file holding every telemetry variable, the session info and iRaceDeck’s own state (the raw data), and a companion .md report you can read at a glance — the session identification, the running order and the on-track order with each driver’s car number, laps completed, and location, the player’s own telemetry, and a short Plugin State table. It is a developer / diagnostic tool: use it to check what iRacing was reporting at a given moment, and attach both files when you report something iRaceDeck said, showed or did wrong. Take the snapshot at the moment it happens, because that is the moment the files describe.

iRaceDeck’s own state is what the plugin has built up over the session, which one frame of telemetry cannot show:

Your fuel use per lap and the laps of fuel left that iRaceDeck calculates from it
The race order and the gaps to the cars around you that it was tracking
The caution state, including the gap to the car you line up behind, and the rolling-start formation
What the Race Engineer was saying, and what he had queued to say next
Your iRaceDeck settings, and any warning banners iRaceDeck was showing

How that part of the .json file is laid out follows iRaceDeck’s internals and may change between releases, so don’t build anything that depends on it. The file is also larger than it used to be: up to a few megabytes in a full field.

The mode only reads data the plugin already has and sends nothing to iRacing, so it never affects the sim. A press while iRacing isn’t running (no telemetry available) is skipped with a warning in the plugin log; a successful save is logged as well, including the file paths. There is no feedback on the key itself.

Details

Method: Local file write (saves telemetry and iRaceDeck’s state to disk) — no iRacing command
Dial: No rotation support
Default binding: No keyboard binding
Telemetry-aware icon: No

Setting: Output Folder

The folder the snapshot files are written to. Leave it blank to use the default — an iRaceDeck\telemetry-snapshots folder in your user home folder (for example C:\Users\<you>\iRaceDeck\telemetry-snapshots). Any folder path works: environment variables such as %USERPROFILE% and a leading ~ are expanded, and a relative path is resolved against your home folder rather than the plugin’s own folder. The folder is created if it doesn’t exist.

Files are named telemetry-snapshot-YYYYMMDD-HHMMSS-mmm.json and .md — local time with millisecond resolution, so presses in quick succession normally get their own files rather than overwriting the previous one.

Capture CPU Profile

Record 30 seconds of what iRaceDeck itself is doing, for a report about high CPU use, without leaving the car. It is the same capture as Capture CPU profile on the Settings window’s Diagnostics tab, from a key: useful in a race that cannot be paused, when opening the Settings window is not an option.

While the capture runs, the key counts down the seconds left. When the files are saved it shows SAVED for 3 seconds, or FAILED if the capture fails, whether it could not start or its files could not be saved (the reason is in the plugin log), then its normal icon again. Only one capture runs at a time: a press while one is running, whether it was started from a key or from the Settings window, is ignored, and every Capture CPU Profile key shows the running capture’s countdown.

The capture writes two files to the profiles folder next to the plugin log, a .cpuprofile and a .txt summary, and keeps the five newest captures. Open the folder with Open folder beside Capture CPU profile on the Diagnostics tab, then attach both files to your report. See If iRaceDeck uses a lot of CPU.

The mode sends nothing to iRacing and works with or without iRacing running.

Details

Method: Records a CPU profile of iRaceDeck — no iRacing command
Dial: No rotation support
Default binding: No keyboard binding
Telemetry-aware icon: No

Settings

No additional settings