Quick triage – is this an LMU bug, a RaceLab bug, or something else?
Use this panel as a fast checklist before you post a bug report. It helps you send your issue to the right place and include the details the devs actually need.
1. Does LMU misbehave without RaceLab?
- Close RaceLab and any other overlays / plugins completely.
- Restart LMU and join the same type of session (offline / RaceControl).
- If the stutters, freezes, or HUD problems still happen, treat it as a core LMU issue. [1]
- If the problem only appears when RaceLab is active, continue below.
2. Is it linked to overlays / data connection?
- In RaceLab, confirm LMU is selected as the active sim and a layout is chosen.
- Load into the car in LMU, then press Start layout in RaceLab.
- Use borderless or windowed mode rather than exclusive fullscreen for overlays.
- Check that no other app is using the same overlay / telemetry port.
- If symptoms follow a specific layout or overlay, log it as a RaceLab overlay / LMU integration bug. [3]
3. Could it be performance, triples or VR?
- Test with plugins and overlays disabled to see if stutters disappear. [2]
- Lower graphics settings and test with fewer AI, especially on triple screens or VR.
- Try borderless window instead of exclusive fullscreen on multi-monitor setups.
- Monitor CPU/GPU usage and VRAM to see if you are hitting a performance limit.
- If performance issues improve when plugins / overlays are removed, treat it as a performance / configuration issue rather than a pure LMU or RaceLab bug.
Before posting your report
- Write a short, clear title – e.g. “LMU – RaceLab overlays cause stutter after 5–10 laps”.
- Include your PC specs (CPU, GPU, RAM), monitor layout (single / triple / VR), and wheel base.
- State whether the session was offline, RaceControl daily race, or custom server.
- Mention the exact LMU build and RaceLab version you are running. [4]
- Attach at least one screenshot or a short clip showing the overlays and the issue.
- List what you have already tried (restarts, different tracks, disabling plugins, changing graphics, etc.).
Sources & References
- Official Le Mans Ultimate known-issues lists, support articles and forum “Known Issues” threads for current LMU bugs. ↩ back
- Le Mans Ultimate performance guidance and community reports where plugins and overlays affect FPS and stability. ↩ back
- RaceLab LMU integration notes and community bug reports about overlays not showing or tracking the wrong driver. ↩ back
- LMU and RaceLab release notes (version numbers, recent changes and temporary compatibility issues). ↩ back
Quick triage – is this an rFactor 2 bug, a RaceLab bug, or something else?
Use this panel as a fast checklist before you post a bug report. It helps you send your issue to the right place and include the details devs and helpers actually need.
1. Does rFactor 2 misbehave without RaceLab?
- Close RaceLab and any other overlays / plugins completely.
- Restart rFactor 2 and join the same car / track / session type.
- If the crashes, stutters or HUD problems still happen, treat it as a core rFactor 2 issue. [1]
- If the problem only appears when RaceLab is active, continue below.
2. Is it linked to plugins, HUDs or data?
3. Could it be performance or content related?
- Test on an official car and track with fewer AI before blaming RaceLab.
- Lower graphics settings and shadows, especially on older or heavy content.
- Monitor CPU / GPU usage and VRAM while driving.
- If FPS and stutters improve when plugins / overlays are removed, treat it as a performance / configuration issue rather than a pure RaceLab or rF2 bug.
Before posting your report
- Write a short, clear title – e.g. “rF2 – RaceLab overlays freeze when session advances to race”.
- Include your PC specs (CPU, GPU, RAM), monitor setup (single / triple / VR) and wheel base.
- State whether the session was offline, official online, league server or modded server.
- Mention the exact rFactor 2 build and RaceLab version you are running. [4]
- Attach at least one screenshot or a short clip showing the overlays and the issue.
- List what you have already tried (restarts, disabling plugins, different content, graphics changes, etc.).
Sources & References
- Official Studio 397 / rFactor 2 release notes, known-issues posts and support information. ↩ back
- rFactor 2 plugin and HUD configuration guides explaining how to enable / disable plugins safely. ↩ back
- RaceLab documentation and community reports on rFactor 2 plugin behaviour and overlay issues. ↩ back
- Recent rFactor 2 and RaceLab patch notes that can temporarily affect plugins, HUDs or data output. ↩ back