Join the Discord! →

Join hundreds of racers just like you! We love to help answer questions and race together.


Iracing Fps Drops When Cars Are Around

iracing fps drops when in traffic? This direct guide for iRacing drivers shows why it happens and the exact settings to fix it fast.

If you’re seeing iracing fps drops when cars are around, you’re usually CPU‑limited by opponent cars, mirrors, and lights. The fix: cap your FPS, lower the “Max Cars” and opponent details, and trim shadows/reflections. You’re in the right place—let’s sort it in a few minutes.

iracing fps drops when cars are around: Quick Answer

Crowds of cars spike CPU and GPU load (paints, headlights, mirrors, smoke). Lower Max Cars and opponent detail, reduce mirror detail, cap FPS, and turn down shadows/reflections. Use iRacing’s frame-time meter to see if you’re CPU or GPU limited, then tune the right settings.

What’s really going on

iRacing is heavy on the CPU. When you join a pack, the sim has to draw many car models, update their reflections, handle headlights, render mirrors, and process particles (smoke/dirt). That pushes the main thread hard and can also hit the GPU. The result: FPS drops and stutters in traffic even if hotlapping feels smooth.

Use Ctrl+F in-session to show the performance meter. If the sim/CPU bar spikes near the limit in traffic, you’re CPU-bound. If the render/GPU bar spikes, you’re GPU-bound. Tweak the matching settings below.

Step-by-step fix

  1. Identify the bottleneck
  • On track, press Ctrl+F. Note whether the CPU (sim) or GPU (render) bar spikes when you’re in a pack.
  1. If CPU-bound: cut opponent load
  • Options > Graphics:
    • Max Cars: drop to 20–30.
    • Opponent Car Detail: Medium or Low.
    • Mirrors: disable “Higher detail in mirrors,” reduce mirror distance, or disable extra mirrors you don’t need.
    • Pit objects / Crowds / Grandstands: Low or Off.
    • Optional: uncheck loading custom opponent paints/textures to avoid VRAM/CPU spikes as cars appear.
  1. If GPU-bound: trim expensive visuals
  • Anti-aliasing: reduce level; avoid supersampling.
  • Shadows: Low or Off.
  • Reflections (cars/track): Low or Off.
  • Headlights/number of lights: reduce, especially for night racing.
  • Particles (smoke/dirt): Medium or Low.
  • Resolution scale: 100% or slightly below if needed.
  • Turn off post effects you don’t need (bloom/motion blur/SSAO if present).
  1. Cap your frame rate
  • Set iRacing’s frame rate limit a bit under your typical in-traffic FPS (e.g., 84 for 90 Hz, 118–120 for 120/144 Hz). This stabilizes frame times and reduces spikes.
  1. Test in a worst-case
  • Load a practice with a big grid at a night track. Drive in the pack and watch the meter. Adjust one notch at a time until it’s stable.
  1. Optional: use upscaling if available
  • If your build shows DLSS/FSR, enable it and choose a balanced/performance mode to offload the GPU without hammering the CPU.

Extra tips / checklist

  • Night races are heavier. Lower headlights and shadows more at night.
  • VR users: reduce pixel density slightly, cut mirrors and opponent detail first.
  • Close background apps (browsers, overlays), set Windows power plan to High Performance, and keep GPU drivers up to date.
  • If you stream/record, try a GPU encoder (NVENC/AMD) and cap FPS to avoid CPU spikes.
  • Big liveries can stutter when new cars load. Disabling custom paints helps consistency.

FAQs

  • Why is FPS fine alone but bad in races? Traffic adds many cars, lights, mirrors, and particles. That spikes CPU and GPU load compared to hotlapping.

  • Should I upgrade CPU or GPU? If pack racing tanks FPS and CPU pacing spikes, a faster CPU (especially single-core speed) helps most. If shadows/AA/reflections tank FPS, upgrade the GPU.

  • What FPS cap should I use on 144 Hz? Try 118–120. Prioritize stable frame times over chasing the max refresh number.

  • Does ping or netcode affect FPS? No. Network affects rubber-banding, not frame rate. FPS is tied to your PC’s CPU/GPU load and settings.

Short wrap-up

Most “cars nearby” FPS drops come from CPU pressure and mirrors/lights. Lower Max Cars and opponent detail, trim mirrors/shadows/reflections, and cap FPS. Test in a big field, then lock it in before race night.