Know what’s next.
Browse a timezone-aware LMU schedule, focus on the next race, filter by skill, save favorites, and open the facts behind every event.
Your schedule, setup, and race preparation—organized before the lights go out. GridCue turns scattered race information into one calm, trustworthy place.
Web, iPhone, Android, and an optional Windows companion.
Spa-Francorchamps · 45 min
Sim racing should feel demanding on track—not before you get there.
GridCue brings schedules, eligibility, setups, fuel and tyre planning, reminders, your garage, and community knowledge into a single workflow. Information stays clearly labeled so you can tell what is verified, editorial, unavailable, or still unknown.
Browse a timezone-aware LMU schedule, focus on the next race, filter by skill, save favorites, and open the facts behind every event.
Keep fuel, tyres, setup notes, calendar actions, and reminders together for the exact race revision you are preparing for.
Save the cars and circuits you use, browse moderated setups, and hand approved LMU files to the Windows companion.
Sign in with the same account to view schedules, update your LMU profile, manage your garage, browse setups, and check companion authorizations.
The optional GridCue Companion safely connects your phone to Le Mans Ultimate on your PC.
It discovers a valid LMU installation, accepts only constrained setup files, and puts you in control of every write and launch.
Read the complete companion guide →
Open a short pairing window on your PC, scan a fresh QR code in the mobile app, and approve the device. Identity changes require pairing again.
Select an existing setup folder inside the LMU root. GridCue never guesses a universal path and never writes outside your choice.
Only .svm files up to 2 MiB pass. SHA-256, file length, confinement, no-overwrite, and atomic staging checks run before a setup appears.
GridCue can request LMU launch only after you tap the action. The companion accepts no arbitrary commands, URLs, paths, or arguments.
Store purchase delivery is prepared in the native apps and remains dependent on release activation. The web app shows the server-verified plan attached to your GridCue account.
GridCue labels planned work as planned. No invented launch dates, no pretending a foundation is a finished integration.
Schedules, race preparation, profiles, setups, garage tools, calendar actions, and Windows companion foundations.
Local telemetry session metadata exists today. Deeper Pro analysis remains gated behind verified entitlements and release activation.
A consent-first OAuth and privacy foundation is prepared. A real connection requires an officially registered client and explicit activation.
Simulator selection is prepared for future schedule, garage, and preparation workflows. No live game connection is claimed.
Account preferences can recognize GT7 as planned while product data and console integration remain future work.
The web app brings schedule, garage, setups, LMU profile, and companion authorization surfaces to a larger screen.
GridCue identifies source state and never presents schedule information as official, live timing, registration, or results.
Missing eligibility facts do not silently become permission to race.
The companion handles bounded bytes, not arbitrary paths, URLs, or executables.
Password verifiers are never plaintext, sessions rotate, and account deletion has an explicit cancellable flow.
No. GridCue is an independent sim-racing companion. Editorial schedule facts cite their sources and are not presented as official registration, timing, or results.
Yes. The web app uses the existing GridCue account API. For safety, its refresh credential stays only in memory, so reloading or closing the tab signs you out.
No. Those actions require the paired Windows companion and the mobile app’s device-bound keys. The website can explain the workflow and manage cloud authorization records.
Not yet. The current repository contains an unsigned development foundation and release staging. GridCue will only add a public download after a signed release is genuinely available.
GridCue says so. Current, possibly outdated, and expired states are visually distinct, and the web app avoids calling archived occurrences upcoming.