Repository navigation
FAQ
Back to Home · Install · Troubleshooting
Yes. The telemetry UDP stream is identical on PS4 and PS5. Just set your PS5's IP in the Live Dashboard the same way.
Lap Analyst compares two individual laps in detail: 19 chart groups, sector timing, heat maps, A/B compare, replay, Corners and a Theoretical-best lap. Race Analyst compares two full race sessions side by side, with synced replay, CSV/HTML export, and Corners and Consistency tabs across the whole race.
- FUEL/LAP is the median fuel burn over your last few clean laps. A lap with a refuel, or the laps after a restart, are ignored, so one thirsty lap can't skew it.
- FUEL LAPS is how many laps the fuel you have left will cover.
- FINISH (races only) shows how many laps of fuel you'd have spare, or how far short you are. PIT BY is the lap to come in on to keep half a lap of fuel in hand. Practice and time trial have no race length, so only PIT BY shows there.
- A leading ~ means the figure is based on fewer than 3 laps.
- PACE LOSS is how much slower your recent laps are than your best lap of the stint, TREND is the per-lap change, and TYRES turns that into Fresh / Good / Fading / Worn.
GT7 doesn't send tyre wear at all, so the tyre figures are estimates. Fuel burn-off makes the car quicker as a stint goes on, which hides some wear, so they under-read rather than over-read. A refuel starts a new stint automatically; for a tyre-only stop press [ NEW TYRES ].
Load the lap in Lap Analyst and click Export Lap Card (PNG) in the EXPORT panel. You get a 1200x630 image with the car, track, lap time, headline stats, the speed trace cut into sectors with their times, a speed-coloured track map and the fuel used, ready to post anywhere. In Race Analyst, Export Race Card (PNG) makes the matching card for a race: every lap time with the best highlighted, a track map, stop laps and fuel per lap.
Yes. The Live Dashboard has an optional REC RATE dropdown (10 / 20 / 30 / 60 Hz). It only affects Record Lap / Record Race, and it never invents data between real packets; it just thins samples to the rate you pick. Laps and races recorded at different rates still compare correctly.
GT7's telemetry doesn't report a track ID the way it does a car ID, so TRACE guesses the track from where the lap starts ("Looks like X - use it?", never filled silently; in a race it shows about one lap in, once you cross the start line). A free-typed name would quietly split one track's laps across spellings like "suzuka" and "Suzuka Circuit". The dropdown is a searchable picker seeded from the community gt7info course database (120+ circuits and layouts).
Run add_track.py (or add_car.py) from the Python source download. If you installed with pip, Chocolatey or WinGet, the same tools are gt7telem-add-track and gt7telem-add-car. The entry is saved next to your settings so it survives upgrades, and appears next time you open the Dashboard.
Almost always ~/TRACE/laps, so an upgrade can't wipe them. That covers pip installs, the Python source download, the macOS app, and Chocolatey/WinGet installs. The one exception: a standalone .exe or binary unzipped into a folder you can write to stays portable and creates a laps folder next to itself. Lap Analyst and Race Analyst read from there automatically.
Load a lap in Lap Analyst and click Submit to Leaderboard in the LEADERBOARD panel. Submitting needs a free account (a display name only, no email or password); if you skipped that at first launch it offers to create one right there. It then asks for the PSN name to show on the row (remembered for next time) and submits your car, track, lap time and a compact input trace. You can also browse the leaderboard in any browser at https://gt7trace.netlify.app/leaderboard.
Yes. The leaderboard is public by design, so anyone using TRACE can see the Top-10 for a car and track and download a lap as a ghost. Use a PSN name you're fine having attached to that lap time. Physically impossible times are rejected automatically, and suspiciously fast first times for a car and track are held for manual review before they publish. See https://gt7trace.netlify.app/privacy for exactly what is and isn't collected.
Click Load Community Line in the LEADERBOARD panel to pull a community-average speed/throttle/brake line, computed from the current top-10 laps for your loaded car and track, and overlay it on your own lap. It needs at least one other public submission for that car and track to show anything.
Every Linux release zip is signed with a dedicated GPG key. Get the public key from the repo (gpg-signing-key/trace-public-key.asc), then run:
gpg --import trace-public-key.asc
gpg --verify gt7telem-linux.zip.asc gt7telem-linux.zip
A "Good signature" result confirms the file matches what was built in CI. (GPG will also warn that the key isn't certified by a trusted signature; that's normal for a key you've just imported.)
TRACE.exe isn't code-signed yet, which is expected for an indie tool. Click More info, then Run anyway. TRACE applied for a free certificate through the SignPath Foundation but wasn't approved yet (they want more public adoption first), so it will reapply later. If your antivirus quarantines it, that's a false positive common with PyInstaller-built apps.
Yes. gt7telem-android.apk on the latest release is a standalone phone version of the Live Dashboard, Lap Analyst and Race Analyst. The phone receives your PS5's telemetry over Wi-Fi itself, so no PC is needed. It is sideloaded, not on the Play Store; see Install.
Yes. TRACE.app is built automatically on a GitHub-hosted Apple Silicon runner for every release. On an older Intel Mac, use the pip install or the Python source download.
The GT7 UDP telemetry stream was reverse-engineered by the community, notably Bornhall's gt7telemetry, which worked out the decryption and packet structure. TRACE's core data layer is built on that work.
GT7 only reports a numeric car ID and no track ID at all. Both the car lookup and the TRACK dropdown are sourced from ddm999's gt7info community database.
- Corners (Lap Analyst) finds each corner on the loaded lap and, with Compare on and your PB loaded as lap B, scores it against the same corner on the PB: brake point, minimum speed, throttle-on point and time gained or lost. After each lap, the Dashboard log and this tab name the three corners costing you the most time.
- Corners (Race Analyst) scores every lap of a race corner by corner, with a lap x corner heat-map plus the average per corner. The Corner baseline button switches between the best lap of the race and your saved PB lap for that car and track.
- Theoretical (Lap Analyst) stitches the fastest micro-sector from each of your laps on a car and track into the lap you could drive, and shows which zones hold your best real lap back.
- Consistency (Race Analyst) shows lap-time spread, trend, a 0-100 consistency score and your most and least consistent corners. Pit laps and spins (more than 7% off your best) are left out.
The live gap to the fastest public leaderboard lap for your current car and track. The Dashboard fetches that lap once per car and track per run (a single read-only request) and compares you against it as you drive. It's skipped silently when you're offline or nobody has set a lap. Untick TOP-LAP GHOST to turn the request off.
Yes. Fuel-low and tyre hot/cold alerts on the Dashboard are spoken through your system's voice. It's built into Windows and macOS; on Linux install speech-dispatcher or espeak-ng. If no voice is available it falls back to the alert sound. Untick VOICE ALERTS to mute it, or NOTIFICATIONS to turn off the new-PB and race-end pop-ups and sounds.
Yes. On startup the Launcher asks GitHub whether a newer release exists and shows a small banner if so. That request goes to GitHub only and carries no version, ID or usage data. Untick CHECK FOR UPDATES in the Live Dashboard header to switch it off. See https://gt7trace.netlify.app/privacy for the full details.
The Records link in the Launcher footer opens your best lap for every car and track, built from your saved laps.
Open an issue: https://github.com/ransh2014/gt7telemtrace/issues
Tick AUTO LAP in the Live Dashboard's Preferences row. In time trial, practice and free run it arms Record Lap by itself once you are driving and saves every lap; races already start on their own. It is off by default.
No track was set, so it would have saved as "unknown". The box lists the likeliest tracks first (matched from where the lap started and its length); pick one or save as unknown. TRACE also warns about this when you start recording.
Laps that are too short, never moved, or identical to the lap just saved are refused. For copies that already exist, Lap Analyst's Find Duplicate Laps button moves the extras into a _duplicates folder; nothing is deleted.