Diagnostics

The Diagnostics page is for when something is off and you want to know what. It surfaces the runtime's metrics and a rolling event log, and it exports the single artifact — the support bundle — that we'll ask for if you open a ticket.

Metrics grid

Four compact cards summarise how hard the runtime is working. Values are live, updated twice a second.

Control-loop rate — target 50 Hz; if this dips into the 40s, something's stealing CPU or the sim is paused. The sidebar of the card shows the last 60 seconds as a sparkline.
Pipeline latency — time from SimSnapshot arrival to force dispatch, in microseconds. Typical value: 100–800 µs.
Effects active — how many of the thirteen effects are currently contributing non-zero output.
Reassertions — how often the dispatcher has had to re-send effect parameters to the device. Under MSFS on Proton the kernel sometimes drops effects after ~20 s; the reassert loop covers for that and you'll see this counter tick up while flying.

Figure 2. Metrics grid close-up. Each card has a headline value, a 60 s sparkline, and a short caption.

Session event log

The bulk of the page is a rolling event log. Levels are colour-coded:

INF / DBG — normal text.
WRN — amber. Usually benign but worth knowing.
ERR / FTL — red. Something failed.

The log is backed by an in-memory ring buffer (about 2,000 lines). Scroll up to see older events; the newest line stays pinned at the bottom unless you've scrolled manually.

Figure 3. Event log strip. Warnings in amber, errors in red. The Copy-all button dumps the current visible window to the clipboard as plain text.

Filtering

The filter bar at the top of the log takes a plain text match. Type WRN to only see warnings and errors; simconnect to see SimConnect-related chatter; any substring at all. Clear the filter to see everything again.

Support-bundle export

The Export support bundle button — top-right of the Diagnostics header — produces a single ZIP containing everything that lets us reproduce your problem without access to your machine. What's in it:

sysinfo.txt — OS, kernel, distro, CPU model, RAM, .NET runtime version, locale.
session.log — the current session's complete event log (not just what's on screen).
crashes/ — the last crash dump plus the stack trace, if there is one.
doctor.json — the most recent Doctor-page scan results in machine-readable form.
tunables.yaml — the active profile's values at the moment of export.
simconnect-config.xml — the XML the bridge last read from MSFS, with any passwords removed. Not included for X-Plane sessions.

The bundle is written to a temporary path and then the Diagnostics page shows a clickable link and a Reveal in file manager button. Attach the ZIP to a feedback report and we'll pick it up when we triage.

Figure 4. After export, a small banner shows the bundle filename, size, and a button to open the feedback form. The support bundle never leaves your machine automatically — you choose to send it.

What it does NOT contain

No personal identifiers, no cloud credentials, no network traffic capture. The full list of allow-listed filenames the bundle is permitted to include lives in the source; anything outside that list is omitted. See Support bundles for the complete list.

Clipboard export

If you just want to quote a single log line (“bridge says X, is that normal?”), right-click the line and choose Copy. For longer quotes, Copy all at the top of the log dumps the visible window as plain UTF-8 text.