Bugs & Issues – Overview & How to Report (Unofficial)
This unofficial page explains how we track RaceLab problems from the community, what counts as a bug, and how to send reports that are actually useful for developers and support.
- Overview: what this Bugs & Issues section covers.
- What it isn’t: not an official support channel or guarantee of fixes.
- How to report: simple checklist you can follow in Discord or email.
Scope
1. What this Bugs & Issues section is for
- Collects real problems seen by RaceLab users across all sims.
- Groups issues by feature (overlays, telemetry, subscriptions, etc.) and by game.
- Summarises what is known, under investigation or fixed in recent versions.
- Provides workarounds and tips where possible, so people can keep racing.
- Helps you avoid answering the same questions from scratch every week.
Tip: When a user says “RaceLab is broken”, start here, then jump to
Bugs by Game, Bugs by Feature or the current Quarterly report for detail.[1]
Not official
2. What this page is not
- Not an official RaceLab support or ticket system.
- Not a promise that any specific bug will be fixed by a certain date.
- Not a place to share account details, payment data or private logs publicly.
- Not a replacement for reading the in-app release notes or roadmap.
- Not a general PC help desk – problems clearly outside RaceLab belong elsewhere.
Important: Everything here is maintained in good faith by the community.
Information may lag behind the very latest RaceLab or sim updates. Always check in-app update notes for breaking changes.[2]
How to report
3. How to report a RaceLab bug clearly
- Describe the problem: one or two sentences – what went wrong, not just “it broke”.
- Which sim & session: e.g. iRacing – official race, ACC – practice, LMU – 1.2, etc.
- RaceLab info: RaceLab version, overlays in use, and whether you were streaming or in VR.
- Steps to reproduce: simple numbered steps to trigger the problem again if possible.
- What you expected: what should have happened instead of the broken behaviour.
- Extra helpful data: screenshot, short video, or relevant log snippet if available.
Tip for Discord replies: ask users for “Sim + session type, RaceLab version,
overlays used and a short step-by-step of what happened” before you decide if it’s a bug or a setup issue.[3]
Once a report is clear, file it under the right place: Bugs by Game, Bugs by Feature, a detailed Bug Detail page, and eventually into the next Quarterly Bug Report.
Is it a bug, a setup issue, or something else?
Before filing a bug, run through this quick check. Many “bugs” turn out to be configuration, sim limitations or problems outside RaceLab. Clear reports save everyone time and help real bugs get fixed faster.
Bug or config?
1. Quick checklist – is it really a bug?
- Does it happen every time you repeat the same steps?
- Yes → more likely a real bug.
- No → might be performance, network or rare edge case.
- Does the sim behave normally without RaceLab?
- Yes, only broken with RaceLab → log it here.
- No, broken even without RaceLab → sim or PC issue, note it but don’t call it a RaceLab bug.
- Have you tried the basic checks?
- RaceLab up to date?
- Sim version up to date?
- Telemetry / ports / plugins configured correctly?
- Is it clearly a missing feature?
- “I wish RaceLab did X” → that’s a feature request, not a bug.
- If still unsure, treat it as a bug but clearly mark it as “Needs confirmation”.
Important: Never share passwords, payment info or private log files in public bug reports.
Keep sensitive details in direct messages if they are needed at all.[2]
Where to report
2. Where to send your bug report
- First stop – community help: share a short version of your report in the appropriate RaceLab or sim Discord channel.
- If other users confirm the behaviour, add it to:
- Bugs by Game (if clearly tied to one sim), and/or
- Bugs by Feature (if clearly overlays, telemetry, subscriptions, etc.).
- For high-impact bugs (crashes, data loss, broken overlays in major events), create a dedicated Bug Detail page using your template.
- Summarise the most important open issues in the next Quarterly Bug Report.
- If the bug is time-sensitive (major sim update, big league event), highlight it at the top of the relevant bug page with a short notice.
Tip: When replying in Discord, you can link people straight to the
matching game or feature page in this Bugs section so they see current status and workarounds.[1]
What happens next
3. After reporting – expectations & status
- Initial triage: your report is checked against existing bugs, and placed under the right category.
- Status set: Open, Under Investigation, Fixed, Deferred, or Not a Bug (see the Bugs by Feature page for the full status key).[1]
- Workarounds: where possible, a temporary fix or workaround is documented on the relevant page.
- Fixes: when a developer fix ships, the bug entry is updated with:
- RaceLab version that includes the fix, and
- any sim version dependency (e.g. “requires LMU 1.2+”).
- Quarterly summary: the most important changes and resolved issues are rolled into a quarterly report so you can see progress over time.
Tip: If you share bug links with users, always mention the current status
so they know whether it’s being worked on, already fixed, or considered low priority.[3]
Sources & references
- Structure of this Bugs section (Bugs by Game, Bugs by Feature, Bug Detail pages and Quarterly Reports) and how they link together for RaceLab users. ↩ back
- Community best practice for safe bug reporting – avoiding sensitive data in public channels and focusing on clear, repeatable steps. ↩ back
- Common lifecycle for software issues (report, triage, status, fix, summary) adapted for this unofficial RaceLab support site. ↩ back