# FAQ & Troubleshooting

> Frequently asked questions and solutions to common issues with Braking Lab Capture.

## Frequently Asked Questions

### Does Capture work on Mac or Linux?

No, Capture is currently **Windows only**. Both iRacing and Le Mans Ultimate run on Windows, so Capture is designed for the same platform.

### Do I need a simulator running to use Capture?

Yes, your simulator generates the telemetry files that Capture processes — `.ibt` files for iRacing and `.duckdb` files for Le Mans Ultimate. Without simulator sessions, there's no data to capture. However, you can import existing telemetry files from previous sessions without running the simulator.

### Does Capture affect sim performance?

No. Capture doesn't interact with the simulator directly — it only reads telemetry files **after** the simulator writes them to disk. It runs as a separate process with minimal CPU and memory usage.

### Can I import old telemetry files?

Yes. During first setup, Capture offers to import iRacing `.ibt` files from the last 7, 30, or 90 days. For LMU, existing `.duckdb` files are detected automatically. You can also process individual files anytime through the [File Manager](/en/docs/capture/file-management).

### Is my telemetry data private?

Yes. Your data is associated with your Braking Lab account and only accessible to you. It's used exclusively to generate your training exercises.

### How much disk space does Capture use?

Capture itself is lightweight (under 50 MB). Telemetry files (`.ibt` for iRacing, `.duckdb` for LMU) are created by the simulator, not Capture. Processed data is small (a few KB per lap) and stored locally until synced.

### Can I use Capture without a Braking Lab account?

You need an account to sync data to the cloud. Without signing in, Capture can still detect and process files locally, but the data won't be available in the web app.

## Troubleshooting

### Capture Doesn't Detect Any Files

**Symptoms:** The file counter stays at zero even after completing sessions.

**For iRacing:**

1. **Verify telemetry export is enabled** in iRacing (Options > Misc > Save telemetry data to disk). See [iRacing Setup](/en/docs/capture/iracing-setup) for details.
2. **Complete a session** — iRacing only writes the file when the session ends or you exit.
3. **Check the telemetry folder** manually at `C:\Users\<YourName>\Documents\iRacing\telemetry\` — are `.ibt` files there?

**For Le Mans Ultimate:**

1. **Verify telemetry recording is enabled** in LMU (Settings > Gameplay > Record Telemetry). See [LMU Setup](/en/docs/capture/lmu-setup) for details.
2. **Complete a session** — LMU writes the `.duckdb` file after the session ends.
3. **Check the telemetry folder** at `C:\Users\<YourName>\Documents\Le Mans Ultimate\Telemetry\`

**General:**

1. **Restart Capture** — The file watcher reinitializes on launch.
2. **Check if capture is paused** — Look for the "Paused" state indicator.

### Files Stuck in "Processing"

**Symptoms:** A file shows "Processing" for an unusually long time.

**Solutions:**

1. **Wait** — Large files with many laps can take longer.
2. **Restart Capture** — If stuck for more than a few minutes, restart the app. The file will be reprocessed.

### Files Stuck in "Syncing"

**Symptoms:** Files show "Syncing" but never reach "Synced".

**Solutions:**

1. **Check internet connection** — Sync requires an active connection.
2. **Check authentication** — You may need to re-sign in. Look for a re-authentication prompt.
3. **Check the Errors tab** in the File Manager for specific error messages.
4. **Restart Capture** — Forces a fresh sync attempt.

### Parse Error on a File

**Symptoms:** A file shows "Parse Error" status.

**Causes:**
- The session was very short (no completed laps)
- iRacing crashed mid-session, corrupting the file
- The file was incomplete (still being written)

**Solutions:**

1. **Retry** — Select the file and click Retry Parse. Sometimes a second attempt succeeds.
2. **Skip** — If the file consistently fails, skip it. Short or corrupted sessions often lack useful data.

### Authentication Keeps Expiring

**Symptoms:** Frequent prompts to re-sign in.

**Solutions:**

1. **Check internet stability** — Token refresh requires an active connection.
2. **Sign out completely** and sign in again from scratch.
3. **Check your Braking Lab account** is active and in good standing.

### App Won't Start

**Symptoms:** Capture crashes on launch or shows an error.

**Solutions:**

1. **Restart your PC** — Clears any locked resources.
2. **Run as Administrator** — Right-click the shortcut and select "Run as administrator".
3. **Reinstall** — Download the latest installer and install again. Your settings and processed data are preserved.
4. **Check Windows version** — Capture requires Windows 10 or later (64-bit).

### Data Not Appearing in Web App

**Symptoms:** Files show "Synced" in Capture but don't appear in the web app.

**Solutions:**

1. **Refresh the web app** — New data may take a moment to appear.
2. **Check your account** — Make sure you're using the same account in Capture and the web app.
3. **Check My Laps** — Data appears in the [My Laps](/en/docs/features/my-laps) section, filtered by track and car.

### Connection Keeps Dropping

**Symptoms:** Connectivity indicator flickers between online and offline.

**Solutions:**

1. **Check your network** — Run a speed test or try other internet-dependent apps.
2. **Firewall rules** — Ensure Capture is allowed through your firewall.
3. **VPN conflicts** — If using a VPN, try disabling it temporarily.

## Getting Help

If your issue isn't covered here:

- Check the [Braking Lab documentation](/en/docs/getting-started/introduction) for general app questions
- Reach out through the Braking Lab community for support