Game / Sim Area / Feature Issue, Cause & Workaround (Unofficial)
Le Mans Ultimate Overlays / Connection Issue: Some users report they cannot get any RaceLab overlay working with LMU at all – no widgets appear on screen even after enabling layouts and starting sessions.

Likely cause: LMU overlay connection not fully initialised (plugin not active, wrong sim selected in RaceLab, or overlay layout not started). In some cases another app is already using the same port or blocking the overlay window.

Workaround:
1) In RaceLab, make sure LMU is selected as the active sim and a layout is chosen.
2) Start LMU, load a session and get into the car, then press Start layout in RaceLab.
3) Check that no firewall/overlay blocker is stopping RaceLab, and that no other overlay app is bound to the same port.

Status: Open – repeated Discord reports (Sept–Dec 2025).
Le Mans Ultimate Telemetry / Driver Mapping Issue: Overlay shows data for another driver instead of the local player (e.g. wrong speed, lap, or inputs – looks like you are watching someone else).

Likely cause: In some LMU sessions the internal driver index or telemetry mapping can mismatch when spectators / replays / driver swaps are involved. RaceLab may be binding to the wrong car slot if LMU does not clearly expose "player car" first.

Workaround:
• Verify you are actually in the car, not spectating or replaying.
• Leave the session and rejoin, then restart the layout in RaceLab.
• If it persists, switch to a simple test session (single car, no AI) to confirm if the problem is session-specific.

Status: Open – under community observation (multiple reports).
Le Mans Ultimate Layouts Issue: User reports "I don't have a layout in LMU" or the layout list appears empty, even though overlays were working before.

Likely cause: Local layout configuration corruption or the wrong sim/layout profile selected in RaceLab. Occasionally happens after updates or when copying configs between sims.

Workaround:
1) In RaceLab, open Layouts and confirm LMU is the selected sim.
2) Create a fresh simple layout (e.g. relatives + one panel) and save it.
3) Restart RaceLab App and LMU, then try Start layout again.

Status: Open – sporadic reports, usually solved by recreating layouts.
Le Mans Ultimate Timing / Penalties Issue: Reports that penalties or off-track events in LMU can cause RaceLab to mark laps as invalid or treat them incorrectly, even when the sim itself handles them differently. This feels inconsistent and frustrating for users doing hotlaps / practice.

Likely cause: RaceLab currently interprets LMU penalty and track-limits flags in a way that sometimes differs from how LMU classifies the lap. This can be a mismatch between LMU's internal rules and the data exposed to third-party tools.

Workaround: Use RaceLab lap-validity as a guide but confirm best laps directly in LMU's own timing for now. Treat this as a known limitation until LMU/RaceLab alignment improves.

Status: Investigating – based on user feedback in Discord.
Le Mans Ultimate Telemetry / Steering Issue: RaceLab telemetry overlay shows a steering angle that looks different to the in-game wheel / HUD in LMU.

Likely cause: Different steering angle sources (raw wheel input vs. in-car steering, scaling for rotation range, or LMU sending a different reference value than iRacing/ACC). Small differences are expected, but large mismatches could be a bug in how LMU exposes telemetry or how RaceLab reads it.

Workaround: Use the overlay as a relative guide (for smoothness / clipping) rather than an absolute degree matching the wheel. If the difference is extreme, report screenshots and wheel settings so devs can reproduce.

Status: Open – needs more reproducible data.
iRacing Display Mode / Overlays Issue: RaceLab overlay does not appear when iRacing is in true fullscreen. It works in windowed or borderless window mode, but users sometimes see worse performance there.

Likely cause: Like most external overlays, RaceLab relies on the Windows compositor. Exclusive fullscreen bypasses this, so overlays cannot be drawn above the game.

Workaround: Run iRacing in borderless windowed mode at your monitor's native resolution. Recover FPS by tuning graphics options (shadows, mirrors, AA) instead of switching back to exclusive fullscreen.

Status: Limitation – by design, not a pure bug.
iRacing VR / Performance Issue: With RaceLab overlays enabled in VR (e.g. Quest via Virtual Desktop), FPS can drop from ~120–135 fps to ~20 fps. CPU and GPU graphs spike when overlays are turned on, especially with many widgets active.

Likely cause: Overlays are extra Chromium/Electron surfaces rendered on top of the game. VR streaming plus high supersampling and many fast-updating panels can saturate GPU and encoder resources.

Workaround ideas:
• Test with a very simple layout (1–2 panels) as a baseline.
• Reduce VR resolution / supersampling slightly.
• Try RaceLab with hardware acceleration ON vs OFF and compare.
• Close any other overlay/monitoring tools to free GPU/compositor load.

Status: Investigating – based on multiple VR channel reports.
VR – All Sims VR / Overlays / Streaming Issue: Across several sims (iRacing, LMU, ACC, AMS2) users report extra latency or “jitter” in VR when many overlays are active, especially when streaming via Virtual Desktop or similar tools.

Likely cause: Combination of: high-res VR rendering, encoding load, and multiple browser-based overlay windows refreshing many times per second. Small timing differences add up in the VR compositor.

General VR tips:
• Start with a lightweight layout and add panels gradually.
• Prefer wired link or the most stable streaming option where possible.
• Keep driver & GPU software up-to-date and avoid running other heavy overlay tools at the same time.

Status: Ongoing optimisation area – behaviour varies by PC and VR setup.
[Game / Sim] [Area / Feature] Issue: [Short description of what the user sees.]

Likely cause: [What seems to be happening / context.]

Workaround: [Steps users can try right now.]

Status: [Open / Investigating / Fixed (Unofficial) / Limitation]

Note: This list is unofficial and community-maintained (Scottozy). It is based on Discord reports, testing, and (where possible) cross-checking with the official RaceLab Garage and Roadmap.

Bugs & Issues – By Game / Sim (Unofficial)

This page groups RaceLab problems by simulation. Use it when a user says “RaceLab is broken in <sim name>” and you want to see known issues, quirks and current status for that specific title.

  • Per-sim overview: iRacing, LMU, ACC, AC, rF2, AMS2, F1 and other titles.
  • Typical problem types: overlays, telemetry, FPS, VR, streaming.
  • Jump points: each card can link to a more detailed sim-specific bug page.

iRacing

  • Overlays not appearing after alt-tabbing or when using Fullscreen instead of Borderless.
  • Conflicts with in-game black boxes or other third-party overlays.
  • Telemetry gaps or missed laps when network or ports are misconfigured.
  • FPS / stutter around race starts or big grids with heavy layouts.
Tip: Many iRacing issues are a mix of overlays + black boxes + Fullscreen mode. Start by testing in Borderless with a simple layout.[1]

Le Mans Ultimate (LMU)

  • Overlay windows not capturing correctly after major sim updates.
  • Triple-screen projection or HDR interactions causing odd overlay positions.
  • Telemetry / UDP changes between LMU versions breaking existing configs.
  • Performance drops with night/rain and heavy RaceLab layouts running.
Tip: Check LMU version and UDP settings first, then compare behaviour with HDR off and a lightweight RaceLab layout.[2]

Assetto Corsa Competizione (ACC)

  • Overlays not visible or flickering with some Fullscreen / windowed combinations.
  • Stutter in heavy weather or night races when streaming + overlays are both enabled.
  • Telemetry or shared memory changes between ACC builds.
  • Overlay scaling issues at non-standard resolutions or very high DPI.
Tip: Many ACC issues resolve by tuning FPS caps and post-processing before blaming RaceLab overlays.[3]

Assetto Corsa (Classic)

  • Older engine quirks when using CSP/SOL with multiple overlay windows.
  • Window focus issues when swapping between RaceLab and AC.
  • Conflicts with existing HUD apps or other browser-source overlays.
  • Occasional FPS hitches on older CPUs with large grids and heavy layouts.

rFactor 2

  • Plugin not loading or telemetry not updating after sim patches.
  • Overlay capture problems when RF2 runs in certain Fullscreen modes.
  • Performance drops in wet/night conditions with many AI drivers.
  • Port conflicts with other tools using the same plugin or telemetry ports.

Automobilista 2 (AMS 2)

  • Overlays not drawing at expected positions on ultra-wide or triples.
  • Minor delays between RaceLab timing and the in-game HUD.
  • Occasional performance issues when recording or streaming plus overlays.
  • Telemetry quirks after major AMS2 updates.

F1 202x Series

  • Wrong UDP format selected (e.g. 202x vs 2025) causing missing data.
  • RaceLab overlays not updating when game is in menus or paused.
  • Ray-tracing and heavy graphics settings amplifying any overlay performance hit.
  • Occasional port conflicts with other telemetry tools using the same F1 UDP stream.

Other Sims & Tools

  • Less common titles supported by RaceLab or experimental integrations.
  • New sims where telemetry APIs or plugins are still evolving.
  • Conflicts with dashboards, crew chief tools or custom HUD software.
  • “One-off” issues where you still need more reports before patterns emerge.

Each game card can link to a dedicated “Bugs & Issues – [Sim Name]” page or to a filtered view in your quarterly bug reports. Start here when triaging reports that clearly name a sim (e.g. “in ACC” or “in LMU”) and then drill down for details.