Repository navigation
SlotForge Telemetry 0.8.0
SlotForge Telemetry 0.8.0 brings lap analysis to everyone—with or without Paddock.
What's new
- Enter your own laps. Paste times from another timer or notebook, review them, mark invalid/pit laps and save a session with car, track, driver and optional setup details. Seconds, decimal commas, minutes:seconds and milliseconds are supported.
- Manage a manual lap library. Edit, delete, back up and restore sessions. Manual entries remain clearly labelled and separate from Paddock imports. Damaged libraries can be recovered from a validated backup while retaining the original.
- Go deeper into each run. Focus on a stint, inspect exclusions, compare opening and closing pace, and find the best consecutive five-lap sequence. Manual sequences require your confirmation before consecutive-lap metrics are used.
- Compare and track progress. Keep the simple comparison table or open a lap-progression overlay. Progress follows a car's runs on the same track and lane, with minimum-lap filters and recorded setup differences.
- Share clear reports. Export a self-contained HTML comparison with results, context, setup differences and provenance. Open it in a browser to read or print.
The setup calculator, saved configurations, themes, calculation reference and Paddock imports remain available. Paddock integration uses its existing supported host API; no new host API is required for these features.
Choose your download
| Computer | File in Assets |
|---|---|
| Windows, 64-bit Intel/AMD | SlotForgeTelemetry-0.8.0-windows-x64-Portable.exe — save, then double-click. |
| Apple Silicon or Intel Mac | SlotForgeTelemetry-0.8.0-mac-universal.dmg — open and drag into Applications. The ZIP contains the same app. |
| Ubuntu / Debian / Mint, x64 | SlotForgeTelemetry-0.8.0-linux-amd64.deb — open with your software installer. |
| Other Linux desktops, x64 | SlotForgeTelemetry-0.8.0-linux-x86_64.AppImage — allow execution in Properties, then open. |
No Terminal, Node.js or coding is required for the packaged apps. GitHub's Source code archives are for developers. SHA256SUMS.txt contains download integrity checksums.
Installation guide · Manual lap entry and Paddock guide
Updating and getting started
Back up your saved setup library and any manual laps, close the old app, then open the new version. Existing profiles, setups, themes and Paddock imports are retained.
For manual laps, choose Analyze → Lap analysis → Add lap data. Manage entries in Library → Race results. Use Analyze → Progress to follow multiple saved runs, or Compare runs → Export comparison report to share a comparison.
Review and reliability
The review repaired pit/invalid flag preservation during time corrections, manual-library recovery, numeric validation, rounded-zero comparison colours and source labels. It also resolved the earlier build-dependency advisory; a clean installation reported zero npm audit vulnerabilities.
Local verification passed 88 tests, all six Windows desktop workflow checks and Windows portable packaging. Release packages are built on their native GitHub Actions runners. Interactive Linux/macOS desktop and real two-computer LAN testing remain outstanding.
Manual entries are user-supplied evidence, not verified Timing captures. Consecutive metrics need a known sequence; pit/invalid laps and missing lap numbers break it. Comparisons describe observations and do not prove that a setup change caused a performance difference.
Windows is unsigned. macOS is ad-hoc signed, not Developer ID signed or notarized. See the installation guide for first-launch prompts.