Join the Discord! →

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


Iracing Frame Rate Limiter Settings

Confused by iracing frame rate limiter settings? This guide for iRacing drivers shows the best cap for your monitor or VR and quick steps to fix stutters.

If you’re stuck on iracing frame rate limiter settings, the fast fix is this: cap your FPS a few frames below your display’s refresh rate and don’t run “No Limit” in races. That stabilizes frame times, reduces stutter, and keeps input responsive. You’re in the right place—here’s the simple setup.

Quick Answer: iracing frame rate limiter settings

Set iRacing’s Max Frame Rate to just under your screen’s refresh (e.g., 58 for 60 Hz, 142 for 144 Hz, 162 for 165 Hz, 238 for 240 Hz). Use G‑Sync/FreeSync if you have it and keep V‑Sync off. Avoid “No Limit” during racing to preserve CPU/GPU headroom and smoothness.

What’s Really Going On

The frame rate limiter caps how many frames iRacing draws. Without a cap, your GPU can run at 100%, causing spikes, heat, and stutters when action gets heavy. A smart cap:

  • Keeps frame times even (smoother motion and steadier steering feel)
  • Leaves headroom so big packs, smoke, and night tracks don’t tank your FPS
  • Reduces input latency compared to using V‑Sync alone

If you have a variable refresh display (G‑Sync/FreeSync), the best experience is VRR on + an FPS cap slightly below refresh.

Step-by-Step Fix

  1. Open iRacing > Options > Graphics. Find “Max Frame Rate.”
  2. Pick a cap near your refresh:
    • 60 Hz: 58 FPS
    • 120 Hz: 118 FPS
    • 144 Hz: 141–142 FPS
    • 165 Hz: 162–163 FPS
    • 240 Hz: 237–238 FPS
    • VR: Match your headset refresh (e.g., 90) or its half‑rate if needed.
  3. Set sync correctly:
    • G‑Sync/FreeSync displays: enable VRR in your GPU control panel, turn V‑Sync OFF in iRacing.
    • No VRR: if tearing bothers you, turn V‑Sync ON and cap at your refresh; if you prefer lowest latency, V‑Sync OFF and accept minor tearing.
  4. Test in a “worst case”: busy session, night, many cars. If FPS dips under the cap, reduce heavy settings (shadows, mirrors, reflections, number of visible cars) or drop the cap one step.
  5. Use one limiter only. Pick iRacing’s cap OR a driver/RTSS cap—don’t stack them.

Extra Tips / Checklist

  • Don’t race with “No Limit.” It’s fine for quick tests; it risks stutter under load.
  • Aim for 10–20% GPU headroom in heavy traffic. If usage is pegged at 99%, lower a couple settings or reduce the cap slightly.
  • Triple screens/VR: mirrors, shadows, and reflections hit performance hardest—tune these first.
  • Nvidia: enable G‑Sync for fullscreen (and windowed if you use borderless). AMD: enable FreeSync. Keep iRacing V‑Sync off with VRR.
  • If you still see spikes, try an external cap (RTSS) at refresh‑2 FPS and leave iRacing at “No Limit”—but only use one limiter at a time.

FAQs

  • What’s the best value for a 144 Hz monitor? Set 141–142 FPS. It stays just under refresh, keeping frame times smooth without overloading the GPU.

  • Should I use V‑Sync in iRacing? Only if you don’t have G‑Sync/FreeSync and tearing bothers you. V‑Sync can add input lag. With VRR, leave V‑Sync off and use a cap.

  • Is the in‑game limiter or RTSS/Nvidia better? Both work. RTSS can give very steady frame pacing. Use whichever is simpler for you, but don’t use two caps at once.

  • My FPS still dips below the cap—why? You’re CPU/GPU limited in heavy scenes. Lower mirrors, shadows, reflections, and “Max Cars,” or reduce your cap a few FPS.

Short Wrap-Up

Cap FPS just under your display’s refresh, use VRR if you have it, and avoid “No Limit” during races. Test in busy sessions, tune mirrors/shadows, and keep one limiter active. You’ll get smoother motion and steadier control, lap after lap.