![]() |
Created by Scottozy
22-11-25
I looked at 345 bug-related messages and classified each into one main topic based on the wording (overlay, FFB, FPS, login, etc).
~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.
~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.
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.
~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.
~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.
~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.
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.”
~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.
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.”
~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”.
| ID | Title / Category | Description & Symptoms | Possible Cause / Notes | Source |
|---|---|---|---|---|
| 1 | Delta Bar RF2 Bugs | Delta bar in rFactor 2 goes out of sync between “personal best” and “session best” after a new lap. | Likely error in the delta calculation logic for RF2 telemetry. | https://roadmap.racelab.app/feedback/120001 |
| 2 | Delta Bar Counting Invalid Laps | Delta bar stores invalid laps as valid, corrupting the delta data. | Incomplete evaluation of the lap legality flag. | https://roadmap.racelab.app/feedback/88453 |
| 3 | Relative & Fuel Calculator Issues | Standings positions are wrong, fuel consumption per lap is overestimated. | Bad telemetry synchronization or a bug in the averaging calculation. | https://roadmap.racelab.app/feedback/86764 |
| 4 | Track Map Inaccuracy | Cars are shown on the track map about one corner behind their actual position. | Outdated sampling rate for car position. | https://roadmap.racelab.app/feedback/97376 |
| 5 | Blind Spot Overlay Not Working (iRacing) | Radar does not light red/yellow for nearby cars. | Incorrect mapping of API signals or overlay bug. | https://roadmap.racelab.app/feedback/180663 |
| 6 | Disappearing Overlays | All overlays flicker or disappear mid-session. | Memory leak or GPU overlay surface resets. | https://roadmap.racelab.app/feedback/94886 |
| 7 | Flag Overlay Issue | Race flags are not shown or get stuck. | Rendering order or texture refresh bug. | https://roadmap.racelab.app/feedback/97000 |
| 8 | F1 25 UDP / VR Overlay Conflict | F1 25 UDP protocol interrupts the VR overlay connection. | New telemetry format is not compatible with the RaceLab UDP handler. | https://roadmap.racelab.app/feedback/218558 |
| 9 | Race Event Popup Annoyance | Popup keeps reappearing after being closed. | Setting is not saved; UI flag is not stored permanently. | https://roadmap.racelab.app/feedback/245480 |
| 10 | iRating Graph Flatlines | Unranked races “mess up” the iRating graph view. | Incorrect data type handling (races with “ranked = false” are not excluded). | https://roadmap.racelab.app/feedback/200415 |
| 11 | Overlays Invisible in Fullscreen | Overlays disappear in fullscreen mode but are visible in windowed mode. | Windows fullscreen layer blocks overlay draw calls. | https://www.reddit.com/r/iRacing |
| 12 | Black Overlay Backgrounds / Blurriness | Black boxes or blurry overlays after an update. | Bug in the transparency buffer or in scaling. | https://www.reddit.com/r/RaceLab |
| 13 | Overlays Move After GPU Driver Update | Overlay positions shift after a GPU driver update. | Resolution or DirectX viewport mismatch. | https://www.reddit.com/r/RaceLab |
| 14 | App Fails to Start | Message “RaceLab could not start properly” appears; blocked by antivirus. | False positive from the virus scanner; RaceLab.exe is moved to quarantine. | https://www.reddit.com/r/RaceLab |
| 15 | Borderless Mode Overlay Failure | Overlays are not rendered in borderless mode. | Hooking limitation in borderless window capture. | https://steamcommunity.com/ |
| 16 | VR Mode Auto-Enabled (“Weird Bug”) | Overlays are mispositioned, triggered by VR mode activating automatically. | Shortcut (CTRL+SHIFT+V) pressed accidentally; setting is not saved. | https://www.reddit.com/r/RaceLab |
| 17 | VR Overlay Offset / “Floaty” | Overlay position drifts in the VR view. | Rounding errors in the OpenVR projection transform. | https://garage.racelab.app/docs/vr/known_issues |
| 18 | AMS2 Crash on Launch | Automobilista 2 crashes when RaceLab overlays are enabled. | RaceLab overlay conflict with the AMS2 DirectX window. | https://www.reddit.com/r/RaceLab |
| 19 | Overlay Requires Restart if App Not Launched First | Overlays do not appear if iRacing is started before RaceLab. | Initialization timing issue (hook only happens after the sim has loaded). | https://www.reddit.com/r/RaceLab |
| 20 | RaceLab Update Loop / Cache Corruption | RaceLab downloads updates again on every launch. | Corrupted cache under AppData\Local\Racelabapps\SquirrelTemp. |
https://garage.racelab.app/docs/troubleshooting |
Description & Symptoms: Delta bar in rFactor 2 goes out of sync between “personal best” and “session best” after a new lap.
Possible Cause / Notes: Likely error in the delta calculation logic for RF2 telemetry.
Description & Symptoms: Delta bar stores invalid laps as valid, corrupting the delta data.
Possible Cause / Notes: Incomplete evaluation of the lap legality flag.
Description & Symptoms: Standings positions are wrong, fuel consumption per lap is overestimated.
Possible Cause / Notes: Bad telemetry synchronization or a bug in the averaging calculation.
Description & Symptoms: Cars are shown on the track map about one corner behind their actual position.
Possible Cause / Notes: Outdated sampling rate for car position.
Description & Symptoms: Radar does not light red/yellow for nearby cars.
Possible Cause / Notes: Incorrect mapping of API signals or overlay bug.
Description & Symptoms: All overlays flicker or disappear mid-session.
Possible Cause / Notes: Memory leak or GPU overlay surface resets.
Description & Symptoms: Race flags are not shown or get stuck.
Possible Cause / Notes: Rendering order or texture refresh bug.
Description & Symptoms: F1 25 UDP protocol interrupts the VR overlay connection.
Possible Cause / Notes: New telemetry format is not compatible with the RaceLab UDP handler.
Description & Symptoms: Popup keeps reappearing after being closed.
Possible Cause / Notes: Setting is not saved; UI flag is not stored permanently.
Description & Symptoms: Unranked races “mess up” the iRating graph view.
Possible Cause / Notes: Incorrect data type handling (races with “ranked = false” are not excluded).
Description & Symptoms: Overlays disappear in fullscreen mode but are visible in windowed mode.
Possible Cause / Notes: Windows fullscreen layer blocks overlay draw calls.
Source: https://www.reddit.com/r/iRacing
Description & Symptoms: Black boxes or blurry overlays after an update.
Possible Cause / Notes: Bug in the transparency buffer or in scaling.
Source: https://www.reddit.com/r/RaceLab
Description & Symptoms: Overlay positions shift after a GPU driver update.
Possible Cause / Notes: Resolution or DirectX viewport mismatch.
Source: https://www.reddit.com/r/RaceLab
Description & Symptoms: Message “RaceLab could not start properly” appears; blocked by antivirus.
Possible Cause / Notes: False positive from the virus scanner; RaceLab.exe is moved to quarantine.
Source: https://www.reddit.com/r/RaceLab
Description & Symptoms: Overlays are not rendered in borderless mode.
Possible Cause / Notes: Hooking limitation in borderless window capture.
Source: https://steamcommunity.com/
Description & Symptoms: Overlays are mispositioned, triggered by VR mode activating automatically.
Possible Cause / Notes: Shortcut (CTRL+SHIFT+V) pressed accidentally; setting is not saved.
Source: https://www.reddit.com/r/RaceLab
Description & Symptoms: Overlay position drifts in the VR view.
Possible Cause / Notes: Rounding errors in the OpenVR projection transform.
Description & Symptoms: Automobilista 2 crashes when RaceLab overlays are enabled.
Possible Cause / Notes: RaceLab overlay conflict with the AMS2 DirectX window.
Source: https://www.reddit.com/r/RaceLab
Description & Symptoms: Overlays do not appear if iRacing is started before RaceLab.
Possible Cause / Notes: Initialization timing issue (hook only happens after the sim has loaded).
Source: https://www.reddit.com/r/RaceLab
Description & Symptoms: RaceLab downloads updates again on every launch.
Possible Cause / Notes: Corrupted cache under AppData\Local\Racelabapps\SquirrelTemp.
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.
