I looked at 345 bug-related messages and classified each into one main topic based on the wording (overlay, FFB, FPS, login, etc).

1. Overlays / widgets / HUD

~131 reports (biggest bucket)

Typical issues:

• Overlays not appearing in iRacing even though Racelab is connected.

• Overlays freezing (data stops updating mid-session).

• Layouts or widgets moving on their own (often linked to the Windows taskbar bug).

• Track map / layout alignment issues; wrong or offset track map; layout not matching actual circuit.

• Difficulty getting overlays set up or visible without other apps on top.

Examples (paraphrased):

• User says layouts don’t seem universal and some tracks show the map way off to one side.

• Several reports that overlays move position after a while, often blamed on the Windows taskbar bug.

• Overlays or specific widgets (e.g. track map, relative, etc.) appear but freeze and stop providing live data.

2. Performance / stutters / FPS

~22 reports

Typical issues:

• iRacing (or other sim) lagging or stuttering only when Racelab is active.

• Clean telemetry when Racelab has focus, but lag when the sim is in focus.

• Telemetry / overlay working for one session and then stopping or freezing on later sessions.

• FPS drops that appear tied to hardware acceleration or particular settings.

Examples:

• User shows a video: telemetry looks fine when Racelab is frontmost, but when iRacing is on screen the sim lags.

• Telemetry only works correctly for the first session, then stops or freezes afterward.

• Another user fixes FPS issues by disabling hardware acceleration in Racelab.

3. Force feedback / wheel behaviour

5 reports (but very serious when they happen)

Typical issues:

• FFB goes weird, inconsistent or cuts out only when Racelab is running.

• Wheel briefly loses force or pulls the wrong way for split seconds.

• FFB going “dead” as soon as Racelab starts or connects.

• Interactions with other FFB-related tools (e.g. MAIRA) while Racelab is running.

Examples:

• “When Racelabs is running, my force feedback is inconsistent and odd; it loses force or veers the opposite direction briefly. Close Racelabs and it’s instantly fine.”

• Another user: “My FFB goes dead the second Racelabs is started.”

• Report about running Racelab alongside another FFB app and seeing strange wheel behaviour.

4. Account / subscription / billing / login

~22 reports

Typical issues:

• Paid for a subscription (often yearly) but app still shows Free.

• Can’t log in; stuck on a web page or error page.

• Confusion about which email/account is tied to the subscription.

• Users being directed to contact support via email.

Examples:

• User: “I signed up for a one-year subscription but my account still appears as Free in the app.”

• Another: “I can’t log in; I just get dumped on a certain site and can’t proceed.”

• Replies pointing them to email support@racelab.app with details.

5. Install / update / startup / crashes

~21 reports

Typical issues:

• Racelab not starting properly, or closing unexpectedly.

• Needing to reinstall or roll back to an older version to fix behaviour.

• After an update, certain features or connections (e.g. LMU, heart rate, telemetry) stop working.

• Launcher behaviour or app not connecting to sim after fresh install.

Examples:

• “I’ve reinstalled a few times but the problem is still there.”

• “New install seems to have fixed it – older one had become weird.”

• After updates, LMU or other sim connections no longer work the same.

6. Configuration / settings

~12 reports

Typical issues:

• Confusion between a setting issue vs. a real bug (e.g. custom offsets, layout config).

• Needing to use specific layouts (e.g. dual-PC streaming layouts) for things to behave.

• Wheel/overlay behaviour that turns out to be misconfigured profiles or wrong options.

Examples:

• A user reports a “bug” with a layout, and another replies “That’s not a bug, it’s a setting issue – you should use custom offset / correct layout.”

• Advice like “Use the dual-PC streaming layout to avoid this problem.”

• Users adjusting hardware acceleration or specific toggles to resolve their issue.

7. Heart rate / wearables

2 reports

Typical issues:

• Heart rate captured by the watch/app, but not displayed in the overlay.

• Happens even after following the documented setup steps.

Examples:

• “I have a problem with heart rate not working. My watch shows HR normally, but it is not displayed in the overlay.”

• “I did everything as described, but it still doesn’t work. I use an Apple Watch.”

8. OBS / streaming integration

~6 reports

Typical issues:

• Overlays disappearing or moving when OBS triggers a scene transition.

• OBS browser sources not refreshing correctly after updating tokens.

• Layouts needing to use the “dual-PC streaming” version to work as expected.

Examples:

• After a stream ends and the next one starts, the overlay moves again and doesn’t stay where it was.

• “It was working and now when I put in the new access token my source stays on the default image / doesn’t update.”

• User notes they solved an issue by switching to the dual-PC streaming layout.

9. LMU-specific issues

8 reports

Typical issues:

• LMU install paths or detection being wrong.

• LMU support temporarily broken by updates, then partially restored.

• Spectator mode events not being recognized correctly.

Examples:

• “Your LMU install is wrong, have you asked in an LMU server?”

• Dev messages explaining that recent updates didn’t break LMU, but they can reproduce and investigate issues.

• “Little bug with LMU spectator mode – events are not recognized.”

10. Other / uncategorized

~116 reports

These are mixed, including:

• One-off problems that were quickly resolved (“issue solved by user”, etc.).

• Feature requests that contain words like “issue” or “problem” but aren’t really bugs.

• Short, vague “doesn’t work” messages without enough context to safely categorize.

• Conversations that mix troubleshooting, fixes and “it’s fine now”.
  

Structured RaceLab Bug Report List

Summary

• Most common themes: Overlay rendering problems, VR synchronization, UDP telemetry changes, startup/initialization issues.

• Potentially related to your FFB issue:

  • Items 16, 17, 18, 19 — if VR or overlay layers are malfunctioning, they can interfere with USB/HID priority or driver timing.

  • RaceLab uses background telemetry hooks that can temporarily block input polling — this could explain your intermittent FFB dropouts.