Where: Sessions export actions, Diagnostics export and this Help Center’s feedback form.
How to use it
- Core telemetry travels over your reachable local network and is processed on the Android device. Session summaries, available detailed traces, labels and learned local information stay there unless you export/share.
- Discord is optional and external. Generated engineer audio and necessary Discord connection metadata go to that service when you use it; the core does not gain a LapMind telemetry cloud account.
- Use the support email or feedback form below. The form prepares a draft in your own email application; it sends nothing until you review and send.
- Describe version, device, console, race context, settings, expected versus observed behaviour and approximate time. Start with a text-only report.
- Do not include bot tokens, personal passwords, real console IPs or private captures in public reports. Agree a private transfer before sending a diagnostics or Session package.
Options and defaults
This workflow uses the explicit actions described above; it introduces no additional saved setting or automatic default.
Operating principle and expected output
No analytics, tracking or remote search service is added by this manual. Search runs in your browser over the delivered article index. No microphone access is requested by LapMind’s Discord route.
When output is absent or limited
Beta37 is a development candidate, not released Public Beta. Image captions distinguish OWNER device screenshots, emulator captures and renderer-only views. None alone proves GT7 timing, headset mixing or sustained runtime performance.
Related manual and troubleshooting
- 5 Hz support recorder
- Discord saved setup, automation, privacy and disconnect
- Export, Backup all and Import/restore