Today is the day to get better at Dirt Track racing on iRacing!

Join hundreds of other racers on our Discord!

Recommended Graphics Settings For Iracing Dirt Ovals

Dial in clarity and FPS on dirt. Recommended Graphics Settings For Iracing Dirt Ovals that reveal the cushion, cut input lag, and stop stutters—plus easy presets.

If you can’t clearly see the cushion, the slick patches, or cars through the dust, you’re guessing—on dirt, that’s slow and risky. This guide gives you the Recommended Graphics Settings For Iracing Dirt Ovals so you can read the track, keep stable FPS, and reduce input lag without spending all night tweaking menus.

Quick answer: Aim for stable, low-latency FPS (ideally 120+ on a 144 Hz monitor), VSync off, VRR (G‑Sync/FreeSync) on, cap your frame rate just below refresh, set Track/World detail high, Particles medium, Shadows low, Mirrors low, AA at 2x–4x MSAA + optional FXAA, Anisotropic Filtering 8x–16x, motion blur off, and adjust gamma so slick vs tacky is obvious.

On dirt ovals, your eyes are a setup tool. You need three things:

  • Clarity: See the groove forming, marbles (loose rubber/dirt), and the cushion (the packed ridge up top).
  • Stability: Smooth, consistent frame times—no stutters—so your timing stays precise entering and exiting corners.
  • Low latency: Your inputs should feel immediate when you’re tiptoeing on the edge of grip.

The right settings make shiny slick spots pop, dust readable (not blinding), and the cushion trackable lap after lap. That means fewer “mystery spins,” better throttle control, and smarter line changes as the track evolves.

Step-by-step: Set up iRacing for clear vision and smooth FPS on dirt

Do this once, then fine-tune at a dirt track you actually race (Eldora, Knoxville, Fairbury, etc.).

  1. Run the Graphics Auto Config (baseline)
  • In iRacing, run Auto Config to get a safe starting point based on your hardware.
  • Then apply the changes below.
  1. Sync and frame rate (latency control)
  • Full Screen: On (exclusive fullscreen preferred for lowest latency).
  • VSync: Off (adds lag). If you have G‑Sync/FreeSync, enable VRR in your GPU control panel.
  • Frame Rate Cap: Set just below refresh rate. Examples:
    • 144 Hz monitor → cap at 141–143 FPS
    • 120 Hz → 117–119 FPS
    • 60 Hz → 58–59 FPS
  • If you don’t have VRR, a cap still helps avoid spikes and heat.
  1. Anti-aliasing and texture clarity
  • AA: 2x–4x MSAA. Add FXAA if you still see shimmering fences/wires. Avoid heavy SSAA unless you have plenty of GPU headroom.
  • Anisotropic Filtering: 8x–16x (critical for sharp track textures at shallow angles).
  • Sharpening: Light touch (around 0.3–0.6). Too much makes the slick look like glare and hides detail.
  1. Track/world detail (where the speed lives)
  • Track Detail / World Detail: High (this helps you see ruts, cushion edges, and surface transitions).
  • Objects Detail: Medium.
  • Pit/Grandstands/Crowd/Event: Low (free FPS; they don’t make you faster).
  • Cars: High for your car; Opponents Medium is usually enough.
  1. Particles, dust, and visibility
  • Particle Detail: Medium (you need to see dust without being blinded).
  • Particle Density: Medium.
  • Keep these lower in large fields or on short bullrings where dust is thick.
  • Motion Blur: Off (adds lag, smears visual cues).
  • Bloom/Depth of Field: Off (eye candy only).
  1. Shadows and reflections (big performance swings)
  • Shadows: Low or Off. At night, consider Low to preserve depth perception.
  • Car Self-Shadows: Off or Low.
  • Object/Track Shadows: Off or Low.
  • Reflections/Environment Maps: Off or Low (little value on dirt; saves GPU time).
  1. Mirrors and opponents (CPU savers)
  • Mirror Detail: Low; Mirror Distance: Short.
  • High Quality Mirrors: Off.
  • Number of Cars to Draw: 12–20 in races if CPU-limited; raise in practice if you have headroom.
  1. Color, brightness, and contrast (read the slick)
  • Gamma/Brightness: Start near default (around 2.2). In a test session, adjust so:
    • Tacky dirt looks matte/dark.
    • Slick looks shiny and brighter, but not blown out.
    • You can still see tire tracks and marbles in the mid-groove.
  • Night races: Small bump in brightness can help; avoid washing out the slick’s shine.
  1. Test properly (don’t tune in a vacuum)
  • Join a dirt practice with a full field and varied track states.
  • Press Ctrl+F to watch FPS; your goal is stable, not just “high.”
  • If you stutter when packs of cars slide by, lower Opponent Detail or Number of Cars, then Shadows and Reflections.

Pick the closest preset, then fine-tune.

Preset A: Competitive/FPS-first (for 60–144 Hz and mid-range rigs)

  • Full Screen: On; VSync: Off; VRR: On (if available)
  • Frame Cap: 2–3 FPS below refresh
  • AA: 2x MSAA + FXAA
  • Anisotropic: 16x
  • Track/World: High
  • Objects: Medium
  • Particles: Medium
  • Shadows: Off (Low at night if needed)
  • Reflections/Env: Off
  • Mirrors: Low detail, short distance
  • Opponents: Medium detail; Cars to Draw: ~16
  • Motion Blur/Bloom/DoF: Off
  • Sharpen: 0.4

Preset B: Balanced (for 144 Hz+ or strong 1080p/1440p rigs)

  • AA: 4x MSAA (add FXAA if shimmering)
  • Anisotropic: 16x
  • Track/World: High
  • Objects: High
  • Particles: Medium
  • Shadows: Low
  • Reflections: Low
  • Mirrors: Low detail, short distance
  • Cars to Draw: 20–24
  • Sharpen: 0.3–0.5

Preset C: Quality/Pretty (high-end rigs, 1440p/4K—still dirt-raceable)

  • AA: 4x MSAA + FXAA (or experiment higher if GPU allows)
  • Anisotropic: 16x
  • Track/World: High or Very High
  • Objects: High
  • Particles: Medium–High (drop to Medium on short tracks)
  • Shadows: Low–Medium (Medium at night if smooth)
  • Reflections: Low
  • Mirrors: Medium detail, short distance
  • Cars to Draw: 24–30 if CPU allows
  • Sharpen: 0.2–0.4

Tip: If you’re CPU-bound in big races, reduce “Number of Cars to Draw” first. If you’re GPU-bound, reduce Shadows and Reflections first.

Key things beginners should know

  • Cushion: The built-up edge of dirt near the wall. You must see its shape and height to run it without flirting with disaster.
  • Slick: Shiny, polished clay where grip drops off. On screen it should read as glossy vs the matte tacky lane.
  • Marbles: Loose rubber/dirt off-line—looks scattered and dull. Don’t mistake it for a grippy line.
  • FPS vs frame time: High FPS matters, but consistent frame time matters more. Micro-stutters ruin corner entry timing.
  • CPU vs GPU: Big fields and mirrors hammer the CPU. Shadows and particles hammer the GPU. Tune the right side of the equation.
  • Night races: Shadows/lighting cost more GPU. Keep Shadows Low, bump brightness slightly, and protect FPS.

Equipment notes: monitors, VRR, and VR

  • Monitors:
    • 144 Hz+ with G‑Sync/FreeSync is ideal. Cap FPS a hair below refresh for smoothness and low lag.
    • On 60 Hz, stability matters even more—cap to 58–59 FPS and slash stutter sources (shadows, particles).
  • NVIDIA/AMD control panel basics:
    • Enable G‑Sync/FreeSync if your display supports it.
    • Let the app control anisotropic filtering and AA.
    • Optional: Set Low Latency Mode (NVIDIA) to On/Ultra or AMD Anti-Lag; test for smoothness.
  • VR (quick pointers):
    • Prioritize Particles Low–Medium, Shadows Off/Low, Reflections Off, Mirrors Low.
    • Target a stable refresh or your headset’s reprojection rate (smoothness beats eye candy).

Expert tips to improve faster

  • Cap FPS and forget it: A clean, consistent frame time makes your throttle timing feel “connected,” especially when sliding off the cushion.
  • Tune in traffic: Dust and frame time only show their true colors when you’re tucked under someone’s tail. Test with 10+ AI or a busy practice.
  • Save two profiles: One for “Night/Heavy Field” (more conservative) and one for “Day/Light Field.” If you can’t save in-game, back up Documents\iRacing\rendererDX11.ini after you dial it in.
  • Read the surface every lap: Look for the matte-to-shiny transition moving corner to corner. If it’s hard to see, tweak gamma and sharpening before your next race—not during it.
  • If you’re getting screen tearing without VRR: Try capping 3–5 FPS below refresh. If it persists, you may need to accept VSync On for visuals—but expect extra input lag.

Common beginner mistakes (and quick fixes)

  • Running VSync On without VRR:

    • Symptom: Inputs feel “laggy,” especially catching a slide.
    • Fix: Turn VSync Off; use VRR if available; cap FPS just below refresh.
  • Ultra shadows and reflections:

    • Symptom: Random stutters mid-corner or in packs.
    • Fix: Shadows Low/Off; Reflections Off/Low. Protect your frame time.
  • Particles on High in big fields:

    • Symptom: Dust cloud turns into a white wall; GPU tanks.
    • Fix: Particles Medium. Keep visibility without a fog bank.
  • Oversharpened image:

    • Symptom: Slick looks like glare everywhere; hard to read traction.
    • Fix: Reduce sharpening to 0.3–0.6 and recheck gamma.
  • Too many cars drawn:

    • Symptom: Smooth alone, choppy in traffic.
    • Fix: Lower “Number of Cars to Draw” to 12–20 for races.
  • Chasing max FPS instead of stable FPS:

    • Symptom: 200 FPS solo, but hitching in traffic.
    • Fix: Cap FPS and tune heavy settings (shadows, particles, mirrors) for consistency.

FAQs

Q: What FPS should I aim for on iRacing dirt ovals? A: Aim for a stable FPS that matches your display. On 144 Hz, target 120–144 with a cap just below refresh. Stability beats peak numbers—avoid spikes and stutters.

Q: Is 60 FPS enough for dirt? A: You can race at 60, but input feel and timing are better at 90–144+. If you’re on 60 Hz, prioritize stability: cap to 58–59 FPS and keep heavy settings low.

Q: Which settings help me see the cushion and slick better? A: Keep Track/World detail High, Anisotropic 8x–16x, and sharpening modest (0.3–0.6). Adjust gamma so slick looks shiny and tacky looks matte without washing out the surface.

Q: How do I reduce dust blinding without losing info? A: Set Particles to Medium. It preserves the “shape” of dust so you can see cars and grooves, but it won’t smother your GPU or your vision.

Q: Should I use VSync, G‑Sync, or FreeSync? A: Use G‑Sync/FreeSync if your monitor supports it, and turn VSync Off in-game. Also cap FPS a couple frames below refresh for the smoothest feel.

Q: Any special settings for night races? A: Night lighting hits performance harder. Keep Shadows Low (or Off if needed), bump brightness slightly, and verify stable FPS in traffic. Don’t let visuals cost you consistency.

Conclusion

On dirt, your graphics are a performance tool. Prioritize clarity (see the slick and cushion), stable FPS, and low input lag, then add eye candy only if you’ve got headroom. Start with the preset closest to your rig, cap your FPS, and test in a busy dirt practice.

Next step: Load Eldora or Lanier in a hosted practice with 10+ cars. Run 10-lap stints while toggling Particles (Low/Medium) and Shadows (Off/Low). Stop when the slick and cushion are easy to read and your FPS graph is flat. That’s your race profile.

Suggested images (optional):

  • Screenshot of iRacing graphics settings with key options highlighted (AA, Particles, Shadows, Mirrors).
  • Side-by-side comparison: over-sharpened vs properly tuned gamma/slick visibility.
  • Simple diagram labeling cushion, slick, marbles on a dirt corner.

If you want to learn more about dirt track racing in iRacing, join the other racers in our Discord. Everyone is welcome. We talk about dirt racing all the time and have fun league races you can join.

Join hundreds of other racers on our Discord!