Bugs & Issues – iRacing
This page focuses on known and suspected bugs affecting iRacing when RaceLab is in use – crashes, overlays not appearing, odd behaviour with sessions, timing, or performance. It helps you decide whether you are seeing an iRacing bug, a RaceLab bug, or a PC / network issue.
Before you call it a “bug”
- Confirm you are on the latest iRacing build and latest RaceLab version.
- Restart iRacing and RaceLab completely (no background instances left running).
- Test with a simple single-car test session and only the overlays you need.
- Temporarily disable other overlay / telemetry tools to rule out conflicts.
Common symptom categories
- Overlays not loading, misaligned, or stuck on screen.
- Performance & FPS drops when overlays are enabled.
- Timing / results look wrong or do not update.
- Connection issues: stuttering data, freezes, disconnects.
- UI / control quirks: hotkeys not working, windows not saving position.
What to collect for a report
- Short description in plain language – what you expected versus what happened.
- Game, car, track, session type and whether it was official / hosted / test.
- RaceLab version, overlay(s) in use, and streaming / capture software (if any).
- Screenshots or a brief video showing the problem and the overlays on screen.
- Any error pop-ups, logs, or Windows Event Viewer messages you see.
Where to report
For iRacing platform bugs (physics, netcode, service status, content issues), use the official iRacing support channels and forums. [1] For RaceLab-specific bugs that only happen when RaceLab is running, use the RaceLab Discord bug-report channels or open a ticket via the RaceLab roadmap / support tools. [3]
Quick triage – is this an iRacing 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 it happen without RaceLab?
- Close RaceLab completely and restart iRacing.
- Join a similar session with no overlays loaded.
- If the problem still happens, treat it as an iRacing/platform issue. [1]
- If it only happens with RaceLab open, continue below.
2. Is it tied to a specific overlay or page?
- Disable all overlays, then enable one overlay at a time.
- Note which overlay is active when the problem appears.
- Check this site for a matching entry on the relevant overlay page.
- If clearly linked to one overlay, log it as a RaceLab overlay bug. [3]
3. Could it be performance / PC related?
- Monitor CPU & GPU usage, VRAM, and RAM while driving.
- Test with streaming / recording disabled.
- Try a simpler graphics preset or windowed (fullscreen) mode.
- If FPS or stutters improve when RaceLab / other apps are closed, treat it as a performance configuration issue, not a pure bug. [2]
Before posting your report
- Include a short title – e.g. “iRacing – overlays freeze when session advances to race”.
- Paste your PC specs (CPU, GPU, RAM, VR/monitor, wheel base) once in your support thread.
- Attach at least one screenshot or a brief clip showing the problem on screen.
- Mention the exact RaceLab and iRacing versions you are running. [4]
- Tell us what you have already tried (restarts, reinstall, graphics changes, etc.).
Sources & References
- iRacing status & known issues – official iRacing service information and bug tracking. ↩ back
- iRacing performance, graphics and CPU/GPU tuning guides from the official forums and support articles. ↩ back
- RaceLab roadmap / bug tracker and Discord #bugs channels used by the RaceLab dev team. ↩ back
- RaceLab and iRacing release notes (version numbers, recent changes and known temporary issues). ↩ back